http://mbsoftwaresolutions.com/images/problem_with_form.png

I've got a simple SCX form that is getting its WindowType property reset

somehow. It's supposed to be a modal form, but it's not respecting it.

Ideas?

--

Mike Babcock, MCP

MB Software Solutions, LLC

President, Chief Software Architect

http://mbsoftwaresolutions.com

http://fabmate.com

http://twitter.com/mbabcock16

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4BB09390.1020903@mbsoftwaresolutions.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Please check if you have a SetFocus() line in form. SetFocus() triggers the

Show() event of the form and the modality of the form cannot be changed

after showing it.

The easiest way would be to put a set step on in the Show(). It should stop

there and check where it was called from.

On Mon, Mar 29, 2010 at 2:48 PM, MB Software Solutions, LLC <

mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:

> http://mbsoftwaresolutions.com/images/problem_with_form.png

>

> I've got a simple SCX form that is getting its WindowType property reset

> somehow. It's supposed to be a modal form, but it's not respecting it.

> Ideas?

>

> --

> Mike Babcock, MCP

> MB Software Solutions, LLC

> President, Chief Software Architect

> http://mbsoftwaresolutions.com

> http://fabmate.com

> http://twitter.com/mbabcock16

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/f0abce311003290456j5beb8e88t5d2d2c80bac42665@mail.gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Just a WAG, but maybe the form that calls this form is set to a Top

Level Form? If so I don't think you can show a Modal form in a Top

Level form.

Frank.

Frank Cazabon

Samaan Systems Ltd. - Developing Solutions

www.SamaanSystems.com

Referrals are important to us.

If you know of anyone who would benefit from our services, please contact me. We would appreciate the opportunity to work with them.

On 29/03/2010 07:48 AM, MB Software Solutions, LLC wrote:

> http://mbsoftwaresolutions.com/images/problem_with_form.png

>

> I've got a simple SCX form that is getting its WindowType property reset

> somehow. It's supposed to be a modal form, but it's not respecting it.

> Ideas?

>

>

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4BB096A8.8050408@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Frank Cazabon wrote:

> Just a WAG, but maybe the form that calls this form is set to a Top

> Level Form? If so I don't think you can show a Modal form in a Top

> Level form.

>

> Frank.

>

>

>

Top-level forms cannot be modal, forms shown in a top level form can be.

Tracy

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4BB0A0C1.1080102@powerchurch.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

OK, was just a WAG, but just checked it out:

If you have a form set as a Top Level Form, and this calls a Modal form

that is set as an In Screen form, then that second screen will never

show and the code will just run to the next line, which is what may be

happening here. I have a sample project that shows this that I can

email to you if you want to see what I am talking about.

Frank.

Frank Cazabon

Samaan Systems Ltd. - Developing Solutions

www.SamaanSystems.com

Referrals are important to us.

If you know of anyone who would benefit from our services, please contact me. We would appreciate the opportunity to work with them.

On 29/03/2010 08:44 AM, Tracy Pearson wrote:

> Frank Cazabon wrote:

>

>> Just a WAG, but maybe the form that calls this form is set to a Top

>> Level Form? If so I don't think you can show a Modal form in a Top

>> Level form.

>>

>> Frank.

>>

>>

>>

>>

> Top-level forms cannot be modal, forms shown in a top level form can be.

>

> Tracy

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4BB0A8BF.8080308@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Frank Cazabon wrote:

> OK, was just a WAG, but just checked it out:

>

> If you have a form set as a Top Level Form, and this calls a Modal form

> that is set as an In Screen form, then that second screen will never

> show and the code will just run to the next line, which is what may be

> happening here. I have a sample project that shows this that I can

> email to you if you want to see what I am talking about.

>

> Frank.

Thanks, Frank, Tracey, and others. It's not a top-level form. I'm

finding some other unholy behavior so I think I'll just nuke and

re-build this form. It's very small and so terminating this pest is not

a huge loss. I do appreciate the feedback though.

Did you ever get some things in VFP that just can't be explained? This

seems to be one of them. I've got code releasing the form and yet when

I call it again, it's got the same values I had from the original call.

It's almost like it's not residing in memory

as expected (nor releasing as expected). Freaky.

--

Mike Babcock, MCP

MB Software Solutions, LLC

President, Chief Software Architect

