Lisp symbol naming convention

[Emiliano]

I don't understand. The error indicates that you added a \ character to the function name. Are you mistyping \ instead of /? In any case, I recommend to copy/paste from Studio instead of typing.

You are right.
I just tried with a new project and working properly.
However, for some reason in my project I do copy-paste the code from Openstudio, to the lisp file, but the error is issued when loading the lisp file.

[roy_043]

I have just started a new ODCL project and, to my surprise, I actually like the new naming convention. It makes a lot of sense.

But I do notice a small thing (ODCL 8.0.0.6):
The 'Clipboard Copy' code for events still uses "dcl_MessageBox" instead of "dcl-MessageBox".

[owenwengerd]

Thanks for the feedback, and good catch on the function name. I've now corrected the function name for the next build.

[Kerry]

If anyone wants to experiment, I've attached a quick-n-dirty utility to update the symbol and function names in existing odcl projects. I've only done very limited testing with the _MasterDemo sample project. It's not bulletproof. For example, it expects default event handler names in the project, so it will fail to update event handler names if they are no longer default. Load and run UDCL8UPDATE, then select the .odcl files. It will look for and update a .lsp file of the same name, and it will make backups of both files.

Owen,
Thanks for this.
I'm updating about 20 projects for ac2015 ... decided to convert the ODCL event handlers and symbol names as well.
Faultless so far ... a very nice bit of code too.

Regards and Thanks
Kerry

[owenwengerd]

That's good to hear, Kerry. Thanks for the feedback!

[Peter2]

... decided to convert the ODCL event handlers and symbol names as well....

Is it correct that these values are not changed by the lisp and have to be modified manually?

[owenwengerd]

... decided to convert the ODCL event handlers and symbol names as well....

Is it correct that these values are not changed by the lisp and have to be modified manually?

No, the lisp attempts to modify everything -- but only if the original event names are the default forms.

[Peter2]

...but only if the original event names are the default forms.

OK - that's the trick.

Thanks - the lisp works fine  :)

[Peter2]

After a long time I tried the lisp again ...

- I had a code in Version 7 (lsp and ODCL)
- I renamed both lsp and odcl filenames
- in Studio, I used the "Reset symbolnames.." and "reset events". I modified from

Code (autolisp) Select Expand

c:xTB_Font_Check_dialog_OptSystemPlot_OnClicked
to
c:xTB_Font_Check/dialog/OptSystemPlot#OnClicked
- in Lisp-code, I also have the old code

Code (autolisp) Select Expand

(defun c:xTB_Font_Check_dialog_OptSystemPlot_OnClicked (intValue /)
- now I used the ODCL8Upd.lsp

-> Lisp and ODCL where backed up; both get the current filedate
-> but the content of the Lisp was not modified

Did I modify to much?

[owenwengerd]

Just a guess, but you probably broke it by manually resetting symbol names and event names.

[Peter2]

Finally I could not find why it was broken, but I restored my bak-files and the tool made its job without problems. Thanks.