Code

[SomethinCool]

Is there a way that i can convert this code from VB to C++? I am asking this in both the C++ and VB forum.

Public Declare Function GetTickCount Lib "kernel32" () As Long
Public Sub Pause(Interval As Long)
    Dim Start
    Start = GetTickCount
    Do While GetTickCount < Start + Interval
    DoEvents
    Loop
End Sub

[SteveCRM]

There is no DoEvents() in C++....so its going to get very complicated

[SomethinCool]

thats what i thought....i wasnt sure if it was gonna be as simple as VB....if anyone knows how to do it...that would be great.

[Zaei]

It would look like this:

void Pause(HWND hWnd, unsigned long interval) {
  unsigned long start = GetTickCount();
  MSG msg;
  while(start + interval > GetTickCount()){
      if(PeekMessage(&msg, hWnd, 0, 0, PM_REMOVE)) {
          TranslateMessage(&msg); DispatchMessage(&msg);}
   }
}

The PeekMessage(), Translate- and DispatchMessage() calls act as DoEvents.

Z.

[SomethinCool]

cool thanks

[The Hobo]

Nifty

[SomethinCool]

what should i put for hWnd though? I am making a console app....

[parksie]

In a console program you don't need DoEvents or its equivalent since it doesn't receive any (useful) events.

[SomethinCool]

then what can i put in there to simulate the same effect as the VB code that i posted above.

[The Hobo]

What exactly are you trying to do? Like your code, why do you need this in there?

[SomethinCool]

well..at first i just wanted to know now i just want to put it in there to blink something..thats all.

[parksie]

To pause for a certain length of time in a console app, the easiest way is to #include <windows.h>, then call Sleep(milliseconds).

On POSIX systems there's usleep or nanosleep or something

[Zaei]

Ah, didnt know it was a console app. In that case, Sleep() is good, or you can simply convert your code straight over, without the DoEvents at all.

Z.

[SomethinCool]

Sorry, I should have told you at first...most people using C++ make Win32 but since i am just starting out, i am gonna make simple console apps.

Also, if you make a Win32 Window using the CreateWindow API, what the form is called?

Like, in VB you'd have form1 and form2 and so on...how do you know what the form name is in C++ if you dont use the MFC.

[parksie]

Forms don't exist even as a concept. In VB a form is an abstract type which consists of a window and an associated set of VB code...

[SomethinCool]

Well, in VB when you type Form2.Label1.Caption = "Hello World!", VB knows to go to Form2, how does C++ know which form to go to?

[parksie]

You can't do "Form.Label1.Caption" using the API.

It's all windows. For example, a button is a window, which is a child of a larger window.


Just forget any VB programming stuff right now if you want to do it in C++, trust me

[SomethinCool]

Should I keep learning console apps before i go into win32 programming or start learning Win32 programming?

If so, what are some good books for Win32 Programming and/or tutorials online?

[parksie]

Learn the language first, then move onto making Windows programs

The winprog.org tutorial is probably the best

[SomethinCool]

I'm not in college, i'm in high school......or are you just saying that...

[The Hobo]

He's just saying that. Visual Basic does alot of things for you that it shouldn't. Windows are created automatically without you doing a thing, and properties are referenced in a nice manner. In C++, you have to create everything yourself. You have to specify the caption as you create the window. If you need to change it later, you use the SetWindowText() API. Everything is done through API.

So you're going to have to drop your concept of forms before you can start understanding. Did you look through the tutorials at the top of this forum?

[SomethinCool]

so it's like a webpage...everything is done by code. Doesn't the MFC make programming a windows program much easier and faster?

[The Hobo]

I suppose, but it also makes you include a bunch of dependencies. I like the API way.

[CornedBee]

And you shouldn't use it unless you know the API. You might get lost. No, you will get lost.