• Options
• Login
• Register
• Desktop Style
• Accelerated Mobile Pages Theme

Application Menus, AHK WinActivate Behavior

• Index

  • Jean Lalonde Support Forum
  • QUICK ACCESS POPUP FORUM
  • QAP SUPPORT
  • Application Menus, AHK WinActivate Behavior
• Application Menus, AHK WinActivate Behavior

• Application Menus, AHK WinActivate Behavior

  jims > 2019-02-27 16:44

  With Application menu items, thanks for including the following option: If the application is already running, activate it instead of launching (application must be of the exact same location)
  
  As expected, this option prevents QAP from starting another instance of the application, but I've found that if all windows are minimized to the Windows taskbar, nothing obvious occurs (i.e., QAP does not expand it from the taskbar as occurs with AHK's WinActivate command).
  
  I suggest that you add an option that would behave like AHK's WinActivate (and another option for WinMaximize) when all application windows are minimized to the taskbar. 
  
  Here's how I've been able to implement the above described behavior with AHK.
  
  

  Code:

  #o::
    IfWinExist, Outlook
    {
        WinActivate
        WinWaitActive, Outlook, , 10
        Sleep 100
    }
    Else
    {
        Run "C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE"
        WinWaitActive, Outlook, , 10
        Sleep 2000
    }
    IfWinExist, Outlook
    {
        ;Optional - desirable for some applications
        WinMaximize Outlook
    }
Return

• RE: Application Menus, AHK WinActivate Behavior

  Jean Lalonde > 2019-02-27 17:46

  Hi Jims,
  
  In fact you found a bug. I fixed it.
  
  Only for the info of those, like you, are interested in AHK language, QAP is using a technique a little more complex than the "IfWinExist" command in order to activate only apps with the same UAC level (run as admin vs normal). To do it, it has to scan every running app. The error was that QAP was checking for all windows, including hidden windows (command "DetectHiddenWindows, On"), and was confused when, in addition to its normal window, an app had an hidden window that was not reported as minimized. In this situation QAP was not restoring, nor activating the minimized window. I fixed it by scanning only for non-hidden windows (command "DetectHiddenWindows, Off").
  
  Thanks for reporting the issue. I'll move your post to the QAP Support section.
  
  Jean

• RE: Application Menus, AHK WinActivate Behavior

  jims > 2019-02-27 19:06

  Hi Jean - thanks for addressing the issue so quickly. I'm amazed by your responsiveness!
  
  For the few applications that I want to always open Maximized (like Outlook), do you have any suggestions? (I created a shortcut to the EXE and then created a QAP menu item to open the new shortcut, but repeated uses of the menu opens multiple Outlook windows.)

• RE: Application Menus, AHK WinActivate Behavior

  Jean Lalonde > 2019-02-27 19:24

  > For the few applications that I want to always open Maximized (like Outlook), do you have any suggestions?
  
  QAP Applications had a "Window Options" tab in the past to control the position, size and state (minimized, maximized, etc.) but so many apps did not comply to the AHK commands (especially WinMove) that I removed these options. Maybe I should review this at least for the states (Maximized, Normal or Minimized).
  
  > (I created a shortcut to the EXE and then created a QAP menu item to open the new shortcut, but repeated uses of the menu opens multiple Outlook windows.)
  
  I see. You could use the Current Windows menu to reactivate the Outlook window. But this is probably not as convenient as reusing always the same favorite entry.
• Next Oldest Next Newest