AdvMessageDlg contentregion disappears

[Radford_Mark]

I have a AdvMessageDialog with a CONTENTREGION that I'm validating input on (async).  If I set Allow := false in the OnSyncButtonClick then the content region disappears.

The work around is to Dialog.ShowAsync; in the validation fail code.  I assume that doesn't cause any problems but shouldn't the Allow := false work correctly?

Using the latest IW 11.0.0.42 and latest TMS.

I thought I had reported this before but can't find a reference to it.

Thank you

[Radford_Mark]

After running some more tests, it just seems that AdvMessageDialog needs some real testing when using Content Regions, especially when using then with the 'Allow' option of the async click.

Please try various options to verify that it all works as the designers intended, because it doesn't seem to...

[Radford_Mark]

Sorry to keep adding to this but I'm discovering more things.   If the Content Region has an invisible IWDatePicker on it with RenderInvisibleControls = true on the region then the region does not disappear....

[Bart]

@Radford Mark

I have a AdvMessageDialog with a CONTENTREGION that I'm validating input on (async). If I set Allow := false in the OnSyncButtonClick then the content region disappears.

This was an issue in Internet Explorer only and has now been fixed.
The update will be available with the next release of the TMS IW Component Pack

[Bart]

We are aware that there can be issues when using a ContentRegion and async events in IE.

Unfortunately this is a complex problem that is related to IntraWeb interaction with the IE browser due to the way the IWRegion is placed in the IWAdvMessageDialog control.

As a workaround you could try using synchronous events instead of asynchronous events.

[Radford_Mark]

But the 'allow' doesn't seem to work for sync events.  i.e. the dialog just closes no matter which button is pressed or if allow := false is used...

[Radford_Mark]

Generally, with limited use, the async stuff works (if that above fix is applied)... can you share that as something I can temporarily add?

Also, if I try to set a edit field value before ShowAsync the value does not seem to get set.  i.e IWEdit1.Text := 'abc';   Is there a way to set the contents of a field in the content area prior to showing the dialog?

Thanks

[Bart]

@Radford Mark

But the 'allow' doesn't seem to work for sync events. i.e. the dialog just closes no matter which button is pressed or if allow := false is used...

This issue was already fixed with the fix for the OnAsyncButtonClick.

The update will be available with the next release of the TMS IW Component Pack.

[Bart]

@Radford Mark

Generally, with limited use, the async stuff works (if that above fix is applied)... can you share that as something I can temporarily add?

Yes, please send an email to mailto:help@tmssoftware.com requesting an incremental source update and we'll provide one as soon as possible.

@Radford Mark

Also, if I try to set a edit field value before ShowAsync the value does not seem to get set. i.e IWEdit1.Text := 'abc'; Is there a way to set the contents of a field in the content area prior to showing the dialog?

This is related to the same ContentRegion issue in IE as mentioned in my previous reply.

[Radford_Mark]

Just a follow up... it appears that the issue with a AdvMessageDlg content region disappearing when an ASYNC event occurs (timer for example) is still only resolved by putting a TIWDatePicker on the form.  (Other controls may also 'fix' the problem but I just drop one of these on the region, hide it, make the region RenderInvisibleControls).  I believe I reported this a while ago but if you need an example, please let me know.