On first glance I don’t see that a keyboard shortcut is assigned to the new menu command, so it is mysterious.
The sample files provided are saved from FrameMaker 11.
The script contains no error checking if you don’t select any format. And it does not remember the last selection. I guess this means there is an opportunity to improve the solution…
I have updated the samples files to FM10 version.
Thanks for pointing out the missing keyboard shortcut argument in the script,This bug is fixed now. Also regarding the Error Checking, we have ensured that no unwanted changes will happen to the file, in addition to that the user can add further checks.
Kindly download the files now from(https://blogs.adobe.com/techcomm/2011/10/extendscript-of-the-week-change-styles-paracharta ble.html) and try running them.
Your fixes show two things:
The global command DefineCommand is not listed in the ExtendScript documentation (nor in the OMV) but only mentioned with the command DefineAndAddCommand. It seems it should have an entry on its own. Also, DefineAndAddCommand is not listed in the OMV as a method for Menu objects.
The fourth paramater for the keyboard shortcut is listed as required, but apparenatly there was no error message. Will this be fixed either to make the parameter optional with a useful default value or to have the ExtendScript engine alert us?
That seems to have fixed the problem I was having with the letter u.
The ChangeStyles2 download does fix the lower-case u problem. However, ChangeStyles2 still conflicts with the Book Report script.
Also, the ChangeFormat script (similar to ChangeStyle) still has the lower-case u problem *and* conflicts with the Book Report script.
I think both ChangeStyles and ChangeFormat need some pretty serious debugging. They're clearly not safe to run. It's a pity, because they would be useful, but they're clearly buggy.
I am having the same problem typing lowercase u after installing your ChangeFormats script that we discussed earlier. Uninstalling the ChangeFormat script also fixed the problem.Could some common code be causing the same problem for users of either script?
It seems like approximately 10 months since activity on this issue. What is the status?
I see the same symptom here.