Prev: Xft : please explain me !
Next: exec fails but re-directed stdout and stdlog is empty
From: David Gravereaux on 7 Aug 2010 15:14
On 08/07/2010 06:05 AM, eugene wrote:
> On Aug 6, 10:05 pm, David Gravereaux <davyg...(a)pobox.com> wrote:
>> Aside from Ffidl, there's other ways to call ShellExecuteEx.
>>
>> 1) Twapi or
>>
>> 2) write a C extension. I'll even donate the code:
>>
>> http://tomasoft.cvs.sourceforge.net/viewvc/tomasoft/winutils/Shell.c?...
>>
>> --
>>
>> signature.asc
>> < 1KViewDownload
>
> Yes David, I'm aware of different ways to call Windows API functions
> from Tcl, however, my application already uses Ffidl for other
> purposes so I just decided to try using it to the maximum extent.
> This ShellExecuteEx though became a major showstopper for me :)
> First I tried to use your winutils package and its shell function
> worked flawlessly with simple verbs like "open", but when I tried to
> use other ones, like "properties" for example, it failed with error
> "File association is not available". I suppose some verbs require
> setting the correct fMask field in SHELLEXECUTEINFO structure and I
> haven't found the way to do it in winutils.


Sounds like some simple mods to the code are needed if that's the case.
'properties' is a canonical verb, so I don't understand why it doesn't
work.

My exceptionally liberal license allows for downright stealing of my
works. So please make derivatives and mod it as required. I must have
wrote that code about 13 years ago.

--


First  |  Prev  | 
Pages: 1 2
Prev: Xft : please explain me !
Next: exec fails but re-directed stdout and stdlog is empty