|
|
Programm3r wrote: an interval timer
What do you mean exactly by an interval timer ? A timer that fires every X msecs ?
If yes, that's how timers are working so I don't see the problem. Can you explain ?
|
|
|
|
|
Cedric Moonen wrote: A timer that fires every X msecs ?
Yes
Cedric Moonen wrote: Can you explain ?
When working with CLI(.Net) I know how to use timers. But I don't know how to use timers in C.
i.e I don't know what function to start looking at 
Makes sense ?
Thanks for the response
Regards,
The only programmers that are better than C programmers are those who code in 1's and 0's..... 
Programm3r
My Blog: ^_^
|
|
|
|
|
Oh, sorry. I thought that you already knew timers but you wanted to do something very specific. The other answers will give you all the info you need  .
|
|
|
|
|
Cedric Moonen wrote: Oh, sorry.
np
Thanks anyway
Regards,
The only programmers that are better than C programmers are those who code in 1's and 0's.....
Programm3r
My Blog: ^_^
|
|
|
|
|
SetTimer[^] is probably along your way.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
|
|
|
|
|
CPallini wrote: SetTimer[^] is probably along your way.
MSDN:
The SetTimer function creates a timer with the specified time-out value.
Will the SetTimer function restart then the UINT uElapse// time-out value is reached??
Regards,
The only programmers that are better than C programmers are those who code in 1's and 0's.....
Programm3r
My Blog: ^_^
|
|
|
|
|
Programm3r wrote: Will the SetTimer function restart then the UINT uElapse// time-out value is reached??
Yes, if you want to stop it, you need to call KillTimer and provide the Id of your timer.
|
|
|
|
|
|
Programm3r wrote: What function can I use to make an interval timer??
This is what SetTimer is for. Do you wanted to ask something different ?
|
|
|
|
|
prasad_som wrote: This is what SetTimer is for
Thank you prasad_som, I'll check it out.
Regards,
The only programmers that are better than C programmers are those who code in 1's and 0's.....
Programm3r
My Blog: ^_^
|
|
|
|
|
Hi,
I am getting crazy with my problem, and I really hope that someone can help me out.
Actually it sounds quite easy:
I have a normal simple dialog, and I then draw 2 lines (like the axes of a coordinate system) in that dialog using GDI+. So far so good. When the user resizes my dialog I of course also want to apply the changes in size to my 2 lines. That means that they should always have the same margin to the dialog borders. And that's the problem. When I make the dialog bigger, then the lines don't get "longer" but they stay in the same length as before. But If I make the dialog smaller they also get smaller. Just strange.
I do this by overriding the OnSize message handler of MFC and I then just get the client rectangle of the dialog and then draw the lines with this new rectangle applied.
I also tested this with just a normal button instead of the GDI+ lines. With a normal button it works as it should, but when using GDI+ it doesn't work and I absolutley don't know why 
Many thanks for that person who can help me...
P.S. I didn't know exactly in which forum to post it, because it may be a problem with MFC, but it also may be a problem with GDI+, so I just posted it in here, because I think that here are more readers...
|
|
|
|
|
FreeCastle wrote: I do this by overriding the OnSize message handler of MFC and I then just get the client rectangle of the dialog and then draw the lines with this new rectangle applied.
By this i understood that you are drawing the lines in OnSize handler..if then its wrong.
Draw the lines in OnPaint handler, the framewrok will call the OnPaint handler after the window got resized. So, in OnPaint handler, get the client rect and draw the lines
Do your Duty and Don't expect the Result
Rate this Post, if I helped You
|
|
|
|
|
Oh okay, I didn't say it right. To be exact, I get the client rectangle in the OnSize message handler, and then compute the new dimensions of the two lines. All I do then in the OnSize()-method is a call to Invalidate() and nothing else. The commands for drawing the two lines are placed in the OnPaint handler.
And yes, the dimensions of the two lines are computed correctly for 100% sure. That's strange in addition: The resizing works correctly if I make the dialog smaller, but when I make the dialog bigger then the two lines don't get bigger starting from a certain size.
|
|
|
|
|
FreeCastle wrote: I get the client rectangle in the OnSize message handler, and then compute the new dimensions of the two lines
No need to get the client rect in the OnSize handler. the cx and cy will give you the width and height of the window.
FreeCastle wrote: All I do then in the OnSize()-method is a call to Invalidate
No need to call Invalidate in OnSize Handler
FreeCastle wrote: the dimensions of the two lines are computed correctly for 100% sure
Pls provide some code, to figure out the problem
Do your Duty and Don't expect the Result
Rate this Post, if I helped You
|
|
|
|
|
Yes I know that cx and cy will also work. But I wanted to be completely sure, so I used GetClientRectangle. The result is anyway the same.
When I don't call "Invalidate" in the OnSize Handler then my dialog won't clear out the old contents (this will be then first done when I hide and show it again).
Here is some example code (all placed in my simple dialog class):
I have the following attributes:
<br />
Graphics* m_Canvas;
RECT m_rcRect;
And the following methods:
<br />
OnPaint() <br />
{<br />
drawLines();<br />
CDialog::OnPaint();<br />
}<br />
<br />
OnSize(UINT nType,int cx, int cy)<br />
{<br />
CDialog::OnSize(nType,cx,cy);<br />
<br />
m_rcRect.bottom = cy;<br />
m_rcRect.right = cx;<br />
<br />
Invalidate();<br />
}<br />
<br />
drawLines()<br />
{<br />
static bool bFirstCall = true;<br />
static Pen pen(Color::Red);<br />
<br />
if (bFirstCall == true) {<br />
m_Canvas = ::new Graphics(m_hWnd);<br />
bFirstCall = false;<br />
}<br />
<br />
m_Canvas->DrawLine(&pen,10,10,m_rcRect.right-10-10,10);<br />
m_Canvas->DrawLine(&pen,10,10,10,m_rcRect.bottom-10-10);<br />
}<br />
|
|
|
|
|
Do as below,
OnPaint(..)
{
CPaintDC dc(this);
DrawLines(&dc);
}
OnSize()
{
}
DrawLines(CDC* pDC)
{
Graphics g(pDC->m_hDC);
Pen pen(Color::Red);
CRect rc; GetClientRect(rc);
g.DrawLine(&pen, 10, 10, rc.Width() - 20, 10);
g.DrawLine(&pen, 10, 10, 10, rc.Height() - 20);
}
Do your Duty and Don't expect the Result
Rate this Post, if I helped You
|
|
|
|
|
Ahhh thank you, that works. But anyway I have to put an Invalidate() into the OnSize handler, because without that I see the changes only after hiding and showing again the dialog.
I don't really understand why this has to be done by a HDC, but the main thing is that it works. But there is one question open to me. In my "real" application I also do some transformations on the Graphics object (you know, for e.g. having a real local coordinate system and so on). Actually those transformations have only to be done when the dialog is showed the first time, and each time when the dialog is resized. But with that solution I also would have to make those transformations each time I draw my graphical objects. I don't really know, but I think this slows the performance a little bit down (and performance is important to me in this app). So is there a way to just recreate the Graphics object when the windows is resized (so that I don't have to perform all the time those transformations)?
Anyway... thank you a lot!!
|
|
|
|
|
FreeCastle wrote: But anyway I have to put an Invalidate() into the OnSize handler, because without that I see the changes only after hiding and showing again the dialog.
That's because only the new part of the window is invalidated (marked for repainting) during a resize. To force the entire window to be repainted when the size changes, invalidating on
WM_SIZE is fine.
FreeCastle wrote: I don't really understand why this has to be done by a HDC
Why what needs to be done with an HDC?
If you want to keep a Graphics object (associated with a HDC for the window) around for the life
of the window then you may want to consider using CS_OWNDC in the window class. See the
RegisterClass API for details (AfxRegisterClass for MFC).
Mark
"If you can dodge a wrench, you can dodge a ball."
|
|
|
|
|
Hello everybody,
Does anybody here has a complete program of Circle Equation?
Please help.Thanks.
|
|
|
|
|
faridah_hani wrote: Does anybody here has a complete program of Circle Equation?
See here[^]
Somethings seem HARD to do, until we know how to do them.
 _AnShUmAn_
|
|
|
|
|
Can you not draw a circle using Ellipse()? 
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Can you explain what do you need,exactly about "complete program of Circle Equation"
|
|
|
|
|
who can tell me more information about windows recycle bin?
I don't know the INFO2 data structure.
Thanks!
|
|
|
|
|
apoluo wrote: tell me more information about windows recycle bin
Recycle Bin is a virtual folder.
It is a Namespace Shell Extension (NSE). My Documents, My Music, and My Pictures all are NSE. This are some virtual representation to some location. That is, if you save any file in My Documents then the file will be originaly saved in C:\My Documents and not in the Desktop/My Documents (that is, C:\Documents and settings\user name\Desktop). Foe more information, refer Shell Extensions and Namespace Extensions.
apoluo wrote: I don't know the INFO2 data structure
I Have no idea abt this structure, may be its a user defined one.
Do your Duty and Don't expect the Result
Rate this Post, if I helped You
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
