Closed Archs closed 9 years ago
Following the documentation for sciter (Upgraded version of HTMLayhout), the HTMLayout
control may need WM_CREATE
message to behave correctly.
But in walk the external widget's WndProc
can't receive WM_CREATE
message, can walk
handle this?
With pull request https://github.com/lxn/walk/pull/141, One can using walk.MustRegisterWindowClassWithWndProcPtr
to do supper classing of the window gui system, and thus can pass WM_CREATE
etc to the target control and thus one could wrap more kind of controls as extrenal widgets into walk
HTMLayout is a fast, lightweight and embeddable HTML/CSS renderer and layout manager component. I've modified a binding go-htmlayout (which is workabe using cgo and syscall together) of the original c api.
I then tried to create an easy
walk
wrapper htmlayout for go-htmlayout using thedeclarative
style. But it doesn't work.In go-htmlayout I use
gohl.ProcNoDefault
to embed the
HTMLayout
window and it works fine(full example here).In
walk
, the following code(full code here)
gohl.LoadFile
fails or has no effect. I've tried to dogohl.LoadFile
in several other places later or earlier, but never made it work.I think this problem relates to the
Windows Messaging Mechanism
and howwalk
andHTMLayout
responds to it. I searched in thewalk
source code and only find that subclassing maybe relevant, but I can't find out the key point of the problem.Can you @lxn help me with this problem, thanks in advance :smile: