> > groupws1 --- frame1 --- groupcw1 --- window1 > > |__ groupws2 --- frame2 --- groupcw2 --- window2 > > > > Let me be more precise. The resulting parent is frame2 in both cases, > > and the resulting manager is the tilling for frame2 in both cases. It's > > window, but the set target object. In your case, the implementation > frame_prepare_manage is called on frame1, which is a wrapper for > mplex_prepare_manage, that forwards the request to the implmentation > group_prepare_manage on groupws2, if that is the current selected > region, etc.
I see. Two solutions come to my mind (besides from modifying the sources which I still not dare to do). One is tweaking the saved session in order to change the current selected region, if this makes any sense at all (if the active region isn't stored there, where is it then? Maybe nowhere?). Inspecting the saved session the only field I suppose that could be related is switchto. But anyway this fix would be too fragile, ready to be broken again after saving the session. The second possibility is to implement a custom clientwin_do_manage_alt hook and do all the work myself, at least for the windows that must reside at nested workspaces. What do you think Tuomo? Any suggestion from the ion savvy? Regards -Carlos
