Watching variables in extended types

[Andrew_Smith]

One of the more useful features in IVF 11 is type extension. However, although the compiler allows you to reference parent components directly from the child, the Visual studio variable watch requires you to fill in the name of the extended type in all references to parent components. Can this be fixed?

Andy Smith

[Steven_L_Intel1]

I entered a feature request for this, ID is DPD200118856.

[Steven_L_Intel1]

Looks as if this was fixed a while ago.

[Andrew_Smith]

I just tried it with XE2013 update 3 in VS2010. Not working for me. See attached screen capture.

[Steven_L_Intel1]

I tested it and it seemed to work. Can you provide an actual test case? A screen shot doesn't tell me a lot.

[Andrew_Smith]

Attached project demonstates.

[Andrew_Smith]

Trying agin with attachment

[Steven_L_Intel1]

The source file isn't in the zip.

[Andrew_Smith]

Sorry VS by default put the source in the previous project I was using. New project attached.

[Steven_L_Intel1]

Works for me in the new beta - I will try it on the older version as well and see what I get.

[Steven_L_Intel1]

Oh, I misunderstood the problem. You're right - if I watch B%I it doesn't work, but I can see B%BASE%I.

[Andrew_Smith]

It might seam a trivial shortcoming and in the simple test case it is. But once you get a few more levels deep with inheritence and you use more meaningful (long) names for things it gets time consuming typing in watches. Your actual code is unlikely to use the full tree to access components so you dont have something in the code to copy and paste from. It is diifucult to hover over the code to watch too becuse you have to expend the tree to find things. Is there any plan to improve the watch capability ? How does it compare to other languages from Microsoft? 

Another case where watches dont work like code is where you access a component from an array of derived types.

[Steven_L_Intel1]

We've already fixed an issue where hovering over a component name in a derived type reference doesn't find the item - that will be in a future release. We're a bit constrained in what we can do here as the debug symbol table languge is limited (we have similar issues on Linux with DWARF), but perhaps we can improve things here.

[Steven_L_Intel1]

We've made further improvements in this area for the next major release.