When this happens, it's best to divide the classes up into multiple classes. However, sometimes that's not possible. The current version of C# does not support this, but the next version will support it.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi
There is a problem with this. If I use 333 as the text, it goes fine, but do I use 1111111191, the caret is being placed maybe 5 - 10 pixels from the last 1. It seems to me that the size of 1 is measured larger than it actually is.
What can I do about this problem? Am I attacking this problem from the wrong angle? Is there any implementation already made?
After a long time I'm thinking to deal with programming again.
I want to write a math application(many graphics) with incredible many calculations in a little time so I must manipulate numbers(integer and real) as fast as possible.
I remember in "TURBO C" and old processors for fastest access(about two times faster) to integer numbers they should be declared as register and no more than two names otherwise the rest would be ignored.
In nowdays what about in "C#" and huge L2 cache memory of powerfull processors?
Has this capability to do with L2 cache?
I mean can I use L2 cache exclusively for frequently used variable names?
>I want to write a math program with incredible many calculations in a little time so I must manipulate numbers(integer and real) as fast as possible.
Seriously, if you want to write an app that does serious number crunching, maybe you'll save some development time by targeting a language that was designed and built to do serious number crunching. C# and .NET were designed to implement business applications. That's not to say they couldn't be used for math-type apps, but managed code doesn't lend itself very well to doing intensive work like that.
Also, if you want to write this app in C# (or any other language for that matter), I would just write the app in the simplest, most obvious way possible. Don't worry about performance right off the bat. Only when you have a working app do you worry about how quickly it runs: time it, profile it, and optimize it then. Trying to tune an application that isn't written yet is an exercise in building castles in the air.
Program Manager, C#
This posting is provided "AS IS" with no warranties, and confers no rights.
Last Visit: 31-Dec-99 19:00 Last Update: 27-Jan-23 21:26