[SOLVED] Strange return in autocad with EditChanged in TextBox Multiline string

Hello Owen,

Again me !  ;D

I needed to use TextBox control with "8- Multiline Sting" Filter.

I use event "EditChange" to know if something append in this field.

I get these string in AutoCAD when multiline are enter in control :

("_>  ("_>  ("_>  ("_>  ("_>  ("_>  ("_>

As many cariage return (enter) it send ("_>"

thanks.

Best regards.

Did you miss a closing quote in your OnEditChanged event handler?

author=owenwengerd link=topic=891.msg4429#msg4429 date=1251411863 wrote:
Did you miss a closing quote in your OnEditChanged event handler?

Not at all !

Just use example code from editor ...  ;D

I verify my code, and make a test ...... and reproduce it twice !

Thanks

Best regards.

I cannot reproduce the problem. Please post a sample along with steps to reproduce it.

author=owenwengerd link=topic=891.msg4432#msg4432 date=1251464021 wrote:
I cannot reproduce the problem. Please post a sample along with steps to reproduce it.

Here is my example ....


(load "d:/textbox_multiline.lsp")
c:test


Enter some lines in textbox1 and see in autocad command line what append ...  ;)

Nothing else to say ....

Thanks

Best regards

Thanks. The problem occurs only when Event Invoke is 'Asynchronous'. This is now fixed for the next build.

author=owenwengerd link=topic=891.msg4436#msg4436 date=1251474286 wrote:
Thanks. The problem occurs only when Event Invoke is 'Asynchronous'. This is now fixed for the next build.

Thanks  ;)

Hello owen,

Now the event "EditChanged" is not called !

and, when i come back in autocad command line, these strange string appear before autocad prompt, and i can't enter any order !

Thanks !

Best regards.

I don't see any problem with OnEditChanged. I did notice that OnUpdate incorrectly calls OnEditChanged; that is now fixed for the next build.

Hello owen,

Sorry to insist !

ok, when i set textbox event invoke  to synchronous, OnEditChanged event is call.

When i set textbox event invoke to asynchronous, never be called !

Hope this help you .

Thanks,

Best regards.

I assume this is also due to the bug with escaped quotes in asynchronous events that receive string arguments, so it should be fixed in the next build.

author=owenwengerd link=topic=891.msg4466#msg4466 date=1251825023 wrote:
I assume this is also due to the bug with escaped quotes in asynchronous events that receive string arguments, so it should be fixed in the next build.

Work fine with new ARX, ether asynchronous or synchronous .

Thanks for your job .

Best regards