Is there any way to make the OpenDCL events invisible when typing in a command in Autocad 2014? If I remove the "c:" from the defun's then they disappear however then the dialog events no longer appear to work.
Any info would be helpful.
Thanks
Scott
Quote from: Syncmas on September 26, 2013, 11:38:45 AM
....If I remove the "c:" from the defun's then they disappear however then the dialog events no longer appear to work.....
Have you also removed the "c:" from the events itself?
Good question. I don't know of any programmatic way to hide lisp defined commands, but it sure doesn't make sense for them to be included in the auto-complete list.
I still have not found a way to get these events from appearing. Just curious if anyone else has a way around this yet?
Unless all of the commands are converted to sub-functions, it won't happen. I considered many possibilities even tripping the atoms-family with no luck. I'm wondering what is the issue with ODCL calling subs instead? (Of course it'll have to be an internal change.) Maybe a future version since "AutoComplete" isn't going away; but then again, what would happen to backward compatibility?..
Sounds like a fleeting objective. just my 2ยข :-X
For synchronous events that are never called asynchronously, there is no technical reason why the c: prefix would be required, but I don't think there's any reliable way to call asynchronous events without initiating them as commands (which obviously requires the c: prefix). I'm assuming that you guys are dealing with modeless forms where it's not possible to fire events synchronously. For modal forms, you can just set the event handler function symbols to NIL after the form is closed.
Hi, Owen.
I was also wondering about that, why 2014 ACAD shows up the Open DCL "c:event command" strings.
You mean there is no way to hide it, when using modeless form?
Quote from: khann on February 24, 2014, 04:24:27 PMYou mean there is no way to hide it, when using modeless form?
If they chose to, Autodesk could expose a way to filter the list. The only other solution I can think of is to somehow push all event handler calls through a single command, but that would require major changes.