https://bugs.winehq.org/show_bug.cgi?id=57882
Bug ID: 57882 Summary: vbscript:Haven't hook up events Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs@winehq.org Reporter: fang.jiali@vico-lab.com
In Microsoft's vbscript.dll, before starting the actual script, the scripting engine will connect to the events of all the relevant objects through the IConnectionPoint interface.
But in this vbscript.dll, it haven't above step(hook up events).
Is this feature planned to be supported in the future?
https://bugs.winehq.org/show_bug.cgi?id=57882
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com --- Hi,
could you produce some sample code that shows this behavior?
https://bugs.winehq.org/show_bug.cgi?id=57882
--- Comment #2 from Jiali Fang fang.jiali@vico-lab.com --- Hi,
My script code is:
Function Button_1_Click() msgbox "Button_1 is click" End Function
In my project, I did this: m_pScript->AddNamedItem("Button_1", SCRIPTITEM_ISVISIBLE | SCRIPTITEM_ISSOURCE); m_pScriptParse->ParseScriptText() with above script code. m_pScript->SetScriptState(SCRIPTSTATE_CONNECTED);
If we use Microsoft's vbscript.dll, the scripting engine will connect to the click event of "Button_1" through the IConnectionPoint interface, and when we click "Button_1", it will execute above script and show a messbox.
But if we use Wine's vbscript.dll, the click event of "Button_1" is not connected the function of "Button_1_Click".
https://bugs.winehq.org/show_bug.cgi?id=57882
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com --- I'm afraid this will need some example that is possible to compile and test.