I have already gone through the same, but the constraint is , i don't want to use glibc for windows.. i just want to know its equivalent functions in windows (in VC++) like setTimer etc..
Actually i want to know the windows equivalent of "Main Event Loop" functionality.. Thanks for co-operation Deepak > -----Original Message----- > From: Kees Zeelenberg [mailto:kzlg@;users.sourceforge.net] > Sent: Saturday, October 26, 2002 12:47 PM > To: Deepak Kumar Gupta, Noida; [EMAIL PROTECTED] > Cc: Deepak Kumar Gupta, Noida > Subject: Re: [GnuWin32-Users] newbie question main event loop > g_timeout_add_full () for windows .. > > > You might have a look at Glib for MS-Windows at > http://www.gimp.org/~tml/gimp/win32/downloads.html > > Kees Zeelenberg > > ----- Oorspronkelijk bericht ----- > Van: "Deepak Kumar Gupta, Noida" <[EMAIL PROTECTED]> > Aan: <[EMAIL PROTECTED]> > CC: "Deepak Kumar Gupta, Noida" <[EMAIL PROTECTED]> > Verzonden: zaterdag 26 oktober 2002 7:27 > Onderwerp: [GnuWin32-Users] newbie question main event loop > g_timeout_add_full > () for windows .. > > > > Hello List, > > > > I want to know about the windows functions (any equivalent > API in VC++) > > similar to g_timeout_add_full (present in glibc) . My > application (VC++) > > needs to use it. Can anybody tell me, what should i do ?. > > > > Please cc reply to me also as i haven't subscribe the list > till now.. > > > > FYI the work of function given at following link: - > > > > http://developer.gnome.org/doc/API/2.0/glib/glib-the-main-event-loop.html#g- > timeout-add-full > > > g_timeout_add_full () > Sets a function to be called at regular intervals, with the given priority. > The function is called repeatedly until it returns FALSE, at which point the > timeout is automatically destroyed and the function will not be called > again. The notify function is called when the timeout is destroyed. The > first call to the function will be at the end of the first interval. > Note that timeout functions may be delayed, due to the processing of other > event sources. Thus they should not be relied on for precise timing. After > each call to the timeout function, the time of the next timeout is > recalculated based on the current time and the given interval (it does not > try to 'catch up' time lost in delays). > > Thanks in advance.. > > Deepak > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > GnuWin32-Users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/gnuwin32-users > ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ GnuWin32-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
