1. Re: bad problem - for Rob.
Matt, I tried this and nothing happened. The button appeared as usual but a
click on it did nothing. ARF020 was not launched. Did I make the change
correctly?
----------------------------------------------------------------------------
---------
include Win32Lib.ew
without warning
----
-- Window Window1
global constant Window1 = create( Window, "Window1", 0, Default,
Default,400, 300, 0 )
global constant PushButton2 = create( PushButton, "PushButton2", Window1,52,
16, 90, 30, 0 )
----
procedure PushButton2_onClick ()
shellExecute("open","exw d:/euphoria/training/arf020.exw", SW_SHOWNORMAL)
-- i put the full path of exw and still nothing happened --
end procedure
onClick[PushButton2] = routine_id("PushButton2_onClick")
WinMain( Window1, Normal )
I've to go out of town this morining but will be back late afternoon.
....george
----- Original Message -----
From: "Matthew Lewis" <matthewwalkerlewis at YAHOO.COM>
To: "EUforum" <EUforum at topica.com>
Sent: Tuesday, August 07, 2001 8:09 PM
Subject: Re: bad problem - for Rob.
>
>
> From: "Irv Mullins" <irvm at ellijay.com>
> > We learned that calling system_exec from a Win32Lib program causes
> > something that deals with the modem to get corrupted.
> > Using the same call from DOS, even if it calls a Win32Lib program,
> > doesn't.
> >
> > Now, what good that info does us is questionable, since we (or I, at any
> > rate) have no clue about what happens internally between Windows and
> > Euphoria.
> >
> > Maybe someone does.
>
> I don't think that there's anything win32lib is doing to mess things up,
but
> rather than system_exec, you could try win32lib's shellExecute/Ex. I
don't
> know how Rob implements system_exec, but shellExecute calls the Win32 API
> routine designed expressly for starting new processes in windows.
>
>
> =====
> Matt Lewis
> http://www14.brinkster.com/matthewlewis
>
>
>
>
>
