Hey folks,
I'm working on something here at work - that's a bit of a PITA. This
particular client has 2 versions of a system - one looks like FP for DOS
(white letters on Blue screen for most of the system) and runs under
VFP7. The other system is a true VFP system with graphical screens and
runs under VFP9.
I've been now asked to add new functionality - but, to BOTH systems -
and I am attempting to make a screen that will actually run under both
systems. Yes, even the system with the Blue screens has Some graphics
screens. Although - the data look-up routines are Completely different
for Each of them. The VFP7 one just draws on the current screen with @
Say/Gets. Where as the lookups for the VFP9 one pops-up other forms and
views the data within it.
At one point - I actually got the data browsing to work - and the
initial buttons & Text on the Form just disappeared and the Data
browsing was coming up. But, after I added a couple more screen objects
- it doesn't work right - and the data browsing is occurring BEHIND the
existing objects (like Text, a button, a box, etc.).
Now - I figured I could just put all those objects in a Container - and
then make the Container invisible - and do the data browsing. But,
that's a PITA - since, EVERY time I want to edit that Form - I first
have to Edit the Container - then once I am in the Container I can
Add/Edit objects.
So - I am curious. Is there a Numerical way I can just go thru all the
objects on a screen? Like, if the objects are listed in an array or
something? I found something about an Object Hierarchy - I think it may
have mentioned an array - within the online help - but, it didn't go
into any details...
Thanks,
-K-
Senior Developer
Waitex Information System, Inc.
P Save a tree. Don't print this e-mail unless it's really necessary.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
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/289EA162F5642645B5CF64D624C66A140E26059F@us-ny-mail-002.waitex.net
** 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.
On Wed, Jun 20, 2012 at 4:35 PM, Kurt Wendt <kurtwendt@waitex.com> wrote:
> Hey folks,
>
>
>
> I'm working on something here at work - that's a bit of a PITA. This
> particular client has 2 versions of a system - one looks like FP for DOS
> (white letters on Blue screen for most of the system) and runs under
> VFP7. The other system is a true VFP system with graphical screens and
> runs under VFP9.
>
>
>
> I've been now asked to add new functionality - but, to BOTH systems -
> and I am attempting to make a screen that will actually run under both
> systems. Yes, even the system with the Blue screens has Some graphics
> screens. Although - the data look-up routines are Completely different
> for Each of them. The VFP7 one just draws on the current screen with @
> Say/Gets. Where as the lookups for the VFP9 one pops-up other forms and
> views the data within it.
-------------------------
Did he just say @say gets?
Why don't you just set up format files for them instead?
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
_______________________________________________
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/CAJidMYLpKDJXKHN-M=h7udPWueDBnTLW0W397iBz7fiiF-Be1g@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.
Author: MB Software Solutions, LLC
Posted: 2012-06-20 16:50:11 Link
On 6/20/2012 5:35 PM, Kurt Wendt wrote:
> Hey folks,
>
>
>
> I'm working on something here at work - that's a bit of a PITA. This
> particular client has 2 versions of a system - one looks like FP for DOS
> (white letters on Blue screen for most of the system) and runs under
> VFP7. The other system is a true VFP system with graphical screens and
> runs under VFP9.
>
>
>
> I've been now asked to add new functionality - but, to BOTH systems -
> and I am attempting to make a screen that will actually run under both
> systems. Yes, even the system with the Blue screens has Some graphics
> screens. Although - the data look-up routines are Completely different
> for Each of them. The VFP7 one just draws on the current screen with @
> Say/Gets. Where as the lookups for the VFP9 one pops-up other forms and
> views the data within it.
>
>
>
> At one point - I actually got the data browsing to work - and the
> initial buttons & Text on the Form just disappeared and the Data
> browsing was coming up. But, after I added a couple more screen objects
> - it doesn't work right - and the data browsing is occurring BEHIND the
> existing objects (like Text, a button, a box, etc.).
>
>
>
> Now - I figured I could just put all those objects in a Container - and
> then make the Container invisible - and do the data browsing. But,
> that's a PITA - since, EVERY time I want to edit that Form - I first
> have to Edit the Container - then once I am in the Container I can
> Add/Edit objects.
>
>
>
> So - I am curious. Is there a Numerical way I can just go thru all the
> objects on a screen? Like, if the objects are listed in an array or
> something? I found something about an Object Hierarchy - I think it may
> have mentioned an array - within the online help - but, it didn't go
> into any details...
You can use a FOR EACH oObject in thisform.Controls loop to cycle
through. Sounds like you might just need to adjust the ZOrder property
of the controls that are showing behind.
Why you'd use @SAY/GET in VFP7, I don't understand, though.
Another idea is to save the group of controls to a container class as
you said and either toggle the visible property, or I suppose you could
RemoveObject/AddObject to toggle them in use as well. ??
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
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/4FE24593.3050504@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.
Format Files???
As for @ Say/Gets - as I said - it's a WAY OLD system - and I have to
make updates within the system. The new stuff I am building - I am using
a Form and actual controls. But, in order not to ReBuild all the
Procedures - like Lookups - I need to access the OLD Code - which all
works w/@ Say/Gets!
You don't ACTUALLY think that I LIKE to work w/@ Say/Gets - DO YOU???
:-)
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Stephen Russell
Sent: Wednesday, June 20, 2012 5:48 PM
To: profoxtech@leafe.com
Subject: Re: Accessing Form Objects Numerically...
On Wed, Jun 20, 2012 at 4:35 PM, Kurt Wendt <kurtwendt@waitex.com>
wrote:
> Hey folks,
>
>
>
> I'm working on something here at work - that's a bit of a PITA. This
> particular client has 2 versions of a system - one looks like FP for
DOS
> (white letters on Blue screen for most of the system) and runs under
> VFP7. The other system is a true VFP system with graphical screens and
> runs under VFP9.
>
>
>
> I've been now asked to add new functionality - but, to BOTH systems -
> and I am attempting to make a screen that will actually run under both
> systems. Yes, even the system with the Blue screens has Some graphics
> screens. Although - the data look-up routines are Completely different
> for Each of them. The VFP7 one just draws on the current screen with @
> Say/Gets. Where as the lookups for the VFP9 one pops-up other forms
and
> views the data within it.
-------------------------
Did he just say @say gets?
Why don't you just set up format files for them instead?
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
[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/289EA162F5642645B5CF64D624C66A140E2605A0@us-ny-mail-002.waitex.net
** 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.
Why you'd use @SAY/GET in VFP7??? I didn't use it! Its an old, OLD
system - starting way back as Foxbase+ or FP for DOS. I didn't build it
- I only support it - and add new features. Many times - if it's a
completely new screen - I will actually make it graphical as a Form.
The idea of using " FOR EACH oObject in thisform.Controls " sounds
exactly what I was looking for. Any place you can point me to in the
Help files for more specific details? As I've definitely not ever done
that particular type of code before...
Thanks again,
Kurt
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of MB Software Solutions, LLC
Sent: Wednesday, June 20, 2012 5:50 PM
On 6/20/2012 5:35 PM, Kurt Wendt wrote:
> Hey folks,
>
>
>
> I'm working on something here at work - that's a bit of a PITA. This
> particular client has 2 versions of a system - one looks like FP for
DOS
> (white letters on Blue screen for most of the system) and runs under
> VFP7. The other system is a true VFP system with graphical screens and
> runs under VFP9.
>
>
>
> I've been now asked to add new functionality - but, to BOTH systems -
> and I am attempting to make a screen that will actually run under both
> systems. Yes, even the system with the Blue screens has Some graphics
> screens. Although - the data look-up routines are Completely different
> for Each of them. The VFP7 one just draws on the current screen with @
> Say/Gets. Where as the lookups for the VFP9 one pops-up other forms
and
> views the data within it.
>
>
>
> At one point - I actually got the data browsing to work - and the
> initial buttons & Text on the Form just disappeared and the Data
> browsing was coming up. But, after I added a couple more screen
objects
> - it doesn't work right - and the data browsing is occurring BEHIND
the
> existing objects (like Text, a button, a box, etc.).
>
>
>
> Now - I figured I could just put all those objects in a Container -
and
> then make the Container invisible - and do the data browsing. But,
> that's a PITA - since, EVERY time I want to edit that Form - I first
> have to Edit the Container - then once I am in the Container I can
> Add/Edit objects.
>
>
>
> So - I am curious. Is there a Numerical way I can just go thru all the
> objects on a screen? Like, if the objects are listed in an array or
> something? I found something about an Object Hierarchy - I think it
may
> have mentioned an array - within the online help - but, it didn't go
> into any details...
You can use a FOR EACH oObject in thisform.Controls loop to cycle
through. Sounds like you might just need to adjust the ZOrder property
of the controls that are showing behind.
Why you'd use @SAY/GET in VFP7, I don't understand, though.
Another idea is to save the group of controls to a container class as
you said and either toggle the visible property, or I suppose you could
RemoveObject/AddObject to toggle them in use as well. ??
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
[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/289EA162F5642645B5CF64D624C66A140E2605A1@us-ny-mail-002.waitex.net
** 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.
Author: MB Software Solutions, LLC
Posted: 2012-06-20 17:16:21 Link
On 6/20/2012 5:57 PM, Kurt Wendt wrote:
> Why you'd use @SAY/GET in VFP7??? I didn't use it! Its an old, OLD
> system - starting way back as Foxbase+ or FP for DOS. I didn't build it
> - I only support it - and add new features. Many times - if it's a
> completely new screen - I will actually make it graphical as a Form.
>
> The idea of using " FOR EACH oObject in thisform.Controls " sounds
> exactly what I was looking for. Any place you can point me to in the
> Help files for more specific details? As I've definitely not ever done
> that particular type of code before...
>
> Thanks again,
> Kurt
Check out the FOR EACH in VFP Help. It's in there. Likewise, you
should consider putting something in the Init of your classes used in
the form so that you're only registering the controls that you really
want to scan/check/work-with. That avoids you cycling through tons of
controls for no reason at all. There's a pattern name for that but it
escapes me at the moment.
For example, in your txtKurt.Init class method, you'd have the following
code:
if this.lRegister then
thisform.AddToCollectionToCheck(this)
endif
And of course that means you'd have a custom property called lRegister
that you set to .T. if you cared about that object on the screen being
included in your check/work-with-it routine. Then in your frmKurt form
class, you'd have a custom method called AddToCollection that received
the object as a parameter and added it to the form's collection (using
some custom property like oControlsToCheck that was a collection object).
Then when you needed to work with those controls that you really cared
about, you could cycle through that collection. example: FOR EACH
oObject in thisform.oMyControls
This is all out of my head, but I think it should work.
(And yes, I still prefer the old Hungarian notation for form property
names. Insert mockery here! lol)
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
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/4FE24BB5.3080808@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.
On Wed, Jun 20, 2012 at 4:50 PM, Kurt Wendt <kurtwendt@waitex.com> wrote:
> Format Files???
----------------
set format to CustEdit
You youngster.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
_______________________________________________
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/CAJidMYLL-3MVF2yi5oRsf7LptEHwJNygU4-HmyiqcyiuWAbckg@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.
Ha HA HA! You're a funny one Mr. Russell!
At least I'm not TOO Young to go have a Beer! So - when is THAT going to
happen again - when will you be back out to the Island again???
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Stephen Russell
Sent: Thursday, June 21, 2012 9:21 AM
To: profoxtech@leafe.com
Subject: Re: Accessing Form Objects Numerically...
On Wed, Jun 20, 2012 at 4:50 PM, Kurt Wendt <kurtwendt@waitex.com>
wrote:
> Format Files???
----------------
set format to CustEdit
You youngster.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
[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/289EA162F5642645B5CF64D624C66A140E2605A2@us-ny-mail-002.waitex.net
** 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.
On Thu, Jun 21, 2012 at 8:22 AM, Kurt Wendt <kurtwendt@waitex.com> wrote:
> Ha HA HA! You're a funny one Mr. Russell!
>
> At least I'm not TOO Young to go have a Beer! So - when is THAT going to
> happen again - when will you be back out to the Island again???
---------------
I have a MAJOR system conversion first week of July. After that I
will be popping up to get that house cleaned, painted and sold.
Has your # changed? I still have one n my phone from my last trips up.
Same place probably same arrival time for me. Unless they changed the
schedule on me.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
_______________________________________________
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/CAJidMYJg1zWbc2q9Um=EaJUGyH8-SUquddr5G8+_RW9XfLiK_g@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.
Memphis has some neat beers. :)
Al
-----Original Message-----
From: Kurt Wendt
Sent: Thursday, June 21, 2012 3:22 PM
To: profoxtech@leafe.com
Subject: RE: Accessing Form Objects Numerically...
Ha HA HA! You're a funny one Mr. Russell!
At least I'm not TOO Young to go have a Beer! So - when is THAT going to
happen again - when will you be back out to the Island again???
_______________________________________________
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/64C7E12259BB4B528228BBE48DF3BC3C@gslredacer
** 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.