|
#1
|
|||
|
|||
BUG report (or known issue?)
If I have the following (silly) code in a custom action GUI block, I get the options from the first list embedded in the second list.
This does not seem to be appropriate behavior. I would have expected each list to contain a distinct set of items per the .action file. I am running the latest evaluation download available as of 7/14/2003. I look forward to hearing back on this one. -- Jason ---------------------------------------- Code:
<Tab Name="My Tab"> <Field Name="Option1" Type="Combo" Description="Message" Width="50" DefaultValue="1"> <ListData> <ListItem Text="Option A"/> <ListItem Text="Option B"/> <ListItem Text="Option C"/> </ListData> </Field> <Field Name="DonkeyCheck" Type="Check" Description="Check if the Donkey is still alive?"/> </Field> <Field Name="TossIt" Type="Combo" Description="Throw what at the Donkey?" DefaultValue="1"> <ListData> <ListItem Text="A banana cream pie"/> <ListItem Text="A whipped cream pie"/> <ListItem Text="A bunch of jello"/> </ListData> </Field> </Tab> |
#2
|
|||
|
|||
Even more insidious....
The bug report I just added is more insidious than I originally expected. (at least in the eval copy)
All edit fields following the combo field get an associated drop list with all items that shoudl only belong to a combo box! |
#3
|
|||
|
|||
Here is a zip with a screen snap and the user.action file.
I forgot to attach some important info in the last post. It's attached to this one. you will need a WInZIP or a similar tool to view the contents.
The .action I modified was the ".Sampel\User Actions\NETAction\Net Action.action" file. scrsnap.bmp is a screen snap of the dialog with the last edit (not intended to be a combo/edit) expanded... In this you see the cumulative effect of the scope issue. -- Jason |
#4
|
|||
|
|||
That is indeed a bug, which will be fixed for the next release.
|
#5
|
|||
|
|||
Timing
Approximately when will the next official release be?
Or is that yet To Be Determined? |
|
|