Skydiver, on 02 July 2012 - 03:12 PM, said:

I never code struct's with hardcodes values inside.

I don't use them much at all to be honest, as I was told to avoid them unless you really need them as they add unnecessary complexity.

I think you should be using a class with a read only field (getter without a setter) if that's your intention.

I never use struct's with hardcoded values inside.

http://www.dotnetper...ct-versus-class

Having multiple cores means you have to wait less time between each operation.

Think of the route to your CPU as a pipe of a fixed width and data must more through this queue in single file, one item and a time creating a queue.
So the data behind, must wait for the data in front to be processed before it's its turn.

Adding a second processor means that there are now two units which can perform the processing and there are two queues, so data can move through faster.

Also, most of the time when you have a "dual core" this doesn't mean you have two CPUs. It means you have "hyper-threading" multiple threads (pipes, in my analogy) going to a single processor.
Which increases the amount of queues, again, bringing about a performance gain although to a less amount as you don't have twice the processing power.

This is not a 50% increase due to limitations from other hardware, and the inability of a lot of software to utilise multi-core processing correctly. Especially with hyper-threading, as programs that aren't designed to work with it only see the pipes and treat it exactly the same as two CPUs (Which it isn't).

Also, GHz isn't a measurement of processor performance - a faster clock speed != faster CPU. Things like the CPU architecture make so much difference.

Quote

In this example the benefit the 16 core computer would have is it would perform this same operation in a similar speed, assumption as it depends on a lot, the real difference would be it wouldn't tax this system anywhere near as much.
So, for example, you could perform 8 operations simultaneously in the same time it would take for the dual-core to perform 1.

I think you've just disabled the feature that was displaying an effect the problem was causing, as I can't really see how having Visual Styles enabled could cause this.

Visual Styles are the themes for Windows, so having them enabled basically means the window colours and effects are set by the users Windows Theme choice.

...If it seems to all work though, I guess it's not important.

Please post the code you are having trouble with.