On Thu, Feb 17, 2011 at 05:30:43PM +0000, Peter Pearson wrote: > On 17/02/11 09:15, Peter Pearson wrote: > >>> Also, I know it will involve QTreeView saving its state during updates > >>> which I know from experience is a pain in the ass, but it would be > >>> *fantastic* if when stepping over code with an opened up structure in > >>> the watch window, I didn't have to re-open the tree to find the variable > >>> each time the values are updated - it really slows things down... I know > >>> I could use the watch, but still - MS Dev studio manages it... > >> > >> Funny. I thought we do as well? > >> > >> Basically the "internal names" (i.e. locals.this.*.foo.x) of the expanded > >> items are stored and items with the same internal name after the > >> step get expanded again. Of course, when there isn't such item, > >> that state is lost. > >> > >> Is this also Mac? > > > > Linux 64's doing it, but Mac 32 isn't... I'll rebuild the Mac one from > > git to confirm... > > Linux 64 seems to keep the expanded state for local items, but not for > watch items. > > Mac 32 doesn't do it for either... > > Shall I raise a bug in JIRA?
The Mac part sounds familiar. Maybe there's already an issue for that. I don't think there's something for the watchers, though. Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
