Issue 105154 - framework: erroneous element exist exception adding new uielements
Summary: framework: erroneous element exist exception adding new uielements
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m59
Hardware: Unknown All
: P2 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: stefan.baltzer
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks: 99999
  Show dependency tree
 
Reported: 2009-09-17 16:40 UTC by noel.power
Modified: 2009-12-14 12:49 UTC (History)
1 user (show)

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

Attachments
patch file (517 bytes, patch)
2009-09-17 16:41 UTC, noel.power 		no flags Details | Diff
simple test document (10.77 KB, application/vnd.oasis.opendocument.text)
2009-09-17 16:41 UTC, noel.power 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description noel.power 2009-09-17 16:40:18 UTC 
adding a new menu ( example attached ) or toolbar results in an element exists
exception getting raised ( always )
Comment 1 noel.power 2009-09-17 16:41:13 UTC 
Created attachment 64815 [details]
patch file
Comment 2 noel.power 2009-09-17 16:41:50 UTC 
Created attachment 64816 [details]
simple test document
Comment 3 noel.power 2009-09-17 16:43:48 UTC 
simply push the button in the document,
expected:
 should add a new menu
actual:
 exception raised

I've raise the prio because there are many many macro's out there that
dynamically add custom menus/toolbars and they all currently fail
Comment 4 carsten.driesner 2009-09-18 07:36:29 UTC 
cd->npower: Hi Noel, do you know if this issue describes a regression or not? If
this is a regression I want to raise this issue as a show stopper.
Comment 5 noel.power 2009-09-18 09:18:02 UTC 
Hi Carsten, not sure what you mean by regression, you mean in a released build ?
this problem is in the developer milestones ( I haven't seen it in the ooo310
milestone ), it seems to have crept in since dev300m58, it is a regression in
the sense that it did work and not it doesn't :-) but... afaik dev300m59 is not
yet used for any released builds, just developer snapshots right? if so, I would
think it is an important bug ( hence p2 ) but no showstopper imo anyway
Comment 6 carsten.driesner 2009-09-18 09:43:40 UTC 
cd->npower: Ok, this issue cannot be reproduced in OOO310 and if we don't fix it
in DEV300 which is the base for OOO320 we would have a regression. For me this
looks perfectly like a show stopper.
Comment 7 carsten.driesner 2009-09-18 10:47:19 UTC 
cd: Set target to OOo 3.2.
Comment 8 carsten.driesner 2009-09-18 10:48:25 UTC 
cd: Add issue as a blocker for OOo 3.2 release.
Comment 9 carsten.driesner 2009-09-22 10:16:31 UTC 
cd: Patch committed to CWS fwk118.
Comment 10 carsten.driesner 2009-09-24 12:18:39 UTC 
cd->sba: Please verify issue. You can use the attached document with macros to
check the patch.
Comment 11 stefan.baltzer 2009-09-30 13:23:45 UTC 
Verified in CWS fwk118.
Comment 12 stefan.baltzer 2009-12-14 12:49:00 UTC 
OK in OOO320_m7. Closed.