When a Form In Dialogue includes a tabpanel and the FID appears on top of a form which includes a tabpanel then when the FID is closed the underlying tabpanel is greyed out and inactive. The user must switch forms and come back in order to refresh.
Running application.UpdateUI() after the FID has closed has no effect.
Morley:
When a Form In Dialogue includes a tabpanel and the FID appears on top of a form which includes a tabpanel then when the FID is closed the underlying tabpanel is greyed out and inactive. The user must switch forms and come back in order to refresh.Running application.UpdateUI() after the FID has closed has no effect.
Thoud shalt not show the same tabpanel twice
Are you showing the same tab?
Riccardino:
Morley:
When a Form In Dialogue includes a tabpanel and the FID appears on top of a form which includes a tabpanel then when the FID is closed the underlying tabpanel is greyed out and inactive. The user must switch forms and come back in order to refresh.Running application.UpdateUI() after the FID has closed has no effect.
Thoud shalt not show the same tabpanel twice
Are you showing the same tab?
Exactly. It’s being shown in a Help screen FID. Showing it on the FID to give the disoriented new user some visual direction on what the supporting text is talking about.
Would be useful if an application.UpdateUI() on hide of the FID refreshed the form. If that’s not possible, that’s unfortunate.
yes you can’t show the same form twice at the same time you can see them on screen.
So when viewing the dialog you still also view the main form. So you can’t reuse a form that is shown there.
In 3.0 we hope to have some kind of aliasses for forms. Then you can allias the form that you show in the dialog and then a form is seen as 2 forms so you can view twice at once.
jcompagner:
yes you can’t show the same form twice at the same time you can see them on screen.
So when viewing the dialog you still also view the main form. So you can’t reuse a form that is shown there.In 3.0 we hope to have some kind of aliasses for forms. Then you can allias the form that you show in the dialog and then a form is seen as 2 forms so you can view twice at once.
That’s probably welcome in some situations.
However the form underneath is very large, features five tabpanels among a great deal else. The Help FID features just one of the tabpanels with supporting text and callouts to point out its features. By using the tabpanel itself I show something in context and at the same time avoid the bandwidth of a large placed gif.
Kind regards,
i don’t know exactly what you mean but i think you don’t get the alias solution i described..
You alias the form that you use as a TAB in the main form and that you use as a TAB in the FID. The main form doesn’t have anything to do with it.
lets say you have Form X.
You show form X in a TAB of the main form.
In the developer you say in a property also that Form X is also called Y.
Then when you show the FID you don’t say show(X) but show(Y)
then there is no problem with disappearing tabs.
Thanks Johan, got it now.
On the first pass, I understood you as saying the form containing the tabpanel would be aliased, which didn’t make much sense. Yes, the alias system you’re actually building will be most welcome and useful.
Thanks for clarifying that.