Using SAPGUI.ScriptingCtrl for testing

Question

Hi
We are using SAPGUI.ScriptingCtrl API for recording SAPGUI events. We also use it to replay those recorded steps afterwards.
Does anybody know if it is possible to hide the SAPGUI? We wanna do it as we wanna start a test run without showing the actuall GUI. It seems that there is no offical way via some methods in the ScriptingCtrl Lib - but we've seen other tools that are able to do it.
So - is there an unoffical way?
Thanks

Answer 1

Hello,
1- For the connection: why don't you use the .connect method?
   You could set all the needed parameters in the SAPLOGON.ini file and then use only the "system name".
   If you don't want i found this way (a little bit direct but works...) we catch the handle of the first session SAP window
   after connection and we "parent" it to the control... (the API is a standard windows one).
   Code Example --->
   GuiApplication1.OpenConnectionByString('My string!');
   windows.SetParent(Isapsessiontarget(Isapconnectiontarget(GuiApplication1.Connections.Item(0)).Sessions.Item(0)).ActiveWindow.Handle,GuiApplication1.Handle);
2- For the popups.... the story became complicated!
  I can summirize:
  1- You need a GLOBAL WINDOWS MESSAGE HOOK (that is a dll file that you attach to your project): It will hook ALL Win messages
     but filter only the ones directed to Your Process (a dll is needed because global hooks must be in global memory and not process one).
  2- then you have to check for the specific message type HCBT_CREATEWND. This one is fired before creating a specific window or
     control (over the form). the Class type of SAP forms is '#32770'. So the trick is:
          - When you catch an event of this type and SAP form class You store the Handle in one list
          - Every time the HCBT_CREATEWND will be fired again for a different class (controls over the form) you check if the parent of the control
            (this is a parameter in the structure passes by the Win message HCBT_CREATEWND. ) is inside the list (that means that the control is owned
            by a CREATED window that must be hided)
          - If Yes you can now parent the Handle contained in the list (that is the handle of the form) to a wanted container control.
     NB: You cannot parent directly when you catch the message with the SAP Form Class Type.... the Setparent will be ignored (the Form is not created
         at this time!). Instead, doing so when you catch a control creation inside the form will guaranteee you that the form is created and that setparent
         API will work!
     PS: Acting at HCBT_CREATEWND level you are sure that you will not see any window because normally it is displayed only after all the controls on
         it are created (and you parent the window at the first created control!)
     PS: If you need i can send You an e-mail with the DLL for hooks (write me and i will answare); in your project you will have to import only one
         function. This one will take a pointer to a procedure to catch events (a sort of callback procedure).