MyEditBox.SELSTART CHANGES during keypress events, interactive change events and/or programmatic change events when line-feeds (LFs) aren’t paired with (CRs):
E.g., ‘LineFeeds’ [chr(10)] …seem to… insert themselves after every ‘carriage return’ [chr(13)] during *certain* run-time keypress events.
Likewise…COM imports (e.g., oWord values) don’t seem to have paired CRLFs in them, but CRs only.
VFP-9 seems to *prefer* paired CRLFs Chr(13) + Chr(10) :
· For an edit box, the Value property may add line feeds to the text entered in the edit box, providing compatibility with previous versions. For this reason, using the Text property is the preferred method for selecting text with the SelStart and SelLength properties.
Its tricky dealing with chr(13)+chr(10) pairs and .Selstart as they oft elude AT(chr(10),MyMemoValue). i.e., using the .Text property seems problematic, too.
Other *questionable Code* to insert line-feeds for consistent .Selstart handling:
myEditBox.value =CHRTRAN(_screen.activeform.myEditBox.value,CHR(13),Chr(13)+Chr(10))
Any general or specific suggestions concerning .Selstart handling and CRLFs would be greatly appreciated.
CRLF --chr(13)+chr(10)--> .Selstart Dilemmas in myEditBox
AVH
I overlooked that property somewhat and am glad you refreshed my knowledge. The answer may be "that simple".
Also, I'm paranoid that setting it to false may invoke compatibility conflicts (or something) with my X-base routines (written 8 years ago). I'll certainly run a battery of tests on it ASAP and try to respond shortly.
Manrey
.Value = strtran(strtran(.Value,chr(10),''),chr(13),chr(13)+chr(10))
... will help stabilize (per se) complex .value and .selstart behavior problems in myEditbox. I'll try to keep you posted.
Thanks again,Ibrahim Khaleel
with _screen.activeform.myEditbox
.Value = strtran(strtran(.Value,chr(10),''),chr(13),chr(13)+chr(10))
endwith
would prevent chr(10) duplications.
If possible calculate selstart using len() - didn't understand the scenario.
MrHelmut
Tamar