Very Strange Behavior

[tlyon]

RE: Very Strange Behavior

Anyone need a copy of A4v6 for DOS? Forget all these windows!

Tom Lyon

[Peter.Greulich]

RE: Very Strange Behavior

I forgot, when you maximize the form - the little X reappears even if you deselected "System Menu" from the form properties. I think in Alpha's eyes this is not a bug. To my mind, it is.

Peter

[forskare]

RE: Very Strange Behavior

Hi Peter,

Thanks for your reply. "I forgot, when you maximize the form - the little X reappears even if you deselected "System Menu" from the form properties."

Are you saying that there is no way to get around this? That a custom menu can be created and the user still has access to the CP via the "x"?

If so the only answer is to have NO menu as even a 'blank menu' will have the "x".

kenn

[Tom Cone Jr]

RE: Very Strange Behavior

Ken,

cancel() does not remove the x from the title bar. It just deactivates it.

-- tom

[forskare]

RE: Very Strange Behavior

Hi Tom,

OK but how does it work being on the OnExit vs an OnEnter event?

Thanks,

kenn

[Tom Cone Jr]

RE: Very Strange Behavior

Ken,

Did I say use the OnExit event? If so, I erred.

Should be in the CanExit event.

OnExit fires after the window closes. You need to hook the cancel() command to CanExit to prevent the window from closing.

-- tom

[Peter.Greulich]

RE: Very Strange Behavior

Ken,

Are you saying that there is no way to get around this? That a custom menu can be created and the user still has access to the CP via the "x"?

As far as the CP goes, why not use :controlpanel.hide()?

If so the only answer is to have NO menu as even a 'blank menu' will have the "x".

A blank menu will have the X - right.

Peter

[forskare]

RE: Very Strange Behavior

Tom,

No you didn't error, I did.

"You need to hook the cancel() command to CanExit to prevent the window from closing." OK, I got it, I think. It ONLY prevents the window from closing when the "x" is clicked. The window will close when a "Close" button is pressed.

Sound right?

[forskare]

RE: Very Strange Behavior

As far as the CP goes, why not use :controlpanel.hide()?

Yah, why not. Too many trees to see through. I just never thought to put it on all the forms? Oh Duh!!!

Thanks Peter.

kenn

[Tom Cone Jr]

RE: Very Strange Behavior

Ken,

No need to put it in the events on all forms. Once the control panel is hidden, it's hidden. I hide it when my opening main menu form opens, and don't have to do it again.

Note, I maximize it in my autoexec script.

Then I hide it.

Why? because it opens before my main menu form, and I want all forms maximized.

-- tom

[forskare]

RE: Very Strange Behavior

Tom,

Forgive me if I might seem that I haven't a clue what this is about. My problem is I'm trying to work through some eratic bahavior. For instance; I created an Autoexec script containing:

this.maximize()
controlpanel.hide()

Problem.....The startup form does not maximize. It will, IF, I change controlpanel.hide() to controlpanel.maximize. When that change is made,....when exiting the form via a hidden button, I get the close / maximize flash on the screen.

Another problem...when going from the startup form to another form, and then close the form (same no matter which form I go to) the startup form does not maximize.

So I put:

this.maximize()
controlpanel.hide()
controlpanel.maximize()

in the autoexec.script and the startup form opens maximized but the startup form does not stay maximized when returning from another form.

And, just using the bottom 2 lines of control panel code produces the same result.

I've looked and looked for any code which may cause the forms to NOT maximize and I can't find any.

Thanks,

kenn

[Peter.Greulich]

RE: Very Strange Behavior

Ken,

I don't think that this.maximize() makes sense in an autoexec script, since "this" would refer to the script itself, and you can't "maximize" the script. How about this as an alternative autoexec script:

controlpanel.hide()
f=form.load("main_menu_form_name_here")
f.maximize()
f.activate()
f.show()
END