Bob Warren wrote:
Richard Gaskin wrote:
(A wealth of information - See his post!)
Thanks. :)
Regarding:-
"I don't know that the new message is needed, but I agree that a way to
have a menu item which closes a stack and re-opens it fresh (to trigger
the opening sequence of messages -- preOpenStack, preOpenCard,
openStack, openCard, etc.) would be handy."
- There are of course other ways in which this could be done, as I have
suggested in the past. For example, saving the current project itself as
a temp file and then provoking a revert at some point. However, it
strikes me that the idea of independent compiling and shelling would be
particularly easy to implement, avoiding the kinds of modifications
which might lead to bloat and further instability of the IDE.
I'm not sure I follow: what constitutes "independent compiling and
shelling"?
Maybe I'll put it in my IDE. :)
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.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