Greetings All
On Jun 29, 2006, at 11:02 AM, Re: BreakPoint at Property Change,
Scott Wagner wrote:
Ok it is when you tab out,. RB 5.5.5 use to give me the same issue.
If it is happening on click you may try another route. i can check
into it.
Scott
On Jun 29, 2006, at 11:58 AM, Chuck Pelto wrote:
On Jun 29, 2006, at 10:50 AM, Scott Wagner wrote:
dim a as string
if myproperty = true then
a = "hello" //Place your breakpoint here. It will only break if
myproperty = true
end if
I've already got something like that in place, as part of my
method to capture changes to text in EditFields. I have a
breakpoint at the a = "hello".... and, despite the fact that I
have not changed the text in the EditField (see previous
communication about Furthermore....), I keep getting dropped into
that If-end if business. Which is why I'm curious as to WHERE the
TextChanged is being called upon. And HOW....
From all I can ascertain, it's being caused by the fact that the
focus is on that EditField when I move from record to record in
the database.
This issue has raised it's ugly head again.
Now that I'm working on getting VCursor approach to the data, what is
happening is that somehow, even if no change to the data in a record
appearing in a form view has occurred, the property of dataChanged is
being set to TRUE and the existing record at position one is being
overwritten with the data of the first record of those found in the
VCursor when.
How do we prevent the boolean property 'dataChanged' from being set
to true when all we are doing is going from one record to another
without changing any data in any of the editable objects?
Does the new release of REALbasic correct this problem? Or is this a
'feature' that I'm not familiar with?
Regards,
Chuck
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
