To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=109550


User pl changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|UNCONFIRMED               |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |DUPLICATE
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Mar 30 17:49:35 +0000 
2010 -------
Sort of; awesome manages multiple desktops for separate screens also in xinerama
mode. That is not wrong of course, but in this case it should not answer to
NET_CURRENT_DESKTOP requests. These are sent to the root window and as there is
only one big root window in xinerama case, awesome can never hope to know which
screen it should change the desktop for.

That said, you are of cause right that OOo shouldn't send one of these requests
for the tooltip that shows the chapter. Which is what was fixed with issue
109544, making this issue a duplicate.

If you find this still happens in build OOO320m14 (which you can find here:
http://download.openoffice.org/next/other.html ), please feel free to reopen
this issue.

*** This issue has been marked as a duplicate of 109544 ***

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to