Sorry to be a pain, but having looked at rev. 1508 I think managing
the scroll region by hand might be necessary at some point.
The use of the tree, and eg. navigating LeoDocs.leo, is likely to be
the first point of call for most users. Currently, and IMO of course,
the behaviour when expanding and contracting nodes makes it difficult
to keep an eye on the structure - I keep thinking (almost
subliminally) 'what did that click do'?
This makes it hard to read a tree you are learning to navigate (eg.
LeoDocs.leo), and gives a bad first impression - the last thing you
want.
>From what I see, I guess that you are right about QTreeWidget
attempting to 'optimise' things BTW ;-(.
Regards
Jon N
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
