|
The caveat to using the decimal type is that unlike floats it's not implemented in hardware directly and is significantly slower to use as result. This isn't a problem if you're doing light computations, but if you're doing larger amounts of calculation working within the limits of native floating points may be needed.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
To further and agree with your statement, decimal should only be used for financial or monetary values in .NET. At least that is my rule of thumb.
Need software developed? Offering C# development all over the United States, ERL GLOBAL, Inc is the only call you will have to make.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway
Most of this sig is for Google, not ego.
|
|
|
|
|
To really jump in on the good vibes agreeance bandwagon, if the 96.1000001 is annoying you, then you really should be using an appropriate format string when you display it to the user.
|
|
|
|
|
Additionally to what the others already said, it's not safe to compare two float values like this:
if(float1 == float2)
Instead, for floats you should rather use something like this:
if((float1 - float2) < delta)
where delta can be a small number like 0.001.
regards
modified 12-Sep-18 21:01pm.
|
|
|
|
|
Hello!
I'm currently fiddling around with pixel drawing on Windows Forms using VC# Express, and I'm crashing into this problem.
I want to try and set up Bitmap which is configured to 8-bit colours and make use of a ColorPalette object, but I'm having slight trouble how to set this up, as I'm quite new to C# compared to C/C++.
Here is my current code:
<< in the namespace/class: >>
Rectangle pixRect;
BitmapData pixData;
Bitmap pixBitmap;
Color[] myCols;
ColorPalette myPal;
<< in the form constructor: >>
unsafe
{
myPal = new ColorPalette();
pixBitmap = new Bitmap(50, 20, PixelFormat.Format8bppIndexed);
pixBitmap.Palette = myPal;
myCols = myPal.Entries;
pictureBox1.Image = pixBitmap;
pixRect = new Rectangle(0, 0, pixBitmap.Width, pixBitmap.Height);
myCols[0] = Color.FromArgb(255, 0, 255);
}
I can actually tell that "myPal" ColorPalette is no assigned, occording to a compile warning message, but there doesn't seem to be a ColorPalette constructor.
Any suggestions ?
Thanks in advance,
OCrowley.
|
|
|
|
|
OCrowley wrote: Any suggestions ?
Not sure. Do you have something against reading the documentation?[^]
led mike
|
|
|
|
|
Well, I was expecting a more informative answer than just a LINK TO ANOTHER MSDN PAGE, but yes I have read that and yes I find it misleading that it doesn't show an example of how to set one up, hense why I asked here. kthnx.
Anyone else? and please, don't bite my head off.
|
|
|
|
|
OCrowley wrote: Well, I was expecting a more informative answer
You were expecting? Really? Wow, perhaps a more informative initial post might garner that. Perhaps the information that you only provide in your second post should have been in the first.
OCrowley wrote: I have read that and yes I find it misleading that it doesn't show an example of how to set one up,
Expecting? Yeah, exactly why I have given up on any expectation of "Personal Responsibility".
led mike
|
|
|
|
|
You may not like led mike's link, but the very first sentence states:
"You are not allowed to construct a ColorPalette object directly."
You can get the Bitmap's ColorPalette using its Image.Palette Property,
also mentioned at the link.
pixBitmap = new Bitmap(50, 20, PixelFormat.Format8bppIndexed);
myPal = pixBitmap.Palette;
...
Mark Salsbery
Microsoft MVP - Visual C++
modified on Thursday, October 9, 2008 12:56 PM
|
|
|
|
|
Hi.
I know it was nearly 4 years ago when I wrote this topic, but I just want to apologise for being rude in the last post. I was young and ignorant back then. MSDN is a great collection and I shouldn't insult the work put into it... although I still think it should have more example code. I sorted the C# problem out since btw.
No hard feelings.
OCrowley
|
|
|
|
|
Hai all,
I created an exe that take a reference of Excel 2007,(C# 2005). My problem is when i am trying to run the exe from another machine(that machine uses Excel 2003) it will produce an exception like ' Interop.Excel ...dll' not found.. How to solve this?
Thanks in Advance
Praji..
|
|
|
|
|
|
If you know we have a thing that is named Accelerator in Visual C++ for working with shortcut and keyboard
do we have any things like this in C#.
if no; Please help me to impelement like this
Hello Friends
|
|
|
|
|
Laji59 wrote: If you know we have a thing that is named Accelerator in Visual C++ for working with shortcut and keyboard
do we have any things like this in C#.
Are you kidding? [^]
Good luck, you're going to need it.
led mike
|
|
|
|
|
Well, I don't no anything about Accelerator! What do you want to do In C#?
While (true) { Human.isLearnable = true; }
|
|
|
|
|
I want to manage some Keys like "Alt+F4" ( for example for exit)
but I don`t want use "KeyDown" event of controls
can I do it in any way ?
Hello Friends
|
|
|
|
|
If this is WinForms, set the form's KeyPreview property to true and handle the form's various key events.
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
|
|
|
|
|
When you turn on KeyPreview, you can manage all events occurring by keyboard in Form_KeyDown:
private void Form1_KeyDown(object sender, KeyEventArgs e)
{
if (e.Modifiers == Keys.Alt && e.KeyCode == Keys.Q)
Application.Exit();
}
While (true) { Human.isLearnable = true; }
|
|
|
|
|
I have a VB6 DLL that has a class, ICommonEnv, that is used as an interface definition for another VB6 class, clsCommonEnv, that implements ICommonEnv. When I build the VB6 DLL, in the VS2005 Object viewer I see clsCommonEnv, _clsCommonEnv, __clsCommonEnv, clsCommonEnvClass, ICommonEnv,
_ICommonEnv, and __ICommonEnv. I understand that the "_" is VB6's class interface and "__" is VB6's events inerface.
I want to use an instance of clsCommonEnv in my C# app, and, of course, I referenced the COM DLL and added the "using" statement in my .cs file.
I have not found any documentation that tells me when and where to use which of the interfaces and classes. For example, I also pass this object to C# and other VB6 objects that expect the ICommonEnv interface. I have tried this code by trial and error, but I would like to find some documentation that really explains what to use and why.
For example...
private _ICommonEnv m_oCommonEnvCOM;
m_oCommonEnvCOM = new clsCommonEnvClass();
Int32 lRet = someVB6COMObject.Init(ref m_oCommonEnvCOM)
Thanks in advance for those who can help point me to useful documentation.
|
|
|
|
|
|
I appreciate the quick response. The article covers stuff I've read before, and doesn't address the peculiar aspects of VB6 COM objects in C# (or .NET in general). Unfortunately, I've inherited production code that has the poor design of using ICommonEnv as an "interface class" in VB6 from which the clsCommonEnv class implements that interface. Good VB6 OO design is making the clsCommonEnv class (and no ICommonEnv class whatsoever), then having any other classes implement that interface (Implements clsCommonEnv instead of Implements ICommonEnv).
An article like the one you posted that is geared to VB6 COM DLLs, rather than C++ COM DLLs is what I am looking for.
Thanks, again, though for being kind enough to post a quick response.
|
|
|
|
|
MSBassSinger wrote: rather than C++ COM DLLs is what I am looking for
Really? In your original post, you wrote:
When I build the VB6 DLL
Which is it, C++ or VB?
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
As I have said in both posts, VB6 DLLs. I never said I was looking for C++ COM info. The 1st response was about C++ DLLs, which is not the issue in my case.
The full line, of which you quoted a part, is:
An article like the one you posted that is geared to VB6 COM DLLs, rather than C++ COM DLLs is what I am looking for.
The object of "what I am looking for" is clearly "article like the one you posted that is geared to VB6 COM DLLs". I should have placed an apostrophe after the phrase "rather than C++ COM DLLs".
|
|
|
|
|
I think my code has just raised a OnGenerateHeadache() event
I'm implementing a TCP server that accepts client connections and process messages sent to it, then sends an appropriate response. Something gave me the idea that using events and delegates was a good idea but now I'm starting to wonder if it was. My code works and I will probably not change it (unless I can improve it) but I'd like to get the opinion of experts on how sound my approach is.
What got me thinking along the lines of events and delegates at first is this; data coming in over a TCP connection could come in various bursts. It's just a stream of data and the start and end of one message might not arrive in the same burst. So my TCPConnection class raises an event every time it receives data but it won't know whether that data constitutes a complete message or just the first half of a message. It simply raises an event (called DataReceived(byte[] stream) ), passing the bytes received as a parameter. Whoever handles that event is responsible for checking when the message is complete.
Enters my next class, FramingEngine . My way of establishing when a message is complete is to 'frame' it with extra bytes before and after. My protocol is slightly more complex but for the sake of simplicity let's just say it works as follows. Every message will start with a 0x02 byte and end with a 0x03 byte (unless the byte is preceded by a 0x10 byte in which case it is just part of the message).
So FramingEngine has a method called DecodeIncomingData(byte[] buffer) which checks for these bytes and packs the message into an internal buffer until it receives the terminating bytes of a message. At this point the method knows that it has received a complete message and it raises an event (called MessageReceived(byte[] message) ), passing the internal buffer which is stripped of all these control bytes.
Enters my next class, MessagingEngine . This is the class that understands the messages. In other words, this class is specific to my current project while TCPConnection and FramingEngine are common classes that could be used in any other project of mine that also utilizes TCP comms. So MessagingEngine has a method called HandleMessage(byte[] message) which processes a message, decides what to do with it and responds if necessary.
So basically, data coming in on the TCP connection gets passed all the way down to MessagingEngine through events. Something like this:
TCPConnection myConnection;
FramingEngine frameEngine = new FramingEngine();
MessagingEngine messageEngine = new MessagingEngine();
myConnection.DataReceived += new TCPConnection.DataReceivedDelegate(frameEngine.DecodeIncomingData);
frameEngine.MessageReceived += new FramingEngine.FrameReceivedDelegate(messageEngine.HandleMessage);
So far so good, but now, to some of the messages (most of them actually) that MessagingEngine receives it has to respond, but is has to do so framing the responses through FramingEngine first and then ultimately sending it to TCPConnection .
The problem is that MessagingEngine has no knowledge of the TCP connection on which the data was received (and is to be sent again). It doesn't even have knowledge of FramingEngine . So, I decided to employ this mechanism of events being raised and handled to pass the message up the chain of abstraction again. As I said, it works, but I'm not sure this is good programming. What are your opinions?
So MessagingEngine when it's ready to respond, raises an event called SendMessage(byte[] message) . FramingEngine has a method called EncodeOutgoingData(byte[] message) which is used to handle the event raised by MessagingEngine . In turn, EncodeOutgoingData raises an event called MessageFramed(byte[] buffer) which is handled by the TCP connection's SendData(byte[] buffer) method, like so:
messageEngine.SendMessage += new MessagingEngine.SendMessageDelegate(frameEngine.EncodeOutgoingData);
frameEngine.MessageFramed += new FramingEngine.MessageFramedDelegate(myConnection.SendData)
Would you have done it differently? Which is an elegant way of doing this?
|
|
|
|
|
Sounds good to me - if it works, then cool
It may be doable without events unless there are other objects that need to be notified about events in your chain.
Have I got this right?
TCPConnection knows about FramingEngine.
FramingEngine knows about MessagingEngine.
If so,
TCPConnection could call a method in FramingEngine.
FramingEngine could call a method in MessagingEngine.
MessagingEngine could send data back to FramingEngine via a delegate.
FramingEngine could send data back to TCPConnection via a delegate.
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
|
|
|
|