Maybe someone can tell me for which control library file belong Timer ? :confused:
Printable View
Maybe someone can tell me for which control library file belong Timer ? :confused:
Msvbvm60.dll
Timer is one of the intrisic controls (also there is a built-in Timer function) so what difference would it make to know the library name? :confused:Quote:
Originally Posted by Lauriux1
I guess that Msvbvm60.dll is not defoult Windows XP file ? I'm right ? :rolleyes:
No, but it is a default VB6 file that should have gotten installed when you installed the software. Did you install VB6 from a legal, manufacturer's disc?Quote:
Originally Posted by Lauriux1
According to MS VB runtime files are distributed with every post Win98 OS.Quote:
Originally Posted by Lauriux1
However, it might not come with developer's license so as Hack said if you want to develop in VB (any version) you must install it from legal media.
Yes I know that! :)
I just want to know is there a big chance that people who will use my program will get an error like "Missing Msvbvm60.dll"
Or Msvbvm60.dll file is in all Windows XP by defoult???
It should be included in the setup and installation package that you create when you roll your app out.
Maybe someone can recommend an good code based timer (short code) ? :)
See post #41 here, but as Hack suggested you really should create an installation package. You are only asking for trouble otherwise. Is there some reason you don't want to create an installation package?
Post #14 not #41 ;)Quote:
Originally Posted by MartinLiss
Yes I can put Msvbvm60.dll to resources of my program but I already have MSCOMCTL.OCX, TABCTL32.OCX, COMDLG32.OCX there and I don't want make it more heavy than it is now.Quote:
Originally Posted by MartinLiss
I just want to make an delay function and for some reasons I don't want use Sleep API, that’s why I need a timer.Quote:
Originally Posted by MartinLiss
But if someone have some ideas how to make an delay function without timer then please post this ideas here. ;)
Code:Dim dClock As Double
dClock = Timer
While Timer < dclock + 1 ' "Wait" 1 second
DoEvents
Wend
Thanks MartinLiss :thumb:
But what is fundamental difference between:
andCode:Dim dClock As Double
dClock = Timer
While Timer < dclock + 1 ' "Wait" 1 second
DoEvents
Wend
:confused:Code:Dim Start As Long
Start = Timer
Do While Timer < Start + 1 ' "Wait" 1 second
DoEvents
Loop
Using a Long rather than a Double limits you to whole numbers. In other words this wouldn't do what you wanted.
I should say however that Do/Loop is better then While/Wend.Code:Dim Start As Long
Start = Timer
Do While Timer < Start + .5 ' "Wait" .5 second
DoEvents
Loop
Thanks MartinLiss for explanation :thumb:
And last question:
What is difference between Sleep and SleepEx ? :confused:
RESOLVED! :afrog:
To mark a thread resolved, click on Thread Tools, and click the 'Mark Thread Resolved' menu item.
Declare Sub Sleep Lib "kernel32" Alias "Sleep" (ByVal dwMilliseconds As Long)
· dwMilliseconds
Specifies the time, in milliseconds, for which to suspend execution. A value of zero causes the thread to relinquish the remainder of its time slice to any other thread of equal priority that is ready to run. If there are no other threads of equal priority ready to run, the function returns immediately, and the thread continues execution. A value of INFINITE causes an infinite delay.
______________________________________________________________________
Declare Function SleepEx Lib "kernel32" Alias "SleepEx" (ByVal dwMilliseconds As Long, ByVal bAlertable As Long) As Long
· dwMilliseconds
Specifies the time, in milliseconds, that the delay is to occur. A value of zero causes the function to return immediately. A value of INFINITE causes an infinite delay.
· bAlertable
Specifies whether the function may terminate early due to an I/O completion callback function or an APC. If bAlertable is FALSE, the function does not return until the time-out period has elapsed. If an I/O completion callback occurs, the function does not return and the I/O completion function is not executed. If an APC is queued to the thread, the function does not return and the APC function is not executed.
If bAlertable is TRUE and the thread that called this function is the same thread that called the extended I/O function (ReadFileEx or WriteFileEx), the function returns when either the time-out period has elapsed or when an I/O completion callback function occurs. If an I/O completion callback occurs, the I/O completion function is called. If an APC is queued to the thread (QueueUserAPC), the function returns when either the timer-out period has elapsed or when the APC function is called.
All VB6 applications require MSVBVM60.DLL to run! It's one of the foundation files for the VB run-time, without it your application will simply not run.Quote:
Originally Posted by Lauriux1
Please before you go off in the wrong direction please read Installation Problems You will need more than just that file for your app to run.