Glenn Posts: 99 19/01/2016

Glenn Posts: 99 OK, the manual has a section on Multi-execution: Multi Execution SyMenu allows more than one running instance from different execution paths. In that way you can use SyMenu from different portable drives at the same time. Overlay unit letter on task icon (see Advanced menu - Options - Startup tab), different fixed colors and different hot keys show up so SyMenu can help you manage a multi session SyMenu system. When SyMenu is executed from the same path of an already running instances, it doesn't execute but it makes that previous instance popup its menu. Is/could there be a way to allow multi-execution from the same path, getting multiple independent instances? No need for the "previous instance popup its menu" feature in that case. Why? Using environment variables, I've been able to customize one SyMenu installation on a read-only, shared, "program" Dropbox folder to work for different projects, with different data in different project-specific Dropbox folders, but the same menu/program needs. And my users will have no problem... they work on one project at a time. So I'm the only one with the problem: I can't keep multiple instances loaded to be quickly responsive to requests for help from different projects. I'm hoping that all the configuration boxes that supply names to the menu entries will be customizable via environment variable or SyMenu variables in some future release, as well as the "Tooltip text on taskbar icon", to go along with the other customizations I could do via environment variables. edited by Glenn on 19/01/2016 edited by Glenn on 19/01/2016

link

---