I think this[^] has the answer you're looking for (particularly answer 4). It isn't as simple as it seems and the other solutions I've seen simply set a transparent replacement colour, which is going to result in popping pixels if any part of your rendered objects happen to contain that colour.
u may need to used blending. opengl supports different blending operation between source and destinations. u can use the function glBlendFunc(..) to define the operations. first u need to enable
blending by calling glEnable(GL_BLEND)
I think this problem occurs because of x and y of points because when I change the points, the shape will fill correctly.
Here is the code:
publicpartialclass Form1 : Form
privatevoid Form1_Paint(object sender, PaintEventArgs e)
Graphics g = e.Graphics;
GraphicsPath gp = new GraphicsPath(FillMode.Winding);
gp.AddLine(new PointF(290, 170),new PointF(98, 128));
gp.AddLine(new PointF(110, 170), new PointF(290, 170));
gp.AddLine(new PointF(110, 170), new PointF(98, 128));
g.FillPath(new SolidBrush(Color.Red), gp);
I want a tool to plot real time graph for .net platform.The data which has to be plotted is continuously coming in some time interval.Is there any tool available?
Also Performance issue is there.Performance also matters when I am using the tool.
Thanks in adv...
Since your question mentions the fact that you want to do this in .NET I would expect the .NET Framework forum would be a good start. I note that you have been a CP member for over a year now so you should be familiar with the posting guidelines.
Just say 'NO' to evaluated arguments for diadic functions! Ash
What is the proper way to cause dc to release bitmap without assigning another "real" resource (return the dc to its freshly created state) so that another dc in another subroutine can select mybitmap?
GDI works with handles: HDC for device-contexts, HBITMAP for bitmaps, and so on. MFC provides a wrapper class for each entity provided by GDI: the CDC class wraps a device-context and internally holds an HDC, the CBitmap class wraps a bitmap and internally holds an HBITMAP and so on.
When you call CDC::SelectObject(), it returns a pointer to the appropriate MFC class that represents the GDI object previously selected into the device-context; these pointers are obtained calling the FromHandle() method (e.g. in case of a bitmap object CBitmap::FromHandle() is called).
The pointers obtained in this way could be temporary because, if your application reach the idle state, i.e. its CWinApp::OnIdle() is called, the objects pointed are deleted; this doesn't mean that the underlaying handle is destroyed, but only that the wrapper class is destroyed. As a conseguence, you cannot store such a pointer to use it later: you should select it back into the device-context before returning from the current message handler.