[svn] 3787: Added FxTextArea, FxTextInput, and TextView class-level examples to the Component Explorer.

Question

Revision: 3787
Author: [email protected]
Date: 2008-10-21 12:16:28 -0700 (Tue, 21 Oct 2008)
Log Message:
Added FxTextArea, FxTextInput, and TextView class-level examples to the Component Explorer.
Modified Paths:
flex/sdk/trunk/samples/explorer/explorer.xml

Answer 1

One workaround is to turn off automation:
File-->Options, Advanced tab, General Section, uncheck "Enable Automation Events"
However, you will loose the ability to configure callouts, and all of the commands in the Process Engineering tab.
Another workaround is to change the loop number of the shape you are editing before changing its type. Then change the loop number back to the correct loop number.
This is another example of the pernicious philosophy of trying to help the user do what the programmers think the user is trying to do that started in Excel 2000 (where you can no longer tell excel that you want a scatter plot - it will force the plot
to be a line plot under certain circumstances).
I suppose another option would be to modify the master and swap the text and subtype shapes in the indicator to use the subtype property for the loop number and then use the text for the instrument type. I guess this is what MS was trying to implement, but
didn't explain it well enough to their programmers.