226
Living Room / Re: 64 Bit OS - When to Switch ?
« Last post by vlastimil on July 08, 2011, 10:31 AM »@vlastimil I disagree that this is a actual issue affecting many end users.-justice (July 08, 2011, 04:29 AM)
maybe not many, but it affects some users/applications
http://stackoverflow...-bit-in-net-winforms
I never ran into this issue, and I do not believe it is any problem. If anything, window handles (which are the things you are referring to, I believe) have only gone up in the supported amounts, and the last time a scarcity of that resource was an issue was back in the W9x days. If you refer to the Z-order that defines what is drawn on top of what, I do not believe there is any sane limitation on that either.
I dare say, if you run into issues with the amounts of resources Windows makes available for a specific purpose, you are abusing that as a developer and without a doubt can find a more suitable solution. For example, there are tons of windowless controls that are considered lightweight because they do not use any Windows resources, and instead co-opt the help of their parent control that do have a handle.-worstje (July 08, 2011, 07:54 AM)
This is not about the number of window handles. It is about recursive window message processing - parent window receives WM_SIZE, sends WM_SIZE to its children, etc. (it is more complex in reality, there are more messages being sent)
Even native Windows controls use this kind of aggregation. List box has a Header control as its child, Combo box has an Edit box as a child. A toolbar can host a combo box (with an edit box inside) and be hosted in a Rebar. These are 4 levels of depth and we are still talking just about a toolbar. That toolbar is hosted within the application frame. Now add a tab or a splitter control and the depth grows. The depth limit on 64-bit windows is pretty shallow, like ~12. If you use .net winforms and make a tab/splitter hierarchy, you can experience this yourself.
Window-less controls can help, but it is a pain to use them. They are not the easy-to-use blackbox that a window is. But this is not the main issue here. The fact that the 64-bit system is worse than the 32-bit one in this aspect. And there may be more catches like this one.
The memory: first, determine if you need it. Do you want to work with really hi-res video or a large database? By all means get a lot of memory, 64-bit Windows AND a 64-bit edition of the software. Do you just browse the internet, use office and play games? You'll be better off with 4GB and 32-bit for the next few years.
Also...there are artificial limits on how much memory a 64-bit Windows allows you to use http://en.wikipedia....ysical_memory_limits

Recent Posts
.
.