First, if you are using Win32::GUI, you shouldn't need to import SendMessage() yourself.

Second, you cannot just make **it up as you go along :) The description of the TVM_GETNEXTITEM message from the page I linked is:

lResult = SendMessage( // returns LRESULT in lResult (HWND) hWndControl, // handle to destination control (UINT) TVM_GETNEXTITEM, // message ID (WPARAM) wParam, // = (WPARAM) (UINT) flag; (LPARAM) lParam // = (LPARAM) (HTREEITEM) hitem; );

The wparam argument should be one of the following flags, not the length of a buffer

TVGN_CARET TVGN_CHILD TVGN_DROPHILITE TVGN_FIRSTVISIBLE TVGN_LASTVISIBLE TVGN_NEXT TVGN_NEXTVISIBLE TVGN_PARENT TVGN_PREVIOUS TVGN_PREVIOUSVISIBLE TVGN_ROOT

And the lparam argument should be either null or the handle returned from a previous call, not a pointer to a buffer.

The basic mechanism is,

  1. You pass TVGN_ROOT/null, to get a handle to the root item in the display.
  2. Then you pass TVGN_CHILD/roothandle (from above) to get the handle to the first child.
    1. Then you use TVGN_NEXT/firstChildHandle (from above) to iterate the first level children.
    2. And TGVN_CHILD/firstChildHandle to process the grandchildren...

Obviously, you will need to loop/recurse at each level to optain all the siblings & children at each level. It's upto you to decide whether you depth first or breadth first.

The return value from the SendMessage is the item handle to each node in the tree. As well as using this as an argument to get the next sibling or child in the tree, you also use it to send TVM_GETITEM messages to each of those items to retrive the TVMITEM(EX) structure that contains the data & state that is the node.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In reply to Re^5: Enumerate a Win32 Treeview by BrowserUk
in thread Enumerate a Win32 Treeview by slloyd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.