Bug 56670 - undefined: XModel/XSelectionSupplier return wrong selection of XShapes and/or added XShape
Summary: undefined: XModel/XSelectionSupplier return wrong selection of XShapes and/or...
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.5.6.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-02 10:28 UTC by Karsten Merkle
Modified: 2013-07-04 14:30 UTC (History)
0 users

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Merkle 2012-11-02 10:28:35 UTC
Problem description: 

Steps to reproduce:
1. install MRI-Tools from
   http://extensions.libreoffice.org/extension-center/mri-uno-object-inspection-tool
2. create a form with input fields
3. group some of them and select group
4. Try tools->Addons-> MRI(Selection) := one of the elements is given 
5. choose enter group and selectan element inside of group
6. again show MRI(Selection) := group is given

This also happens without MRI, whether I call 
- getSelection on the document model 
- getCurrentSelection on SelectionsSupplier
- register as XSelectionChangeListener 


Current behavior:
On first getSelection of new created group an element returns.
After entering group ans selecting, alway the group gets returned, even the UI clearly shows only one XShape is selected.

Spoof: Selecting two fields inside a group returns shapeCollection with two elements... each of them is the group

Expected behavior:
- getSelection on the document model
- getCurrentSelection on SelectionsSupplier
- register as XSelectionChangeListener 
should return a shapeCollection of contained Elements...




Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120918 Firefox/15.0.1 SeaMonkey/2.12.1
Comment 1 Thomas Hackert 2013-07-04 14:30:57 UTC
Hello Karsten, *,
thank you for reporting the bug :)

If I see this correctly (and someone in our chat confirmed it), this is a bug of the extension itself, not from LO ... :( So you should report it to the extension provider, not to our bugzilla. I will close this bug as "NOTOURBUG". If you think, I am wrong here, feel free to reopen it, but than give us a good explanation, why you think, it is ... ;)
Sorry for the inconvenience
Thomas.