Not sure I'd call this a bug, but it seems like a bad design
decision. When you're in the Script Editor, you have a whole
different set of menus than when you're in the main IDE. I just
always took it for granted that that was "the way things are" and
I've gotten used to using Command-S (except, of course, when that
breaks for God knows what unfathomable reason) and going merrily on
my way. Come to think of it, if the menu's command-key equivalent
works and the item is dimmed out, that does feel like a bug so I
agree, Jacque!
Dan
On Aug 24, 2005, at 1:46 PM, J. Landman Gay wrote:
Jon wrote:
I often find myself editing a Script, Applying the script, and
then immediately going to the main Rev menu to do a Files/Save.
Unfortunately, Save is grayed out if I have a Script Editor open/
active. I have to click on the main Stack in order to get the
menu to allow me to do a Save.
Any idea whether this behavior is necessary or not? I don't
understand, technically, why one would not (or should not) be able
to be do a Save while the Script Editor is active.
If no one can explain why this behavior is necessary, I may BZ it.
You can probably Bugzilla it, since the dimmed item sounds like a
bug. However, in the mean time, you can just type Control-S in the
script editor and it will bring the stack forward, save, and then
toggle the script editor to the front again. Or at least it does
that on a Mac.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
