Issue 112599 - Crash when dragging open text filed after callout shape
Summary: Crash when dragging open text filed after callout shape
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: DEV300m82
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 12:29 UTC by wolframgarten
Modified: 2017-05-20 11:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Screenshot of a selection problem in calc (9.52 KB, image/png)
2010-07-26 14:52 UTC, clippka
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description wolframgarten 2010-06-22 12:29:54 UTC
How to reproduce it 
1 Create a new Calc document
2 Hit 'Show Draw Functions' on Standard bar to show the Drawing bar
3 Choose Text or Callouts on the Drawing bar, drag and draw a Text or Callouts
  in the new Calc file, then enter some characters in the Text or Callouts,
  select all of characters, rightclick - Default
4 Select the texttool from the toolbar and drag open a text area: Office crashes
Comment 1 redflagzhulihua 2010-06-23 02:42:10 UTC
I assume this bug exists in the CWS? Because MWS build will crash after step 3.
How we deal with that CWS then? Will we think this bug is introduced by this
CWS? If so, the CWS will not pass. If not, we will have to start a new CWS to
handle this bug related to the old one. What the action will be take at Sun?

Thanks,
Comment 2 wolframgarten 2010-06-23 10:33:40 UTC
This is also part of the master. Proceeding the issue i97336 in another way does
not lead to the crash of i97336 but lets you drag the texttool what leads to
this crash here i112599.
Comment 3 redflagzhulihua 2010-06-25 02:38:38 UTC
Hi wg,

Thank you, I got it. I wonder, if the scenario happens, that is, a new bug found
after a bug is fixed, but the new bug is not introduced by the bug fixing. What
will we do to the cws? Will we fail the cws and fix the new bug? or will we pass
the cws and fix the new bug in a new cws?

Thank you.
Comment 4 wolframgarten 2010-06-25 06:19:57 UTC
Since the original issue is fixed as it is described I think we will fix the new
crash in a separate CWS.
Comment 5 redflagzhulihua 2010-06-28 02:24:04 UTC
Hi wg,

Thanks for telling me.
Comment 6 clippka 2010-07-26 14:50:53 UTC
so far I tried m85 and m1 on windows and linux on two pc and can not reproduce
the crash.
What I see is some strange selection painting in calc, maybe this is also the
source of the crash.

cl->aw: please have a look at the wrong selection handling, see screenshot for
one example
Comment 7 clippka 2010-07-26 14:52:31 UTC
Created attachment 70823 [details]
Screenshot of a selection problem in calc
Comment 8 Armin Le Grand 2010-08-06 13:09:29 UTC
AW: Did some experiments. Interesting is that when once de-selecting the scape
and selecting it again, applying default on the text does nothing wrong. Seems
to have to do with the not-yet-ready state of the newly created object in edit mode.
Taking a look how Default is handled...
Comment 9 Armin Le Grand 2010-08-06 13:19:10 UTC
AW: Also happens with a rectangle when in TextEdit mode.

- new calc
- create rectangle
- enter text
- select text
- apply 'Default' from the context menu

->Problems (C++ exceptions?) which indicate a former exception inside system Paint()

It plays no role if the rect was deselected in-between.

The same works in SW, so i guess applying 'Default' using the active EditEngine
does something different in SC as compared to SW.

AW->NN: Can You check where and how this is implemented in SC? Unfortunately i
have no idea what happens. Somehow the active EditEngine triggers something in
the application which then does some action on DrawingLayer. Here, SC seems to
do something different from SW.
Comment 10 niklas.nebel 2010-08-25 15:35:50 UTC
Does anybody still see a crash? The selection error alone doesn't need the 3.3
target.
Comment 11 wolframgarten 2010-08-26 09:40:31 UTC
No crash reproducible anymore on OOO330m5, Prio and Target changed.
Comment 12 Marcus 2017-05-20 11:11:06 UTC
Reset assigne to the default "issues@openoffice.apache.org".