Custom dialog: Unexpected behaviour

[vsiegle]

Using Dev7 on XP I created a custom dialog box to delete records. I activated the first two buttons. Scripted button one to delete a record. Scripted button 2 to cancel the dialog and exit the script. All worked as expected when tested. Compiled the database to runtime. Launched and tested the dialog. No problem. Exited and opened the file with Dev7 and tested again and work as expected until I activated the dialog box and instead of using the "Cancel" button I closed the window with the windows close box. When I did this the record was deleted just as if I had clicked the "Delete" button. I confirmed that this behaviour was repeatable in my other solutions. The number one button is considered "default" and I can only assume that the close window box on the title bar of the window is activating button one. Can anyone else confirm this?

[Vaughan]

Confirmed.

Unexpected behaviour perhaps, but not unknown nor undocumented.

[DykstrL]

Just swap your buttons so clicking the cancel button or the "X" has the same effect.

It is frustrating that FileMaker has the default set opposite to what it really should be.

I think we've all been there at one time or another.

[vsiegle]

Thanks for the quick response. Just wanted to be sure it was not something local to my setup.

[Vaughan]

Yup. Must have seemed like a good idea at the time.