> > Ok, my own little brainfart for the night... it's early though, so let's see > how this goes. > > for fun I tore off the Icons menu... I never really use it, but I wanted to > see how well it works. Pretty neat. Then, for soem more fun, I tore off my > aterms menu... NEAT! I've now got a quicklaunch menu that takes up barely > any space, and I suspect uses NO more ram. >
yeah the menu already existed, it just was not mapped. > So, the brainfart: what would it take to have these menus show up at > startup, in an already torn-off state, or do we have to create bbmenu? :) > Oh, and I guess if this were an option, it may also be a good idea to have > the menu show up on the main menu, even if it is torn off. > egads no. If you tear it off it should not be there. Keeping that consistent would be a nightmare. As for it being there when you start up that would mean once again storing some kind of blackbox state. Been trying real hard to avoid that. This seems like something better solved by an external app. The blackbox library will have a menu in it so it should be fairly trivial to get what you want.
