Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
My Program View on AutoResize, Just Chat only!
Message
 
 
To
16/08/1998 09:49:58
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00127133
Message ID:
00127237
Views:
31
Dragan,

>I'd like to turn the thing the other way 'round: we should enable the user to change font size (if not font name too, sometimes) and then appropriately resize the form. The example which needs it badly is right before my eyes at the moment - the UT Navigator. After several hours of reading messages, I awfully hate Arial and just wish I could replace it with Tahoma or something else, and use a bigger size. The form should or should not resize with the font, depending on its purpose and layout.

In the object inspector for the PTF OOP book I added a menu to the editbox that displays the object data that allowed the user to select the font and colors of the editbox. Giving the end user control like that makes sense to me. The UT Navigator could use this kind of feature. The browser allows us to select one of 5 font sizes and that can be very good for large blocks of free flowing text.

The problems of moving things around to handle label size changes is just not worth the effort IMHO. There are dialogs in a couple of places in VFP samples and the class browser where labels are clipped off by controls when larger fonts are selected.

>M$ just loves bitmaps, and it never thoroughly supports the vector graphics. Just try to use foxels. I do (now I may expect lots of comments against this heresy), and I practically don't have the problem of how does an app look in different resoultions - I just change the base fontsize of the forms and all objects on them, and it looks quite readable in any resolution. The general problem with pixel approach is that a form designed in 480x600 may be far too small to read in 1280x1024.

I got very tired of fighting foxels for position and sizes in FPW and Win3 and welcomed pixels. Foxels are better suited for what you are trying to accomplish though. For my last two apps I'm requiring the systems to run at least in 1024x768, it's required by what the enduser needs, and that resolution is much more available than it was 4 years ago. Everything we do is driven by the enduser and we just need to best meet their needs.

>I think we'll see lots of soapboxes 'round here, once we got this started :)

No different than any other thread around here. *g*
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform