I am trying to setup a toolbar button to export all my settings to a dated file in my DOpus folder.
I have a button with this function:
Prefs EXPORTSETTINGS=all,alltoolbars,filetypes,filters,images,prefs,toolbars TO "{home}\MySettings{date|yyyymmdd}.dps"
When I click it, the export settings progress bar does it's thing, and then informs me that settings were exported OK, but when I look in the DOpus folder, there's no file.
Actually, I cannot find the file it made anywhere.
I guess I was being hopeful.
/home is listed on page 165 of the DOpus8 PDF manual, under the PATH stuff. I was hoping it would work in the control code squiggle stuff too.
Is there any way I can use something like that, so that it copies the settings to the DOpus folder? I just prefer to keep everything in the folder relating to the app, rather than scattered all over the show.
[quote]I guess I was being hopeful.
/home is listed on page 165 of the DOpus8 PDF manual, under the PATH stuff. I was hoping it would work in the control code squiggle stuff too. [/quote]
Look in your Opus configs directory. Apparently when it comes to exporting prefs, the /home system folder alias does not refer to the directory Opus program directory, rather it creates a "home" subdirectory under the configs subdirectory and in that, are the saved preferences (on my machine anyway).
Ummm... he's just getting confused between external control codes and the builtin Opus aliases. As an alias "/home" should still point to the Opus install folder.
In any event, this actually raises an interesting feature request though. I think it might be rather nice to be able to use some of these aliases in external controls. For instance, the 'My Documents' virtual folder is not always in a %USERPROFILE% sub-folder... mine is on the D: drive. Being able to use something like {/mydocuments} could be handy at times since there's no standard environment var to use (as was the case in THIS situation) as an alternative. When I share certain buttons with friends who have seen the 'Opus light' they have to modify stuff like this to suit their systems.
[quote="JohnZeman"][quote]I guess I was being hopeful.
/home is listed on page 165 of the DOpus8 PDF manual, under the PATH stuff. I was hoping it would work in the control code squiggle stuff too. [/quote] Look in your Opus configs directory. Apparently when it comes to exporting prefs, the /home system folder alias does not refer to the directory Opus program directory, rather it creates a "home" subdirectory under the configs subdirectory and in that, are the saved preferences (on my machine anyway).[/quote]
The issue is with all aliases, not just /home.
I've had this in my issue log for about six months now. (I have about 40 such issues for which I'm still creating test cases, performing detailed analysis on, and verifying if they are still issues in the newest release.)
I believe it is by design, or more accurately by a lack of design. There are only a few references in the User Manual stating that Folder Aliases are supported by a given feature. This leads me to believe, that they are not widely supported throughout all raw commands. However, Jonathan Potter would know if this is the case or not.
I've polished up my issue report (as an enhancement request) and will be submitting it to GPSoftware right now. I will be referring them to this thread: