Win32api.MessageBox

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Unkwntech

    Win32api.MessageBox

    When I use win32api.Messag eBox from the interactive console from an
    app that runs at the command line, it works and displays my alert just
    fine however when I use it in a service that I built I can hear the
    'beep' but the alert does not show and the program seems to stall
    waiting for the alert to close, how can I have the alert show so that
    the user can see what it says and press the button?
  • Bruno Desthuilliers

    #2
    Re: Win32api.Messag eBox

    Unkwntech a écrit :
    When I use win32api.Messag eBox from the interactive console from an
    app that runs at the command line, it works and displays my alert just
    fine however when I use it in a service that I built I can hear the
    'beep' but the alert does not show and the program seems to stall
    waiting for the alert to close, how can I have the alert show so that
    the user can see what it says and press the button?
    I'm by no mean a Win32 expert, but IIRC, Windows 'services' (IOW :
    daemons) are not suppose to directly interact with the user. Now you'd
    better not take me on words on this...

    Comment

    • Duncan Booth

      #3
      Re: Win32api.Messag eBox

      Bruno Desthuilliers <bruno.42.desth uilliers@websit eburo.invalidwr ote:
      Unkwntech a écrit :
      >When I use win32api.Messag eBox from the interactive console from an
      >app that runs at the command line, it works and displays my alert just
      >fine however when I use it in a service that I built I can hear the
      >'beep' but the alert does not show and the program seems to stall
      >waiting for the alert to close, how can I have the alert show so that
      >the user can see what it says and press the button?
      >
      I'm by no mean a Win32 expert, but IIRC, Windows 'services' (IOW :
      daemons) are not suppose to directly interact with the user. Now you'd
      better not take me on words on this...
      >
      It's an option when you install the service. By default services will run
      under the 'local system' account and have no access to the desktop. You can
      either give the service permission to interact with the desktop from the
      service properties (or specify --interactive if installing it with
      win32serviceuti l).

      --
      Duncan Booth http://kupuguy.blogspot.com

      Comment

      Working...