Issue 114977 - assertion: AccessibleName already set!
Summary: assertion: AccessibleName already set!
Status: CLOSED DUPLICATE of issue 117714
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: DEV300m88
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 3.x
Assignee: Oliver-Rainer Wittmann
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-07 20:10 UTC by 400guy
Modified: 2011-04-06 08:34 UTC (History)
4 users (show)

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

Attachments
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 400guy 2010-10-07 20:10:11 UTC 
I am running a non-product build of DEV300_m88, and I have not
previously set anything within Tools > Options > OpenOffice.org >
Print.


To provoke the assertion ...

(*) Select menu options Tools > Options and open OpenOffice.org >
    Print.  Program displays a dialog with section Reduce print data
    containing a radio button Settings with options Printer (selected)
    and Print to file.

(*) Click on the option Print to file.  Program displays Debug Output
    ...

        Error: AccessibleName already set!
        From File
/home/terry/OOo_hacking/DEV300_m88/vcl/source/window/window.cxx at Line 9160
        Abort ? (Yes=abort / No=ignore / Cancel=core dump)
Comment 1 philipp.lohmann 2010-10-14 13:45:55 UTC 
reason for this is sfx2/source/dialog/printoptions.cxx ImplSetAccessibbleNames.
This was introduced (by od, now on CC) to fix issue 63982 and certainly
implements the behavior described there.

However mt told me, that the accessible name is NOT supposed to be what gets
read (contrary to the description in issue 63982) and should only be unique -
and not be changed since there is no notification for this name change. Whence
the assertion I guess; window.cxx asserts every control the sets a new
AccesibleName when one was already set.

HTH ?
Comment 2 philipp.lohmann 2010-10-26 10:31:11 UTC 
please fix this another way, it would seem that the original issue 63982 is not
actually fixed.
Comment 3 Martin Hollmichel 2011-03-16 10:57:24 UTC 
set target to 3.x since not relevant for 3.4 release.
Comment 4 Mathias_Bauer 2011-04-06 08:34:20 UTC 
I fixed that issue before I found this duplicate

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