*I THOUGHT* it was matter of if the viewer stays in the foreground or
switches to the background. BUT, chromium-browser --new-window will got to the
background if there's already a chromium-browser window open.
As you say, though, if chromium-browser opens the file BEFORE going into the
background, then it will work.
On Mon, 28 May 2012, Christopher Barrington-Leigh wrote:
> I just changed my image viewer from eog (I think) to /usr/bin/chromium-browser --new-window
> and now images appear just fine, even though when I check the existence of the image (or, for instance, reload it) it has disappeared. So is the current bug just a matter of how long the viewer application takes to load the image? Or to return a 0 status to its caller??
>
>
*I THOUGHT* it was matter of if the viewer stays in the foreground or
switches to the background. BUT, chromium-browser --new-window will got to the
background if there's already a chromium-browser window open.
As you say, though, if chromium-browser opens the file BEFORE going into the
background, then it will work.
On Mon, 28 May 2012, Christopher Barrington-Leigh wrote:
> I just changed my image viewer from eog (I think) to /usr/bin/ chromium- browser --new-window
> and now images appear just fine, even though when I check the existence of the image (or, for instance, reload it) it has disappeared. So is the current bug just a matter of how long the viewer application takes to load the image? Or to return a 0 status to its caller??
>
>
--
Gerry Skerbitz
<email address hidden>