Well, that's a bug of DrLaunch. Since I've also written DrLaunch, I took care to include support for actman. To do this I used a combination of the current activity and the widget id to uniquely identify an instance (and thus its settings). This way, every widget instance is unique even between different activities (which would otherwise be not).

The support for actman is optional in DrLaunch since actman may not be installed, so if actman is not installed it will just use the widget id. When you installed actman, DrLaunch started using a different widget id which did not have your original settings. When you restarted your desktop, DrLaunch failed to load its settings because of the different unique-id and it started with the default settings.

I remember adding code for supporting the non-actman -> actman transition but either I remember wrong or it failed. Either way, this is a problem of DrLaunch

I'll give it a try. This is something I wasn't aware off, so I'll test it. Thanks for noting it!