Page 1 of 1

active tab value doesn't work

Posted: Tue Jun 21, 2011 1:21 am
by amc
Hi,

the active tab panel value doesn't seem to work if you have an error indicated on any other tab.

How to demonstrate.

create a standard 3-tab tab panel. on tab 0 (first tab), put a text box with one error message with an error condition indicator.

in rpg, set the active tab value to 2 (third tab) and make sure the error indicator for the text box on tab 0 is set to off. exfmt the screen. tab 2 will be displayed as expected. click on tab 1 (middle tab) to return to rpg. in rpg, set the text box error indicator on, set the active tab value to 0 (first tab) and exfmt the screen. tab 2 (middle tab) will still be displayed, with the error message bleeding through from tab 0 (first tab). I expect that tab 0 should be displayed.

Can you have a look at this . I can send some code if required.

thanks & regards

Tony C

Re: active tab value doesn't work

Posted: Tue Jun 21, 2011 10:20 am
by Brian
I have recreated the problem and am looking into it now.

Re: active tab value doesn't work

Posted: Tue Jun 21, 2011 10:39 am
by Brian
I will post back here when we have a fix. Thanks for bringing this to our attention.

Would it be sufficient if the ProfoundUI runtime just automatically returned you to the tab with the error instead of your program having to do it?

Re: active tab value doesn't work

Posted: Tue Jun 21, 2011 7:27 pm
by amc
Brian,

In the program I am working on, returning to the tab with the error would be sufficient.

If later on, you fix the active tab value to take precedence, it will still be ok for me as I am setting the active tab value before display anyway.

regards

Tony C

Re: active tab value doesn't work

Posted: Mon Jul 25, 2011 11:00 am
by esdaled
Any update on this item?

We are also experiencing the same problem.

Returning to the tab with the error would be fine.

Re: active tab value doesn't work

Posted: Mon Jul 25, 2011 5:05 pm
by Alex
In the next update, Profound UI will automatically switch to the Tab with the error. We are estimating that we will publish the update before the end of this week.