On Tue, Oct 26, 2010 at 06:09:16PM +0200, tbp wrote:
> On Tue, Oct 26, 2010 at 5:52 PM, André Pönitz <andre.poen...@nokia.com> wrote:
> > Should it have n sets of children ('as doubles', 'as floats', 'as short'...)
> > instead? Then one could expand the interesting ones once and no
> > extra click needed to switch the type.
> That's the way of MSVC, and at least it's exhaustive (but they cheat
> since they alias __m128* to an union), at the price of much screen
> estate.
>
> > So what would be the preferred display in that case?
> I don't really know what would be reasonable; i suppose having per
> 'instance' preference isn't an option :)
There are "preferences by type" and "preferences by iname" already.
"iname" basically encodes name and depth of the variable (local.a,
local.b.some_member, watch.1, ...).
So you can have different displays for different __m128 variables
within the same function already. The deal is that a likewise named
variable in another function "inherits" the display (by design
actually).
> Hmm. What about the exhaustive children thing + a preferred short
> display (one of those children) per vector type (as in __m128, __m128i
> etc)?
If you can come up with some ASCII art for the layout I'd fix it tomorrow.
Andre'
_______________________________________________
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
