Resolved Bug: Condition change causes node combo box change

[Mark Sanctuary]

When trying to update a clause the node selected and all its arguments reset. Here is the steps to the bug I am seeing...

 

1. [*:3k9a13if]Select an existing program that you want to change
   [*:3k9a13if]Select a 'If' clause that you want to update
   [*:3k9a13if]Mine says 'Control' and I change it to 'Status'

After doing this the node combo box and all the argument combo boxes jump to the top entries and does not stay on the already existing node and arguments.

 

If it could stay on the existing node this would be very helpful. I understand that the lists sizes change from selection to selection. So if it could capture the selected node and arguments, and try to keep them selected unless they are not there on the new lists, otherwise they could jump to the top entry in the combo boxes. If you go to say 'X10' that does not have it and you decide to come back to 'Status' would be nice if it still had the same previous info from before.

 

Why this suggestion; because when your trying to just adjust one item then hit the Update button you don't notice that your node and all its arguments has just changed too. And when you’re updating a program condition you more than likely will not be changing the node and all its arguments.

[Michel Kohanim]

Mark,

 

Should already be fixed.

 

Thank you,

Michel

 

When trying to update a clause the node selected and all its arguments reset. Here is the steps to the bug I am seeing...

 

[*:3u1xb105]Select an existing program that you want to change
[*:3u1xb105]Select a 'If' clause that you want to update
[*:3u1xb105]Mine says 'Control' and I change it to 'Status'

After doing this the node combo box and all the argument combo boxes jump to the top entries and does not stay on the already existing node and arguments.

 

If it could stay on the existing node this would be very helpful. I understand that the lists sizes change from selection to selection. So if it could capture the selected node and arguments, and try to keep them selected unless they are not there on the new lists, otherwise they could jump to the top entry in the combo boxes. If you go to say 'X10' that does not have it and you decide to come back to 'Status' would be nice if it still had the same previous info from before.

 

Why this suggestion; because when your trying to just adjust one item then hit the Update button you don't notice that your node and all its arguments has just changed too. And when you’re updating a program condition you more than likely will not be changing the node and all its arguments.

[Mark Sanctuary]

Tested and confirmed this bug is resolved.

[Sub-Routine]

I'm sorry, I still see the scene/device node changing to the first device on the list when I change between Status and Control.

 

Rand

[Mark Sanctuary]

Your right it is not preserving the choice if it’s on both status and control combo box lists.

[Mark Sanctuary]

Chris,

This is one of those annoying issues that when adjusting existing programs between Control and Status. Is there any chance it might be fixed in the next beta drop?

[Chris Jahn]

I wasn't going to make this change, but after playing with it a bit I agree that it would nicer if it retained the combo box values.

 

I'll put the fix in the next drop.

[Mark Sanctuary]

I tested this a bunch of ways and I think this is now fixed now. What do you think Rand?

[Sub-Routine]

I haven't tested it in many ways but so far, so good.

 

Rand