Thread: [Announce] Actman activity manager
View Single Post
rantom
2010-09-30 , 18:07
Guest | Posts: n/a | Thanked: 0 times | Joined on
#88
Originally Posted by v13 View Post
I'm sorry but I don't understand your English

I'm using DrLaunch with D.A.M. all the time and I don't have problems. Can you try to explain it again? Perhaps with step-by-step instructions on how to replicate the bug.
It's alright, I was wondering if anyone understood me. So here we go:

1. Create new desktop using actman. Let's call it for now Normal.
2. Create for that specific desktop new shortcuts using DrLaunch. Let's use Phone, Conversations and Web (or Microb, if you have Browser-switchboard installed).
3. Create another desktop with actman and let's call it Portrait.
4. Create new launchers again using DrLaunch, let's use Address Book, Settings and e-mail.
5. Swap between desktops with actman to Normal. You should be now in Normal and you either lose launchers, get Normals mixed up with Portrait or/and vice versa, when switching back to the Portrait.

At least this is the way, that it happened to me. I think it's the same, what you mentioned earlier, that already should be implemented in actman/DrLaunch, but isn't. That's the unique id's. I'm suspecting, that the id's somehow get mixed up and thus you'll see some launchers on wrong desktop.

Originally Posted by v13 View Post
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