There are some prefs that will be lost if import .dps:
- I configured background-images. I always have to reassign them.
- Datatypes > All folders: I created a contextmenu like "Play folder with Winamp". It's lost if import settings.
The second point is very bothering. Do I have to export registry-entries to save contextmenus made in DOpus?
I've had similar experiences.
My "Play/Enqueue with foobar"-menu items disappeared when importing settings from a file on a new install. It was imported with the correct executable path, but was imported as the wrong type; "Run as application" instead of "Run as Opus function". Thus is disappeared from my context menu as I tell DOpus to filter out all non-Opus functions.
I've actually seen similar "forgetfulness" in DOpus before, when adding functions to a File Type. You add a new action as a "Opus function", but as you press OK, it saves it as a "Normal function" (Run as application). You then have to delete it and try and add it again, as you cannot change an action from "normal" type to "Opus" type. It usually works the second time around (and no, I'm not adding it wrong the first time ).
Any thoughts? Anyone recognise this behaviour?
I've seen it lots of times, but it seems to be happening by random, so I haven't had the energy to look into it and send a bug report. But if more people are having problems with action types going haywire, maybe there's a bug somewhere..?
Ok, tried some things:
-
Images: I deactivated importing images and DOpus leaves the image-settings that were choosen before. If I activate it again, DOpus overwrites the images with saved one, but only with defined one in the predefined image-groups (separate added images will be ignored and standard colorsettings will be used instead)!
-
Datatypes: Entries in menu "datatypes > datatype-groups" will be saved correctly. Entries in "datatypes > DOPus datatype-groups" will NOT be saved.
As a little work-around you can export your DOPus datatype-groups from registry. Worked for me.