Button Object Bug

[anticecil]

I already confirmed this with StephenL as being a bug in at least r248 and r249.

Upon investigation, using the "Button clicked" event condition with the "disable" action on the Button Object or the Bouton CS object to disable itself causes some side effects in mmf.

side effect 1: f2 no longer restarts the app.
side effect 2: f4 (not alt+f4 as it should be, but which also still works) closes out the app.

Disabling a button in any other circumstance (only once, start of frame, etc) or using "button clicked" to disable a DIFFERENT button does not produce these effects.

also, enabling that button again does not resolve the effects.

haven't noticed any further side effects but that's not to say there aren't any.

[LB]

This is not an MFM2 bug. This is a windows bug. The reason is that focus is not lost from the button obejct. You know very well that you can't use the menu shortcuts when focus is on a windows control. All you have to do is get an edit box to grab the focus then loose it.

[anticecil]

if that is the case then the object should automatically lose its focus so the application can continue functioning. or at least have a focus->on/off action like other windows controls have.

it also doesnt explain why f4 closes out the application in this specific context. f4 does nothing if the button or any other windows control has focus. so IT is a mmf2 bug.

note: you seem to be right about the focus thing making you unable to use menu shortcuts (alt+f4 excluded for some reason. still works even when a windows control has focus, but no other shorcut works), and also in my previous post using button clicked DOES reproduce the first effect, f2 does not restart the app, but DOES NOT reproduce the second, making it an mmf2 bug.

[LB]

Still you are wrong. The Alt + F4 menu shortcut has nothing to do with the actual Alt + F4 shortcut. If you remove it Alt + F4 will still work because it is a windows feature.

This is a windows bug and many non-MMF2 apps I have seen have this issue.

[RickyRombo]

LB he isn't pressing Alt. He's pressing only F4

[LB]

Because it is a windows shortcut key...

[RickyRombo]

What? You're doing a terrible job of explaining why F4 acts like Alt + F4.

[LB]

Eh that's not what I am saying.. >_<

I am saying that because it is a Windows control it has certian ties with Windows shortcuts. Button object can be assigned to a menu command. When the button is disabled but still has focus it causes Windows to glitch up a bit. I have seen this in several other non-MMF programs and it behaves this way.

[anticecil]

LB f4 is not a windows shortcut. it is ALT+f4 that is. im saying that simply f4 is closing out the application.

and your explanation that its because the button is a windows control is moot. none of this happens with any other windows control or in any other circumstances. only when you disable a button in regards to itself being clicked.

[lembi2001]

obviously when you are disbabling the button you are inadvertantly causing ALT to become active. try this to test my theory:

make sure your toolbars are visible in your app and then run it. disable your button and then press any one of the menu shortcuts to see if the menu displays. if it does you may have to find a way to stop ALT becoming active

EDIT - Forget what i said. You are right this does appear to be abug in the object. it is not a windows thing at all as clicking the button and disabling it should not make you able to close a window just by pressing f4.