[maemo-developers] Software on MMC cards & OSSO question

[From: Murray Cumming]

On Sun, 2007-09-02 at 21:40 +0300, Mika Yrjölä wrote:
> On 9/2/07, David Hazel <david.hazel at enchaine.com> wrote:
> 
> > My second question is to do with the OSSO library. I am using the call
> > osso_rpc_run_with_defaults to open the browser. The Doxygen
> > documentation says that this call is "blocking", which I take to mean
> > that control should not return to my application until the browser is
> > closed. However, I am finding that control returns immediately, and does
> > not block my application. Is this a bug in OSSO, or have I misunderstood
> > what the "blocking" refers to? Ideally, I really need my application not
> > to continue past the invocation of the browser until the latter is
> > closed by the user. Failing that, I need to be able to embed a browser
> > in my application.
> 
> The call will block until either a reply/error has arrived to the
> call, or it timeouts. In this case, I'd assume that whatever method
> you're calling, it probably returns a reply indicating success (or
> failure) to your application via libosso as soon as that particular
> operation (say, opening an URL) has succeeded, allowing the execution
> of your app to continue. One way of doing what you want might be to
> listen for the disappearance of the browser service with D-BUS (and
> hope that it's gone because user closed it, instead of a crash :), but
> this is just a quick idea.
> 
> (as a disclaimer, it's been a while since I've used the osso_rpc_*
> calls myself, so my knowledge might be obsolete and misleading)

Yes, this is what happens. I doubt that there are many cases when they
ever do anything but return success.

I also very much doubt that there's any
show_web_page_and_block_until_the_user_closes_it() D-Bus method for the
browser.


-- 
murrayc at murrayc.com
www.murrayc.com
www.openismus.com