DoEvents [Résolu]

Signaler
Messages postés
104
Date d'inscription
lundi 21 août 2006
Statut
Membre
Dernière intervention
29 mai 2011
-
Messages postés
3275
Date d'inscription
jeudi 3 avril 2008
Statut
Membre
Dernière intervention
14 septembre 2014
-
Bonjour, est ce qu'il existe mieux qu'un DoEvents
niveau rapiditée ?

7 réponses

Messages postés
104
Date d'inscription
lundi 21 août 2006
Statut
Membre
Dernière intervention
29 mai 2011

thank you, moi j'ai remplacer mon Doevents qui me permetait da valider ma toucher UP par ceci et ca marche terrible :

Option Explicit


Private Type FILETIME
dwLowDateTime As Long
dwHighDateTime As Long
End Type
Private Const WAIT_ABANDONED& = &H80&
Private Const WAIT_ABANDONED_0& = &H80&
Private Const WAIT_FAILED& = -1&
Private Const WAIT_IO_COMPLETION& = &HC0&
Private Const WAIT_OBJECT_0& = 0
Private Const WAIT_OBJECT_1& = 1
Private Const WAIT_TIMEOUT& = &H102&
Private Const INFINITE = &HFFFF
Private Const ERROR_ALREADY_EXISTS = 183&
Private Const QS_HOTKEY& = &H80
Private Const QS_KEY& = &H1
Private Const QS_MOUSEBUTTON& = &H4
Private Const QS_MOUSEMOVE& = &H2
Private Const QS_PAINT& = &H20
Private Const QS_POSTMESSAGE& = &H8
Private Const QS_SENDMESSAGE& = &H40
Private Const QS_TIMER& = &H10
Private Const QS_MOUSE& = (QS_MOUSEMOVE _
Or QS_MOUSEBUTTON)
Private Const QS_INPUT& = (QS_MOUSE _
Or QS_KEY)
Private Const QS_ALLEVENTS& = (QS_INPUT _
Or QS_POSTMESSAGE _
Or QS_TIMER _
Or QS_PAINT _
Or QS_HOTKEY)
Private Const QS_ALLINPUT& = (QS_SENDMESSAGE _
Or QS_PAINT _
Or QS_TIMER _
Or QS_POSTMESSAGE _
Or QS_MOUSEBUTTON _
Or QS_MOUSEMOVE _
Or QS_HOTKEY _
Or QS_KEY)


Private Declare Function CreateWaitableTimer Lib "kernel32" _
Alias "CreateWaitableTimerA" ( _
ByVal lpSemaphoreAttributes As Long, _
ByVal bManualReset As Long, _
ByVal lpName As String) As Long


Private Declare Function OpenWaitableTimer Lib "kernel32" _
Alias "OpenWaitableTimerA" ( _
ByVal dwDesiredAccess As Long, _
ByVal bInheritHandle As Long, _
ByVal lpName As String) As Long


Private Declare Function SetWaitableTimer Lib "kernel32" ( _
ByVal hTimer As Long, _
lpDueTime As FILETIME, _
ByVal lPeriod As Long, _
ByVal pfnCompletionRoutine As Long, _
ByVal lpArgToCompletionRoutine As Long, _
ByVal fResume As Long) As Long


Private Declare Function CancelWaitableTimer Lib "kernel32" ( _
ByVal hTimer As Long)


Private Declare Function CloseHandle Lib "kernel32" ( _
ByVal hObject As Long) As Long


Private Declare Function WaitForSingleObject Lib "kernel32" ( _
ByVal hHandle As Long, _
ByVal dwMilliseconds As Long) As Long


Private Declare Function MsgWaitForMultipleObjects Lib "user32" ( _
ByVal nCount As Long, _
pHandles As Long, _
ByVal fWaitAll As Long, _
ByVal dwMilliseconds As Long, _
ByVal dwWakeMask As Long) As Long


