Unity hiding open LibreOffice files

[Jim Byrnes]

On 02/04/2013 02:55 PM, Colin Law wrote:
> On 4 February 2013 18:34, Dotan Cohen <dotancohen at gmail.com> wrote:
>> On Sun, Feb 3, 2013 at 11:26 AM, Colin Law <clanlaw at googlemail.com> wrote:
>>> What do you mean when you say it is open on any desktop?  Are you
>>> talking about the same file being open on a different PC or are you
>>> talking about workspaces on one PC? Or what?
>>>
>>
>> I mean that there exists a LibreOffice window open with the document
>> loaded in memory. The LibreOffice window may or may not be on the
>> 'virtual desktop' that the user is currently viewing. The file is not
>> open on any other computer, it is a file on the local hard drive, open
>> in a local LibreOffice instance.
>
> I am not seeing that in Precise or Quantal.
> Open Nautilus and browse to folder containing LO document
> Double click the document to open LO
> Switch back to Nautilus so the document is behind it
> Double click the file again and it is brought to the front.
>
> I do see a problem if the open document is moved to a different
> workspace (is that what you mean by virtual desktop?).  In that case
> when I double click it in nautilus the LO icon in the launcher
> jiggles, but that is all, and it only does that the first time.  It is
> not limited to LO however, I see the same issue with pdf documents
> opened in Document Viewer.

I am seeing the same thing.  You don't have to move it there to see this 
happen.  Just opening a LO file in another workspace will give the same 
behavior.

Playing around with this I thought I might have a workaround, but it 
turns out I was wrong.  I use a little program called Drawers that sits 
on the Unity launcher and allows you to drop stuff on it you want to 
run. Sort of like Top Shelf on 10.04.  I use it to open clac spreadsheets.

I found if I open a file in workspace 1 and then go to workspace 2 and 
try to open the same file I am switched back to workspace 1. The problem 
is if I open a file in workspace 2 and then go to workspace 1 and try to 
open the same file nothing happens, so its not much of a workaround.

> I don't know whether this was a design decision or a bug.  Does anyone know?

I don't know, but having users thinking that they cannot open a file 
just because it is already open on another workspace and not giving some 
kind of visual clue that that is what is happening doesn't seem to be a 
good thing.

I'm glad I saw this thread because sooner or later I would have been 
bitten by this.

Regards,  Jim

> Colin
>