On Tue, May 18, 2010 at 12:00 AM, Dmitriy Igrishin <[email protected]> wrote: > Hey OvermindDL1, > >> That is just because of the way they have it set up. WMenu works fine >> for me and it keeps state just fine, but I have it save/restore the >> path on change for the submenu's, works well, was simple to do, I see >> not need for such changes. > > Do you enable internal path support for items provided by WMenu or you > set internal path by you own handler when user clicks on some item?
Well, first of all I do not do submenu's like how the examples do, I needed more control, so in each WMenu I have a container, in that container I have another WMenu if necessary (and so forth if necessary). Those containers are subclassed from some generic logic of my things that handle that with an internalpathchanged. In my opinion, internalPathChanged callbacks really need to be changed. Instead of just handling every single path change, they should register to a certain part in the hierarchy. It could easily be handled very efficiently internally by a tri-tree. Hmm, would you accept a patch if I committed such a change? ------------------------------------------------------------------------------ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
