Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Form becomes inactive
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00872123
Message ID:
00872144
Views:
27
Matt,

FWIW, No one could ever pay me enough to go back to coding in FP2.x. *g*

Are you running converted forms or brand new started from scratch VFP forms?

What code is in the commandbutton.Click() that you are talking about in the second paragraph?

You can adjust the .Height and .Width properties at designtime from the property sheet. While it's somewhat annoying to not be able to drag the size there is a simple solution. Set the BorderStyle in the form.Init(). This lets you freely size it at designtime and when it runs the user can't size it. Although in VFP8 (it's been announced that VFP9 has some much cooler resize features built in) it's pretty easy to allow your forms where appropriate to be resizeable and resize the controls along with it.

>We have an application that sporadically appears to freeze, but what is happening is that the current form becomes inactive. The previous form receives focus (our control centre) and this can be dragged about, and only some of the functions work, but the screen that should still be active just makes an annoying "plunk" sound when clicked but doesn't respond and can't be dragged, closed etc.
>
>A specific example which just occurred is that a report was produced from a button on the current form, followed by a "messagebox" as the last command in the sequence initiated by the button to advise that the report/s had been produced. Control should then return to the current form, but instead seems to pass back to the previous screen (partially, as stated above). I have coded a command window which I can access via hotkey combination and issue formname.release which causes the application to close...
>
>I'm beginning to have serious doubts about the stability of VFP8 and some of the nutty stuff (like not being able to dynamically resize a dialog form in the designer without first changing it to resizable, adjusting size then changing it back to dialog!), uppercase F2 keys??, and a bunch of other irritations. I think 2.6 was way better and simpler (except for the few bugs it still had and problems with HP printer drivers).
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