Windows - Minimize, Close or leave Open?

[LaRetta]

Hi everyone,

I'm working with multiple windows more in vs. 7 than in prior versions ... much more. I've only been opening new windows over the top of each other, using straight layout switches or closing the prior window as I move a User through their process - never minimizing. But I still occasionally get a User trapped with the error "Can't modify because it's being modified in another window" in a few places where I've forgotten to add a Commit Record/Request. Oh dear.

I'm reviewing my window-handling processes for several reasons (including many new features in vs. 7 that I'm just now figuring out how to take advantage of) But I have a few questions:

1) Does the window'd state make a difference in OS (Windows) and FM-resource efficiency, ie, does Minimized save any resources over an open window? I assume leaving a window open and opening another on top (both maximum window'd size) would be the LEAST efficient. And that minimizing would still use more resources than closing a window. Right?

2) Does size of the window(s) affect resources? BTW, WHAT resources are effected by how I handle my windows? Is it only each User's video RAM or something?

3) If a window is minimized, I assume it would be important to add a Commit Record/Request.

I don't want to stress my User systems nor my host FM solution but, when I have options, I'd like the flexibility (and understanding) of minimizing (if its resource-cost is low enough) or to close a window (spend a bit more design-time) to improve my Solution. I want to do what's best. Can someone explain how this windowing open/close/minimize process might effect my Solution? Thank you.

LaRetta

[RogerJ]

Hi LaRetta. I will briefly try and answer one or two of your questions without going into great detail. Question 1) Yes; Question 2) Yes, it affects system resources. System resources are made up of RAM and Windows Caching (a portion of the HD set aside for holding files/info when RAM is depeleted). An open app takes up more resources than a minimized app. And, it does not use video RAM for this purpose. Video RAM is only used to digest and put on the display what you see.

Roger (PC TECH)

[LaRetta]

Hi Roger,

Thank you for helping me.

"An open app takes up more resources than a minimized app."

I'm more interested in resource-use with multiple windows within FM (or is the principle exactly the same?). I usually open a second window on top but if it will save 'resources' then I'll minimize the prior windows until needed again. Is this right?

Of course sometimes I WANT the prior window still open when I'm opening a tiny window on top but many times the prior window doesn't need to display also. Soooooo, I'm going to minimize all open windows (or close them) as I move around. Is that what everyone else does?

LaRetta

[RogerJ]

Hi LaRetta;

"I'm more interested in resource-use with multiple windows within FM (or is the principle exactly the same?)."

Yes, the principal is the same. An open window takes up more resources than a closed or minimized window. It not only takes up SYSEM resources but VIDEO RAM, as it has to disply on the monitor. If you have a video card with lots or RAM, this will not be a problem (of course depending on how many "daughter" windows you have open), but one with limited video RAM, or a PC that "shares" RAM from the system resources could be a problem.

Use your descretion...