is it closing(unloading) the current screen before the jump, or leave it on(stay in memory?) and switching to another screen?
What's the most efficient way of dealing with this when switching from one another given the fact that my pc has bare minimum horse power.. Or hardly it takes any memory/cpu at all...
I just discovered that when closing a screen, "EXIT" is better command to use than "CLOSE" or am i saying it wrong?
"bare minimum horsepower"....are you short on memory or cpu processing power? Usually on a low spec computer preloading screens into memory when RR starts and keeping them in memory speeds things up--the additional memory usage is small. Background running tasks and services in Windows can make the difference on a low spec computer.
So, what should i use? close||load? exit||load ? or just load?
thanks.. will do..^^
You don't have to add /DISCARDABLE to every screen (while this could work), you can simply set the screenlimit to a low number like 3 or something (minimun is 3 - 1 for main menu, another for a new screen to be loaded and another to provide support to a possibly opened menu).