WindowMessage library

[agraham]

Since dzt wrote the dzEventsMagic library and I (sort of) documented it Basic4ppc has moved on. As dzt seems to have vanished from the forum I decided that I would create a similar, but enhanced, internally simplified and mergeable, library to replace it.

So for those few of us who might want to intercept and send Window Messages here is library, source for merging, help and demo application.

[Zenerdiode]

This is great, I've been wanting something like this for a while - but I think I ask too much anyway.

but can I most humbly say the help file does not work for me? I'm using XP SP2. I'm getting "The page cannot be displayed" messages.

[agraham]

Originally Posted by Zenerdiode

I'm getting "The page cannot be displayed" messages.

You probably need to unblock it as it is probably being considered a security risk as a download. It's somewhere in
Right click -> Properties I think.

[Zenerdiode]

I'm sorry but I had completely disregarded that because I mistakingly thought it affected Windows Vista and above only. It was in Properties and once unblocked it never asks again. Thank You.

[berndgoedecke]

Hello Andrew,
in my curent Desktop-Project I use dzEvent_Magic to get x- and y- scroll position from the scrollbars, of an MDI Client, which is set to Autoscroll like this:

#Region BuildFormEx3
AddForm("Form3", "Report")
FormEx3.New2("Form3","Report",600,600)
AddImage("Form3", "ImageF", 580, 580, 20, 20)
FormEx3.AddControl("ImageF")
AddImage("Form3", "ImageB", 580, 560, 20, 20)
FormEx3.AddControl("ImageB")
AddImage("Form3", "ImageZF", 580, 540, 20, 20)
FormEx3.AddControl("ImageZF")
AddImage("Form3", "ImageZB", 580, 520, 20, 20)
FormEx3.AddControl("ImageZB")
AddImage("Form3", "VLinImage", 15, 0, 15, 15)
FormEx3.AddControl("VLinImage")
AddImage("Form3", "HLinImage", 0, 15, 15, 15)
FormEx3.AddControl("HLinImage")
FormEx3.StartPosition = 0
FormEx3.WindowState = 0
FormEx3.ImageLayout = 0
frm3obj.FromControl(FormEx3.ControlRef)
frm3obj.SetProperty("AutoScroll", True)
dzem.New1(FormEx3.ControlRef, False)
dzem.Hook(276) 'WM_HSCROLL
dzem.Hook(277) 'WM_VSCROLL
hscrollobj.value = frm3obj.GetProperty("HorizontalScroll") ' returns an HScrollProperties type
hscrollobj.SetProperty("LargeChange", 100)
vscrollobj.value = frm3obj.GetProperty("VerticalScroll") ' returns an VScrollProperties type
vscrollobj.SetProperty("LargeChange", 100)
#End Region

The events are catched by this Sub(It's from an example in the Forum I didn't fin again):
Sub dzem_MagicEvent ' notice we seem to get two events for every scoll action!
msg1 = dzem.msg
Select msg1
Case 276
If Htoggle Then
ScrX = hscrollobj.GetProperty("Value")
IDebug.Text = FormEx3.ClientAreaHeight 'ScrXMax -
IScrolX.Text = ScrX
VLinImage.Left = (ScrX/(FormEx3.ClientAreaWidth-15))
VLinImage.BringToFront
End If
Htoggle = Not(Htoggle)
Case 277
If Vtoggle Then
ScrY = vscrollobj.GetProperty("Value")
IScrolY.Text = ScrY
HLinImage.Top = (ScrY/(FormEx3.ClientAreaHeight-15))-1
HLinImage.BringToFront
End If
Vtoggle = Not(Vtoggle)
End Select
End Sub

Is it possible to realize it with WindowsMessageDesktop.dll too?
I put the whole Project to this post too. It's buggie but it has been compieled(Desktop)
To see the window you have to click the Menue "Report", "Neu"
It would be verry nice, if it is possible, because the dzt dll is not mergeable.

Best Regards

berndgoedecke

[agraham]

Originally Posted by berndgoedecke

It would be verry nice, if it is possible, because the dzt dll is not mergeable.

That's the main reason I wrote this, so it could replace dzMagicEvents and be mergeable.

<font color="blue">dzem.New1(FormEx3.ControlRef, False)</font>
becomes
<font color="blue">WinMSg.New1(FormEx3.ControlRef)
WinMsg.Start</font><font color="SeaGreen"> ' might be better to do this after setting the traps</font>

<font color="Blue">dzem.Hook(276)</font> <font color="seagreen">'WM_HSCROLL</font>
becomes
<font color="blue">WinMsg.Trap(276)</font>

<font color="blue">dzem.Hook(277)</font><font color="SeaGreen"> 'WM_VSCROLL</font>
becomes
<font color="blue">WinMsg.Trap(277)</font>

<font color="blue">Sub dzem_MagicEvent</font>
becomes
<font color="blue">Sub WinMsg_TrapEvent</font>

<font color="Blue">msg1 = dzem.msg</font>
becomes
<font color="blue">msg1 = WinMsg.wMsg</font>

You must have a Form close event but you don't need to unhook each message
<font color="Blue">Sub FormEx3_Close
    WinMsg.Stop
End Sub</font>

[berndgoedecke]

Hello Agraham,
I've tried it in the way you have proposed, but the trap event wouldn't work.


Best regards
berndgoedecke

[agraham]

In Report02.sbp I can't see a WindowMessage object nor any of the code lines I posted.

[berndgoedecke]

In the meantime a played around with the BigScreenDoor example from the Forum and there it computes, but I don't know why it do not work on the FormEx.

[berndgoedecke]

BigScreenDoor