Thanks, Tracy. I've looked into it a bit, but not sure I really want all
those gyrations since the DE that now ends up on the form is ReadOnly. I
understand why that is, but it presents a different set of challenges.
Fred
On Thu, Mar 27, 2014 at 2:25 PM, Tracy Pearson
Fred Taylor wrote on 2014-04-02:
Thanks, Tracy. I've looked into it a bit, but not sure I really want all
those gyrations since the DE that now ends up on the form is ReadOnly. I
understand why that is, but it presents a different set of challenges.
Fred
Fred,
You are able to
Yeah, that does work, but you can't tweak a DE for a form, say for if it
needed just an additional table, you'd have to subclass a new DE with the
table. Think I may just go the programmatic route and build the DE on the
fly.
Fred
On Wed, Apr 2, 2014 at 2:45 PM, Tracy Pearson
Is there a way to stop datasession changes? Really annoying when debugging
and it's on the wrong table. Usually I put the stop on a table change to
make sure. I agree that the debugger is great except for the crashes. And
that seems to be when I put a watch on a parameter.
Al
-Original
At 15:03 2014-03-26, Allen pro...@gatwicksoftware.com wrote:
I'm finding the debugger quite annoying. For example it stops with a
different table than it should. It changes it. Often does not halt on a
break yet will with a set step on. Often falls over and causes 05 issues, I
think when a break
At 15:09 2014-03-26, Richard Kaye rk...@invaluable.com wrote:
I can't say I've had those kinds of stability issue with the
debugger itself. You do have to be aware of datasession changes,
etc. and sometimes it seems to hang on to breakpoints but it's an
otherwise invaluable tool. I watch the
I agree that going out of scope is a pain. I do wish it ignored the var
doing that. Would have been a good fix.
Al
-Original Message-
I have not had problems with the debugger changing things (except for
causing extra events to fire). It has been a bother when what I need to
If it a consolation, VS is as bad with web services. Well complex ones
anyway.
I'm having VFP dll issues at the moment and debug is useless for that.
Al
-Original Message-
I did a bit of Web dev for a possible project, and yes, I most
definitely agree with you on that.
From: pro...@gatwicksoftware.com
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
Date: Thu, 27 Mar 2014 08:10:09 +0100
Is there a way to stop datasession changes? Really annoying when debugging
and it's on the wrong table. Usually I put the stop on a table change to
make sure. I
On 03/27/2014 03:48 PM, Dan Covill wrote:
A confession: I never, ever used the datasession 'feature', because I never
figured out what it was doing.
It provided one way for a form to be open multiple times, each with it's
own local database and table state (buffered records, record pointers,
: A Use for OKL
Date: Thu, 27 Mar 2014 08:10:09 +0100
Is there a way to stop datasession changes? Really annoying when
debugging
and it's on the wrong table. Usually I put the stop on a table change to
make sure. I agree that the debugger is great except for the crashes. And
that seems
Fred Taylor wrote on 2014-03-27:
Dan,
Data Sessions are indispensable, however the DataEnvironment is somewhat
of
a feature that I find less than useful, especially in an environment that
you need to switch entire pathing for multiple companies to their
respective data tables.
At 13:17 2014-03-25, Richard Kaye rk...@invaluable.com wrote:
You're right, Gene. Nothing can cover all situations. But any
logical condition will do. Two generic strategies I've used when I
don't necessarily have some well-defined condition are:
ASSERT .F. MESSAGE [Debug now?]
And
ASSERT
As long as you have a wait state to accept the keystroke. :-)
--
rk
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene
Wirchenko
Sent: Wednesday, March 26, 2014 1:26 PM
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
I was using
a wait state to accept the keystroke. :-)
--
rk
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene
Wirchenko
Sent: Wednesday, March 26, 2014 1:26 PM
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
I was using a variety of sledgehammer
At 13:38 2014-03-26, Richard Kaye rk...@invaluable.com wrote:
As long as you have a wait state to accept the keystroke. :-)
Good point.
I have exactly that though. The trouble I have had is when
using the debugger causes other events to fire. This is not fun when
the code works
At 14:28 2014-03-26, Gianni Turri gianni...@gmail.com wrote:
Using
_vfp.AutoYield = .t.
the keyboard is polled between code lines instead that only at a wait state.
Thank you. I would not have thought of that since it is one of
those commands that one does not think of if one has not
PM
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
I have exactly that though. The trouble I have had is when using the
debugger causes other events to fire. This is not fun when the code works when
using the debugger, but not when not.
[snip]
Sincerely,
Gene Wirchenko
I'm finding the debugger quite annoying. For example it stops with a
different table than it should. It changes it. Often does not halt on a
break yet will with a set step on. Often falls over and causes 05 issues, I
think when a break when changed is used with a property. Didn't use to do
all
to effectively
troubleshoot stuff... That's a nightmare, imho. :-)
--
rk
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Allen
Sent: Wednesday, March 26, 2014 6:04 PM
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
I'm finding the debugger quite
At 04:33 2014-03-24, Richard Kaye rk...@invaluable.com wrote:
You might want to look at using ASSERTS. Very useful for triggering
the debug process in a controlled way.
If you can define an expression that covers the
case. Sometimes, the condition is higher-level than VFP.
[snip]
[mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene
Wirchenko
Sent: Tuesday, March 25, 2014 3:01 PM
To: profoxt...@leafe.com
Subject: RE: A Use for OKL
At 04:33 2014-03-24, Richard Kaye rk...@invaluable.com wrote:
You might want to look at using ASSERTS. Very useful for triggering the
debug
You might want to look at using ASSERTS. Very useful for triggering the debug
process in a controlled way.
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene
Wirchenko
Sent: Friday, March 21, 2014 5:59 PM
To: profoxt...@leafe.com
Subject: A Use
Dear Vixens and Reynards:
OKL is often reviled, but I just found a very good use for it
in debugging.
I am debugging a .BeforeRowColChange method. I want to
single-step through the method to find the error. The problem is
that I do not want to single-step through it unless it is
24 matches
Mail list logo
