Prevent user pasting CR LF

[hua]

Guys,

I occasionally come across in user's data, CRLF (\r\n) tacked at the end of the field value. Below is one such example


I suspect this occur when user copy and paste from documents such as Word or Excel into my FWH program. Is there any way to prevent this from happening?

TIA

[James Bott]

Maybe use bChange to use a codeblock to strip out and CR and LFs?

James

[Armando]

Hua:

At the moment I do not remember if there is a function to remove the CRLF,
any way you can try the following sample code:

Code: Select all  Expand view

cString := "This is a string + CRLF " + CRLF

MsgInfo(LEN(cString))
cString := STRTRAN(cString,CRLF,"")
MsgInfo(LEN(cString))
 

Please use this code in the VALID clause of your GET

Regards

[James Bott]

I just found that there is a bPaste codeblock you should be able to use also. Unlike bChange or VALID this codeblock will only be called when pasting.

James

[hua]

Thanks Armando and James.

Armando, I don't think it's practical to modify the source to sanitize input at VALIDs. There are a lots of them because ideally all gets should strip any formatting information.

Thanks for pointing out bPaste James. Maybe I could try to customize TGet so all of my gets will sanitize pasted input using bPaste.

Antonio, I hope FWH can come up with a built-in mechanism to strip-off formatting when text is pasted. Much like how a text editor behave where whatever we pasted only the text sticks not the control characters/formatting.

[James Bott]

Hua,

Antonio, I hope FWH can come up with a built-in mechanism to strip-off formatting when text is pasted. Much like how a text editor behave where whatever we pasted only the text sticks not the control characters/formatting.

I think it would have to be optional, since sometimes we want control characters and formatting, such as in multi-line text fields. It could be complicated in apps where you want both behaviors.

James

[Armando]

Hua:

I agree with you when there are many GETs , it occurs to me to make a global function
with my suggestion and in each GET call that function.

Regards

[James Bott]

Armando,

Depending on how many GETs you have, it would probably be easier to modify the TGet class by adding a CLASSVAR to trigger stripping the CR and LF characters. A CLASSVAR is like a static, so if you default it to .t. then all GETs will be stripped. If you need a GET to not be stripped, then you just reset the CLASSVAR before entering the GET and reset it again when leaving the GET. There would be no changes to your app code--you only have to link in the modified GET class.

The only issue is when the stock TGet class is modified, then you need to move your changes to the new class.

James

[Armando]

James:

Armando,
Depending on how many GETs you have, it would probably be easier to modify the TGet class by adding a CLASSVAR to trigger stripping the CR and LF characters. A CLASSVAR is like a static, so if you default it to .t. then all GETs will be stripped. If you need a GET to not be stripped, then you just reset the CLASSVAR before entering the GET and reset it again when leaving the GET. There would be no changes to your app code--you only have to link in the modified GET class.
James

You're absolutely right.

The only issue is when the stock TGet class is modified, then you need to move your changes to the new class.
James

This is why I do not like to modify the clases, but it depends on each developer


With best regards

[James Bott]

Armando,

Another option is to create a TGet subclass. Then you would need to modify the FIVEWIN.CH file to call that subclass rather than the TGet class.

When a new version of FW comes out the only change you would have to make is to the CH file and probably that change would only be one word--the name of the TGet subclass.

James

[Armando]

James:

I think It's the best option.

Thanks a lots