http://mbsoftwaresolutions.com

http://fabmate.com

http://twitter.com/mbabcock16

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4BB0AAE8.8050009@mbsoftwaresolutions.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

MB Software Solutions, LLC wrote on 2010-03-29:

>

> Thanks, Frank, Tracey, and others. It's not a top-level form. I'm

> finding some other unholy behavior so I think I'll just nuke and re-

> build this form. It's very small and so terminating this pest is not

> a huge loss. I do appreciate the feedback though.

>

> Did you ever get some things in VFP that just can't be explained?

> This seems to be one of them. I've got code releasing the form and

> yet when I call it again, it's got the same values I had from the original

call.

> It's almost like it's not residing in memory as expected (nor

> releasing as expected). Freaky.

>

>

Mike,

Grigore showed a great example of this behavior a couple years back.

Christof explained it at a SWFox.

Create a class with a property that gets set to SYS(2015), instantiate it a

few times and run it.

Clearing the FoxPro session and restarting it changes the SYS(2015). Or

issuing a CLEAR ALL.

o1 = CREATEOBJECT("myTest")

?o1.sys2015

o2 = CREATEOBJECT("myTest")

?o2.sys2015

DEFINE CLASS myTest as CUSTOM

SYS2015 = SYS(2015)

ENDDEFINE

Tracy Pearson

PowerChurch Software

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/000101cacf44$792f9e10$6b8eda30$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Did I? I forgot, Tracy :) Starting to getting old, methinks....

On Mon, Mar 29, 2010 at 4:33 PM, Tracy Pearson <tracy@powerchurch.com>wrote:

> MB Software Solutions, LLC wrote on 2010-03-29:

> >

> > Thanks, Frank, Tracey, and others. It's not a top-level form. I'm

> > finding some other unholy behavior so I think I'll just nuke and re-

> > build this form. It's very small and so terminating this pest is not

> > a huge loss. I do appreciate the feedback though.

> >

> > Did you ever get some things in VFP that just can't be explained?

> > This seems to be one of them. I've got code releasing the form and

> > yet when I call it again, it's got the same values I had from the

> original

> call.

> > It's almost like it's not residing in memory as expected (nor

> > releasing as expected). Freaky.

> >

> >

>

> Mike,

>

> Grigore showed a great example of this behavior a couple years back.

> Christof explained it at a SWFox.

>

> Create a class with a property that gets set to SYS(2015), instantiate it a

> few times and run it.

> Clearing the FoxPro session and restarting it changes the SYS(2015). Or

> issuing a CLEAR ALL.

>

> o1 = CREATEOBJECT("myTest")

> ?o1.sys2015

> o2 = CREATEOBJECT("myTest")

> ?o2.sys2015

>

> DEFINE CLASS myTest as CUSTOM

> SYS2015 = SYS(2015)

> ENDDEFINE

>

>

> Tracy Pearson

> PowerChurch Software

>

>

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/f0abce311003290642v66358f2bm85d5c68603d411e0@mail.gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

Grigore Dolghin wrote on 2010-03-29:

> Did I? I forgot, Tracy :) Starting to getting old, methinks....

>

> On Mon, Mar 29, 2010 at 4:33 PM, Tracy Pearson

> <tracy@powerchurch.com>wrote:

>

>>

>> Mike,

>>

>> Grigore showed a great example of this behavior a couple years back.

>> Christof explained it at a SWFox.

>>

>> Create a class with a property that gets set to SYS(2015), instantiate

>> it a few times and run it. Clearing the FoxPro session and restarting

>> it changes the SYS(2015). Or issuing a CLEAR ALL.

>>

>> o1 = CREATEOBJECT("myTest")

>> ?o1.sys2015

>> o2 = CREATEOBJECT("myTest")

>> ?o2.sys2015

>>

>> DEFINE CLASS myTest as CUSTOM

>> SYS2015 = SYS(2015)

>> ENDDEFINE

>>

>>

>> Tracy Pearson

>> PowerChurch Software

>>

Grigore,

You're specific example was how a second form would have artifacts on it,

something with a textbox. You might have presented it to me off this list,

but I recall it was you that showed it to me. Later that year I saw Christof

present the sys(2015) behavior at SWFox.

Tracy Pearson

PowerChurch Software

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/000201cacf49$316f7230$944e5690$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.