There's no way to automatically turn a "Rename PRESET=xyz" command into the equivalent Rename command that specifies everything in the command instead of refering to a preset, but it's easy enough to do manually in most cases.
Are you having problems converting any particular options?
Thank you for your reply. I am not having problems at all. I have successfully used the Rename button and screens to build the rename command I wanted to issue. I then wanted to build a Rename button that did exactly the same thing using RAW commands only.
I really asked this question to improve knowledge of Directory Opus. Although I purchased Directory Opus 8 last September, this is the first time that I have had the time to sit down and play with the product properly. I wanted to initially use the supplied buttons and screens to build all of the commands/functions that I need, then look at the raw commands so I could learn the syntax. Directory Opus makes it extremely easy to set up Rename buttons that do exactly what I want. But it would be really useful if I could see the actual Raw commands it sets up under the covers. I believe that this would make it much easier for me to learn the syntax of the various Raw commands (as a newish user) so that I can start to do even more complex stuff.
I believe that if I could see the underlying Raw commands associated with the buttons I build, it would make using/learning the product that much quicker and easier.
With rename presets, though, a preset does not generate a raw command which is then run. Instead a preset will directly set the options the same as a raw command would. So, while you can more or less do the same thing with rename presets and raw commands, they are both independent things and neither form is translated into the other before being run.
(Of course, the raw commands can refer to presets, but that's a side issue.)