From: Ken C. <kca...@st...> - 2009-05-15 15:34:09
|
I've got a task that I'd love to have the panels separate from the rest of the configuration. We've got a layout that will sometimes run with a full CTC implemented on the screen and a dispatcher. Another time, it will not have a dispatcher, but would run ABS and let the trains figure out things for themselves. And another time run with a APB flavor to help keep trains out of each other's way but without a dispatcher. And if we ever get some good documentation or examples of modern CTC panels I'd need to make a new style panel to alternate with the classic CTC we have today. So today I'm keeping a number of panels all in the one file and with instructions to the owner to hide the ones not meaningful to the session being ran. If each panel was just that panel, and the rest of the tables were all in a common file, I'd be happier. But I also know that at some layer some of the tables are meaningful only with the related panel or that having some values in the panel while the rest are in the 'global' file would be nice but extremely messy to say the least. Now for my two bits: Doing the 'X' in the corner should not be considered a delete. That should require something special like a menu selection. Also at save time, if we see that more than one panel exists, and have the same (or null) names, to ask the user if he wants all of them saved or to choose/name the panels. This would also help, I think, some of the people who end up with XX 'copies' of the panel. Granted for this to be meaningful, we'd have to keep a timestamp on a per panel basis to know which one or ones they were editing. -ken cameron Syracuse Model Railroad Club http://www.SyracuseModelRr.org/ CNY Modelers http://www.cnymod.com/ mailto: kca...@st... |