[wx-dev] #9603: wxExecute doesn't return proper value with Mac app
bundle
wxTrac
noreply at wxsite.net
Thu Jun 19 11:51:25 PDT 2008
Ticket URL: <http://trac.wxwidgets.org/ticket/9603>
#9603: wxExecute doesn't return proper value with Mac app bundle
-------------------------------------+--------------------------------------
Reporter: blarged | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: wxMac | Version: 2.8.7
Keywords: wxMacExecute, wxExecute | Blockedby:
Patch: 0 | Blocking:
-------------------------------------+--------------------------------------
build: 53607
from:[http://docs.wxwidgets.org/stable/wx_processfunctions.html#wxexecute]
'''For asynchronous execution, however, the return value is the process id
and zero value indicates that the command could not be executed.'''
All right, so I've been banging my head on this for quite some time. In
the above documentation when wxExecute is called with the wxEXEC_ASYNC
flag, the returned long should be the process id. This works great... but
not if not executing an app bundle on a Mac.
The app bundle is successfully launched, however, the returned value
regardless of wxEXEC_ASYNC or wxEXEC_SYNC is the success code of
wxMacExecute.
{{{
from: src/mac/corefoundation/utilsexc_base.cpp
const long errorCode = ((flags & wxEXEC_SYNC) ? -1 : 0);
const long successCode = ((flags & wxEXEC_SYNC) ? 0 : -1);
}}}
No where can I find it returning a process id.
There doesn't seem to be any documentation for wxMacExecute, so I'm not
sure what the specifics of the return are. but since wxMacExecute is
called from wxExecute when there is an app bundle, I would think the
return values should match up.
--
Ticket URL: <http://trac.wxwidgets.org/ticket/9603>
More information about the wx-dev
mailing list