Forum Discussion
autopunk2007
14 years agoOccasional Contributor
You're right Tony. Very tricky.
I do agree that AQA can improve their support for silverlight, and I hope that this thread can help them improve this.
After hours of painful attempts to find I decent/elegant workaround. I found something that can probably help you too.
If you make any changes to TC options, the object browser regenerates.
So, if you execute the following in your test for example, the object hierachy is completely rebuilt and it will fix itself.
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="Word.Document" name="ProgId" />
<meta content="Microsoft Word 12" name="Generator" />
<meta content="Microsoft Word 12" name="Originator" />
I do agree that AQA can improve their support for silverlight, and I hope that this thread can help them improve this.
After hours of painful attempts to find I decent/elegant workaround. I found something that can probably help you too.
If you make any changes to TC options, the object browser regenerates.
So, if you execute the following in your test for example, the object hierachy is completely rebuilt and it will fix itself.
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="Word.Document" name="ProgId" />
<meta content="Microsoft Word 12" name="Generator" />
<meta content="Microsoft Word 12" name="Originator" />
Options.Web.TreeModel = "DOM"
Options.Web.TreeModel = "Tree"
Sys.Refresh
I know, a strage workaround, but it works (keeps the relationship between a textblock and ListBoxItem in sync.)
This will suffice for what I need. But I hope it can help you and others until AQA resolve the problem.
Thanks again Tony
Evan
Related Content
Recent Discussions
Name Mapping Issue
Solved46 minutes agokgreger1- 2 days agodhundley