To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=83553
User aw changed the following:
What |Old value |New value
================================================================================
CC|'' |'af,aw,hdu,tl'
--------------------------------------------------------------------------------
Assigned to|aw |hdu
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Nov 16 09:49:08 +0000
2007 -------
AW: I am sorry, but i cannot see any regresson on DrawingLayer side. It has
always been like this (thanks to the people before me). What happens is pretty
simple:
- Mouse moves
- PickAnything is the central old method to find out what's under the given
position
- To answer if we have a hit, the geometry of the object is needed
- To get that for text, the DrawOutliner is used
- Since the DrawOutliner is a single-incarnated, shared ressource, it needs to
be filled newly with text data (OutlinerParaObject)
- Since newly filled, it layouts the text
- With the layouted text, the position is tested against hit
Nothing has changed here from my side. Maybe sd::FuDraw::ForcePointer (or
better: the application) calls PickAnything more often than in older versions?
Maybe Text layout got slower or some buffering broke loose there?
One of the next steps for reworking the office is the controller side what would
include these interaction handlings. Forthe future this IsHit quastion can be
answered by the text primitives which get layouted only once when the more
complex primitive homing them changes.
For the current situaton i see only one possibility:
It makes no sense to try to hold the layouted OutlinerParaObject in the
DrawOutliner to rescue the layout, this changes too often. The only thing i can
think of is to buffer the last input to PickAnything() and it's result and just
try not to call PickAnything too often. Of course this will not really make
things better at real MouseMoves, but i guess it gets called often with the same
position.
AW->HDU: What also is needed is an error description to recreate it. The stack
is nice, but under which circumstances does who have the impression that it is
much slower suddenly than before? Please add information. Also adding some
people to copy who may be involved.
---------------------------------------------------------------------
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]
