Still no Open or Browse Folder Dialog. I think its pretty poor,
especially since it whinges profusely about the one that I cobbled
together many years ago.
Cant get any help on the ShellObjects, and there are too many topics of
help that say things such as method blah blah is a method of
tms has a browse folder dialog I think
also, jedi set has one
Rohit Gupta wrote:
Still no Open or Browse Folder Dialog. I think its pretty poor,
especially since it whinges profusely about the one that I cobbled
together many years ago.
Cant get any help on the ShellObjects, and
Reuben asked about Xtra and Indy SMTP sending.
Had a customer with the same problem, so I did some tracing and hunting
and found that if you set the AuthenticationType to atNone, the XTRA
SMTP will allow you to send mail at the moment.
Go figure!
Cheers, Max.
In both D7 and D2007, just on dbedit on one form has a sticky modified
property. Once the value is changed, the modified goes to true and
stays there. Even after post, cancel or scroll, until the form is
killed. Obviously, there is nothing in any event that modifies the
value only the
It's probably because Modified is a property of TCustomEdit and not
related to any data-awareness.
From the Help: Use Modified to determine whether the user changed the
Text StdCtrls_TCustomEdit_Text.html property of the edit control.
Modified is only reset to *False* when you assign a value to
Thats true, however, all other dbedits behave differently - their
modified does get reset when post, cancel or scroll is performed. And
the vcl assigns a value to it on scroll. Looks like I might have to
step through the vcl code to see whats happening. We use the modified
this way all over
Ok, found the full symptom.
Its definitely in D7 and D2007 and its a basic functionality failure.
Once the modified is set due to user edit, it is not reset even when
posted. Its not reset when scrolled either. Unless the new value is
different to the old one. So you keep scrolling and
A possible work around is
IsModified := DbEdit1.Modified and DataSet1.Modified;
I suggest you file a QC report.
HTH
D
On Thu, 30 Aug 2007 16:25:57 +1200, you wrote:
Ok, found the full symptom.
Its definitely in D7 and D2007 and its a basic functionality failure.
Once the modified is set