Public Sub Wait(lNumberOfSeconds As Double)
Dim ft As FILETIME
Dim lBusy As Long
Dim lRet As Long
Dim dblDelay As Double
Dim dblDelayLow As Double
Dim dblUnits As Double
Dim hTimer As Long
hTimer = CreateWaitableTimer(0, True, App.EXEName & "Timer")


If Err.LastDllError = ERROR_ALREADY_EXISTS Then
' If the timer already exists, it does n
' ot hurt to open it
' as long as the person who is trying to
' open it has the
' proper access rights.
Else
ft.dwLowDateTime = -1
ft.dwHighDateTime = -1
lRet = SetWaitableTimer(hTimer, ft, 0, 0, 0, 0)
End If
' Convert the Units to nanoseconds.
dblUnits = CDbl(&H10000) * CDbl(&H10000)
dblDelay = CDbl(lNumberOfSeconds) * 1000 * 10000
' By setting the high/low time to a nega
' tive number, it tells
' the Wait (in SetWaitableTimer) to use
' an offset time as
' opposed to a hardcoded time. If it wer
' e positive, it would
' try to convert the value to GMT.
ft.dwHighDateTime = -CLng(dblDelay / dblUnits) - 1
dblDelayLow = -dblUnits * (dblDelay / dblUnits - _
Fix(dblDelay / dblUnits))


If dblDelayLow < CDbl(&H80000000) Then
' &H80000000 is MAX_LONG, so you are jus
' t making sure
' that you don't overflow when you try t
' o stick it into
' the FILETIME structure.
dblDelayLow = dblUnits + dblDelayLow
End If
ft.dwLowDateTime = CLng(dblDelayLow)
lRet = SetWaitableTimer(hTimer, ft, 0, 0, 0, False)


Do
' QS_ALLINPUT means that MsgWaitForMulti
' pleObjects will
' return every time the thread in which
' it is running gets
' a message. If you wanted to handle mes
' sages in here you could,
' but by calling Doevents you are lettin
' g DefWindowProc
' do its normal windows message handling
' ---Like DDE, etc.
lBusy = MsgWaitForMultipleObjects(1, hTimer, False, _
INFINITE, QS_ALLINPUT&)


DoEvents
Loop Until lBusy = WAIT_OBJECT_0
' Close the handles when you are done wi
' th them.
CloseHandle hTimer
End Sub
Messages postés
3275
Date d'inscription
jeudi 3 avril 2008
Statut
Membre
Dernière intervention
14 septembre 2014
3
???je ne comprends pas la question??

Bonjour chez vous !
Messages postés
7668
Date d'inscription
samedi 5 novembre 2005
Statut
Membre
Dernière intervention
22 août 2014
25
Le multiThreading (et encore, en fonction du cas...) que VB6 ne gère pas ...
Messages postés
13280
Date d'inscription
lundi 13 décembre 2004
Statut
Modérateur
Dernière intervention
3 février 2018
37
salut,

mieux qu'un doevents?

umm...
un 128ème de doevents...

If (i And 127) = 0 Then DoEvents

<hr size="2" width="100%" />Prenez un instant pour répondre à [infomsg_SONDAGE-POP3-POUR-CS_769706.aspx ce sondage] svp  
Messages postés
3275
Date d'inscription
jeudi 3 avril 2008
Statut
Membre
Dernière intervention
14 septembre 2014
3
ben il y a toujours un DoEvents das ton code !

sais tu à quoi sers DoEvents?

Bonjour chez vous !
Messages postés
104
Date d'inscription
lundi 21 août 2006
Statut
Membre
Dernière intervention
29 mai 2011

si je ne dit pas de betise DoEvents sert a donner la main au system et du coup ca me procure une sorte de pause a mon action mais si je met DoEvents directement dans mon code ca donne pas terrible mais par l'intermediaire de code
c'est nettement plus rapide pour moi.
Messages postés
3275
Date d'inscription
jeudi 3 avril 2008
Statut
Membre
Dernière intervention
14 septembre 2014
3
ok ,super


a+










Bonjour chez vous !