Alexander Wagner a écrit : > >> For the "Hotkey-Menu-Items" > >> > >> Tools / Start Engine 1 > >> Tools / Start Engine 2 > >> > >> one could consider probably be something like > >> > >> Tools / Analysis Engine #1 / Select Ctrl-Shift-A > >> / Start Engine 1 F1 > >> > >> Tools / Analysis Engine #2 / Select Ctrl-Shift-2 > >> / Start Engine 2 F2 > >> > > I use such menu nestings on Pocket PC because I have to, > > but on a normal PC screen, I personally prefer more linear > > menus (even if the list is a bit long). That is, I find > > things good enough in their current state. > > Probably I'd move them then anyway up to the other engine > start menues. IMHO they are a bit lost at the end of this > list below the Import function. > Yes, that's right. > Other question: considering we all agree on the above > points, would you do the "moving arround"? At least I for my > part frankly admit that I'd gladly not touch anything really > _inside_ scid. I do not know the internal code good enough > to see wether there could be some effect in an other area as > you mentioned. Though I could of course edit menue.tcl and > commit it. > Well, this is not really "inside" Scid. For me Scid internals are in src/ directory (especially tkscid.cpp). The rest is pure Tcl and really easy to handle. So it is as you want, but for now I spend more time playing chess with Scid + Novag Citrine + FICS, so you could easily change menus if you want things done quickly.
But getting back to CVS I see a Scid2/scid2 directory (I missed it before). Do you confirm it can be deleted ? Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
