| |
|
|
| I schreib Yes strain on the XIDE (and was Frank Yes completely hundsgemein now so on my own let (Frank is in the leave)) and I Specifically strain on the Communikation between XIDE-self and the XIDE-Panels(Plugins) work nuisance I awfully so rum the Messages (z.B. User Messages) simply lost weg if XProfan strain times not in the WaitInput is.
On well german weg any Messages lost - be because - the program stoppt strain in the Waitinput. therefore must I The Xide always join not just a Message To Send - separate such a long time one and the same Message To Send To the XProfanProgramm with of/ one others special Message answer.
Specifically in XIDE sees the so from (what but almost completely banana is) CompileMarkSeparation.data
boolMsgHasSend dd ?
.code
sureSendMessageToPlugin macro h,m,w,l
mov boolMsgHasSend,FALSE
.while boolMsgHasSend==FALSE
invoke SendMessage,h,m,l,w
invoke Sleep,10
.endw
endm
;--wproc-Auszug
...
invoke SetWindowPos,pluginr,0, eax,oben,breitexr,unten,SWP_NOOWNERZORDER or SWP_NOZORDER or SWP_SHOWWINDOW
.if phWnd
mov eax,pVSplitx
.if fpluginleftx==eax
.else
mov fpluginleftx,eax
sureSendMessageToPlugin phWnd,20012,0,0
.endif
.endif
.elseif eax==20019
mov boolMsgHasSend,TRUE
...
one can discern that the principle naturally imaginable simply is - gleichwohl but too completely Performanceschlapp.
XProfan ought to In any drop no Messages simply forget only because Waitinput strain not on the Zuge is. XProfans wProc (no idea which - can only Roland know ) must simply any thorough relevanten Messages on a pile pack and at each Waitinput whom pile work out - and Waitinput properly durchlassen if yet what on the pile lying.
this trouble has vordergründig nothing with the ProcAddr-trouble To do though ProcAddr ditto absolutely such a pile needed.
Please Please Roland pile finally (for may part too high ) only Please nothing forget - already not at all Messages (neither these *g*)
|
|
|
| |
|
|
|
RGH | so How You you the vorstellst, would not weg, without The compatibility To all recent (X)Profan-versions aufzugeben. eachone invasion into filigrane Messagehandling of XProfan lead zwangsweise To Inkompatibilitäten. but Perhaps helps you Yes such a thing in a scheduler, from the one ersehen can, which User-Messages since the last WaiInput aufgetreten are. i'll me time To gegebener Time thoughts above make!
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 07/10/07 ▲ |
|
|
|
|
| scheduler - very - I say hold pile.
at best manages (already from Performancegründen) XProfan The scheduler self.
For this, my idea:
WaitInput <-- als Prozedur: alles bleibt beim Alten WaitInput({modi}) <-- als Funktion, wenn z.B. modi 1 ist dann wird waitinput gleich verlassen wenn noch Msgs auf dem Stapel liegen. (so correctly. beautiful with filling of %message %umessage & Co.) |
|
|
| |
|
|