A Window is not a flea.

[mronck]

Re: A Window is not a flea.

Seems to, yes. I tried that and it worked! However, the Alpha Five child windows will pop-up from internal system, you can't programmatically approach them. Or you prove me wrong with that as well :-)

[Peter.Greulich]

Re: A Window is not a flea.

If you mean like controlpanel or code editor - they seem to pop up where they want. But if you mean forms, then the above is applicable. Open the form via code and position via code - no?

[mronck]

Re: A Window is not a flea.

If you mean like controlpanel or code editor - they seem to pop up where they want. But if you mean forms, then the above is applicable. Open the form via code and position via code - no?

Agreed on forms. But my prob was with the own A5 child windows. You know, when you are building something every time those small windows open where you have to configure settings and such. I know I am probably just nagging, but it annoys me when those windows always pop-up somewhere left, I just would like them to pop-up in the center. Almost sounds compulsive :-) but it is what it is.

[Peter.Greulich]

Re: A Window is not a flea.

Got it. I understand. I agree that it is a pain. Too many popup windows if you ask me. I'd prefer an IDE w/o all the windows.

[jkwrpc]

Re: A Window is not a flea.

Peter you are right about people not knowing about popups. I was opening forms as dialogs, but that has some challenges. When I converted them to popups everything worked and meet my goals. It is a nice feature, but as was discussed not something everyone would use or like to use all the time.

This is a question for those working with grids on the desktop. I think there is also something like a page layout component. I am not sure how that works never having used, but could be used to control the placement of the grids? Then control through code when certain grids appear, kind of like pages? If you possible it could give you pretty granular control of objects on the form/page.

[Clunes]

Re: A Window is not a flea.

There has been some discussion since my last - sorry found bed too important after all my travelling!! For what it is worth the following script can be put in the on_activate event to a form. It is designed to put the form in the left quarter of a view. This assumes that if you are using two screens, it measures the width of the two as one and then divides that into 4. So in theory it would be in the middle of the left screen.

I do not have two screens so my assumptions on how the window is measured may be wrong. Frustrating was the way Alpha plays with measurement. I found that this all measured in pixels, which was logical, however all the references in properties were either inches or cm. Trial and error and a lot of debugging got me there.

Code___________

dim myw4 as c
dim myww as n
dim mywh as n
myww = UI_INFO( 8 ) 'Get the client area width
mywh = UI_INFO( 9 ) 'Get the client area height

myw4= a5_get_units() 'this line was not required
dim myw1 as n

myw1 = topparent.height

topparent.Top = (mywh/2) - (myw1/2) 'measure height of form and reduces measurements by 1/2 of height

myw1 = topparent.width

topparent.Left = (myww/4) - (myw1/2) 'measure width of form and reduces measurements by 1/2 of width

End Code____________________

[mronck]

Re: A Window is not a flea.

Hi Mark,

That is indeed a script for use on a form. My problem however was NOT with the position of a form within an application, but with A5 Child Windows within the A5 working area. These child windows are the ones that open whenever you would need to configure components or similar. Those are system windows from A5, not from the actual application built. I am sorry if I made this not clear enough.

[Clunes]

Re: A Window is not a flea.

Ok (should have read ALL previous posts - maybe not compulsive but could be phobic)- You can probably get over this with using xdialog window instead of the child window, but depending on how many you see coming up and what they are. For instance you can build a window for email settings, error messages (not built in ones as they would be system related).

I do this sort of thing so I can remove all alpha menus and make sure the user only does what is needed.