![]() | |
#11
| |||
| |||
|
|
Amen. To see that this is the standard way Windows works, do this: 1. Open the display properties window (right click on blank area of Windows desktop, choose Properties). Go to the Settings tab. Make note of the resolution. 2. Note how much space on the screen the dialog occupies. 3. Now change the resolution to something lower than it currently is and apply (Do NOT close the dialog). 4. Note how much space on the screen the dialog occupies - it occupies more space. 5. Now change the resolution to something higher than it originally was and apply (again, do NOT close the dialog). 6. Note how much space on the screen the dialog occupies - it occupies less space. 7. Repeat for each resolution. The dialog does NOT change size. It *looks* bigger or smaller based on the resolution. If your form is designed to take the whole screen at 800x600, leave it that way. When I run your form at 1920x1280, it will take up a small portion of my screen (800x600 pixels, to be exact) and that is exactly what I want. Liz Dennis Santoro wrote: So, in summary, pick a size. Design for it. Forget zoom. |
#12
| |||
| |||
|
|
Enlightening and interesting, and of course absolutely right. But how to use opal to resize the Paradox outer shell (the Paradox windows application) to fit the form precisely? With Paradox 11 I have problems with the form zoom property because text-editing gets a weird lag with the cursor(Bertil has described and confirmed this phenomena) So with this problem in mind there is almost a *must* to use a form scale of 100%. But I should very much like to know how to resize the Paradox application to fit the form, so the users (with different screen resolutions) don't have to do this manually. Any tip? Bjorn |
#13
| |||
| |||
|
#14
| |||
| |||
|
|
Make sure your forms are all the same size, or pick the largest form. Temporarily put code on the form to get the app size. Run the form, position form and app as desired. Trigger the code, record the size of the app, put code in init to size the app. That's what I do. I also set the position of the app window (you can also read size and position on exit, store them for the user, and restore them on start-up - it's not hard (assuming your form has a startup script or form). Liz Bjorn Sagbakken wrote: Enlightening and interesting, and of course absolutely right. But how to use opal to resize the Paradox outer shell (the Paradox windows application) to fit the form precisely? With Paradox 11 I have problems with the form zoom property because text-editing gets a weird lag with the cursor(Bertil has described and confirmed this phenomena) So with this problem in mind there is almost a *must* to use a form scale of 100%. But I should very much like to know how to resize the Paradox application to fit the form, so the users (with different screen resolutions) don't have to do this manually. Any tip? Bjorn |
#15
| |||
| |||
|
|
Hmm, Our state medical system uses software that spawns numerous pop up windows and it is very messy. |
|
It amazes me that professionals design such user unfriendly software. |
|
I am also trying my best to get away from pop up forms as much as possible. I've grown to really dislike apps where everything you do spawns yet another pop up. It makes for a very confusing interface, in my opinion. Hmm, Our state medical system uses software that spawns numerous pop up windows and it is very messy. It amazes me that professionals design such user unfriendly software. As a semi-amateur, it is something I avoid, and people who use my software find it reasonably straight forward... PW |
#16
| |||
| |||
|
|
See the sizing demo on our paradox resources page (link in my signature). Generally I design all my forms to maximize inside the size I define my ap window and use that use that space unless I am popping up a dialog (which I then have at an explicit sub size) Denn Santoro President Resource Development Associates http://www.RDAWorldWide.Com Offices in the United States and Germany Providing solutions to health care, business, governments and non-profits since 1982 |
#17
| |||
| |||
|
|
Thanks a lot Liz, In the back of my head I was discussing with myself something like that. With your pin-pointed information I tested this with success. Already I have established a user-profile table for various settings, like printers other stuff. Now I think I will add a registration for preferred screen-resolution. But is there a way to detect the user's desktop resolution so this can be done automatically? Bjorn |
#18
| |||
| |||
|
|
IMO, the resolution is less important than storing the app size and position when the user closed it. This way you can always open the app in the position and size the user prefers. That said, look at sysInfo() in ObjectPAL help - it has resolution information. (I only use this to determine whether or not to maximize Paradox. If the resolution is 800x600 or less, I maximize; otherwise, I explicitly size and position it to take up a portion of the screen.) FWIW, Liz Bjorn Sagbakken wrote: Thanks a lot Liz, In the back of my head I was discussing with myself something like that. With your pin-pointed information I tested this with success. Already I have established a user-profile table for various settings, like printers other stuff. Now I think I will add a registration for preferred screen-resolution. But is there a way to detect the user's desktop resolution so this can be done automatically? Bjorn |
![]() |
| Thread Tools | |
| Display Modes | |
| |