FoxPro Help and Support - problem with form in project

Author

problem with form in project

Piddepadde

2005-05-07, 8:24 pm

Hi,

I have created a form and it is working fine when executing it from the form
designer.
After creating a project with a menu and calling the form with a do form
command the form shows correctly but I cannot use it... with that I mean
that the objects doesn't respond to mouse clicking.

pls help

/Patrik

Josh Assing

2005-05-07, 8:24 pm

can you post an example?

On Sat, 7 May 2005 16:12:01 -0700, "Piddepadde"
< Piddepadde@discussio
ns.microsoft.com> wrote:

>Hi,
>
>I have created a form and it is working fine when executing it from the form
>designer.
>After creating a project with a menu and calling the form with a do form
>command the form shows correctly but I cannot use it... with that I mean
>that the objects doesn't respond to mouse clicking.
>
>pls help
>
>/Patrik
>

---
Remove x's to send.

Piddepadde

2005-05-07, 8:24 pm

well,

it's difficult to post all that info in a post window and I have not seen
that it's possible to enclose files...?

I have been looking through the forms property a couple of times but can't
see anything that should cause this problem.

maybe it's some commands that are missing in the menu setup code ????

"Josh Assing" wrote:

>
> can you post an example?
>
> On Sat, 7 May 2005 16:12:01 -0700, "Piddepadde"
> < Piddepadde@discussio
ns.microsoft.com> wrote:
>
>
>
> ---
> Remove x's to send.
>

Stefan Wuebbe

2005-05-08, 3:23 am

That does not sound like a "typical issue" to me.
When you say the form controls do not respond to mouse clicks - do
they respond to the keyboard, e.g. <Tab> and character keys etc.?
Does the menu work as expected?
If not, how much CPU time does your.exe consume? What happens
when you run a testForm.scx instead, say with just two empty textboxes
on it? How does your simplified "main.prg" look like?

-Stefan

"Piddepadde" < Piddepadde@discussio
ns.microsoft.com> schrieb im Newsbeitrag
news:597A649B-73D9-4FA0-9E0B- 494ED1154FA8@microso
ft.com...[color=darkred]
> well,
>
> it's difficult to post all that info in a post window and I have not seen
> that it's possible to enclose files...?
>
> I have been looking through the forms property a couple of times but can't
> see anything that should cause this problem.
>
> maybe it's some commands that are missing in the menu setup code ????
>
> "Josh Assing" wrote:
>

--
|\_/| ------ ProLib - programmers liberty -----------------
(.. ) Our MVPs and MCPs make the Fox run....
- / See us at www.prolib.de or www.AFPages.de
-----------------------------------------------------------

Piddepadde

2005-05-08, 7:23 am

Hi,

My main program consists of two lines and looks like this:

SET CONSOLE OFF
DO putte.mpr

I have tried a testform with just two textboxes and implement it in my
project and that form doesn't respond to mouse clicks or keyboard actions
neither.
Maybe there is something severe fault in the setup code in "putte.mpr" (the
menu). Here is the code in menu setup:

PUBLIC m.Done
SET APLABOUT PROMPT 'Om QP-system'
SET EXCLUSIVE OFF
ON APLABOUT WAIT WINDOW "QuickPrint Administration System" + CHR(13) +
"Version 1.0"
SET DELETED ON

and here is the menu cleanup code:

READ VALID m.Done

Note that the cleanup and setup menu code is a copy from my old foxpro 2.5
for macintosh.

/Patrik

"Stefan Wuebbe" wrote:

> That does not sound like a "typical issue" to me.
> When you say the form controls do not respond to mouse clicks - do
> they respond to the keyboard, e.g. <Tab> and character keys etc.?
> Does the menu work as expected?
> If not, how much CPU time does your.exe consume? What happens
> when you run a testForm.scx instead, say with just two empty textboxes
> on it? How does your simplified "main.prg" look like?
>
>
> -Stefan
>
>
>
>
> "Piddepadde" < Piddepadde@discussio
ns.microsoft.com> schrieb im Newsbeitrag
> news:597A649B-73D9-4FA0-9E0B- 494ED1154FA8@microso
ft.com...
>
>
>
> --
> |\_/| ------ ProLib - programmers liberty -----------------
> (.. ) Our MVPs and MCPs make the Fox run....
> - / See us at www.prolib.de or www.AFPages.de
> -----------------------------------------------------------
>
>

Piddepadde

2005-05-08, 1:23 pm

No need for more help in this matter at the moment... have been using the
project wizard to make all the necesary code for me..
Thanks anyway

/Patrik

"Piddepadde" wrote:

> Hi,
>
> I have created a form and it is working fine when executing it from the form
> designer.
> After creating a project with a menu and calling the form with a do form
> command the form shows correctly but I cannot use it... with that I mean
> that the objects doesn't respond to mouse clicking.
>
> pls help
>
> /Patrik
>
>

Piddepadde

2005-05-09, 3:24 am

Thanks Anders,

I did try the read event... but did place before do putte.mpr..
Now I know better.

Thanks
Patrik

"Anders Altberg" wrote:

> ON APLABOUT is ignored in Visual FoxPro for Windows so you can just remove
> it.
> The RED VALID is repalced with READ EVENTS and CLEAR EVENTS. Please not how
> they are placed in the example below. After CLEAR EVENTS execution will jump
> to the line after READ EVENTS if there is one.
> The typical way to launch a simple Visual FoxPro form from a Main.prg goes
> like this.
>
> * Main.prg
> SET EXCLUSIVE OFF && General SET commands can also be added in the LOAD
> event of the form.
> SET DELETED ON
> DO putte.mpr
> DO FORM myform
> READ EVENTS
>
> Add a button on the form with this code in the Click event:
> * Procedure Click
> Thisform.Release()
>
> Add these lines of code to the Release method, and the QueryUnload and
> Destroy events of the form
> * Procedure Release
> IF NOT This.QueryUnload()
> NODEFAULT
> RETURN .F.
> ENDIF
>
> * Procedure QueryUnload
> LOCAL lnResponse
> lnResponse = MESSAGEBOX('Säkert?', 4, '' , 10000)
> IF lnResponse=7
> NODEFAULT
> RETURN .F.
> ENDIF
>
> * Procedure Destroy
> CLEAR EVENTS
>
> -Anders
>
> "Piddepadde" < Piddepadde@discussio
ns.microsoft.com> wrote in message
> news:B6638982-78AD-4697-AA80- 1DB552D4F255@microso
ft.com...
> (the
> Newsbeitrag
> seen
> can't
> the form
> form
> mean
>
>

Sponsored Links