Issue 78691

Summary: [API] Tree Control: XTreeExpansionListener implemented in Java freezes the UI when node is expanded
Product: App Dev Reporter: chne
Component: apiAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P2 CC: arielch, issues
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
Document including test macro
Java source for test macro attached none

Description chne 2007-06-20 11:44:52 UTC
If a XTreeExpansionListener is added to UnoTreeControl the office freeze while
try to expand a node via UI. If I use the method expandNode() all works as expected.

cn->cl: please contact me to reproduce the behavior.
Comment 1 clippka 2007-06-20 12:39:12 UTC
must be a java thread issue, in c++ this works
Comment 2 clippka 2007-07-23 17:23:18 UTC
Comment 3 clippka 2008-01-10 09:38:05 UTC
@cl->kso: as I only helped out developing this control for your team, fixing
these issues has not much priority for me. And since I have a tight schedule I
send you this issue to decide if they are important enough to assign other
resources as it is unrealistic to assume that I will work on them any time soon.
Of course you can always escalate with my manager.
Comment 4 kai.sommerfeld 2008-01-10 10:01:18 UTC
Carsten, please take over.
Comment 5 hanya 2012-05-31 14:03:28 UTC
Created attachment 77869 [details]
Document including test macro

Is this issue still valid? I made a small macro to test this problem but 
I don't know this is enough to reproduce the problem.
Comment 6 hanya 2012-05-31 14:04:25 UTC
Created attachment 77870 [details]
Java source for test macro attached
Comment 7 Ariel Constenla-Haile 2012-05-31 14:12:35 UTC
(In reply to comment #5)
> Is this issue still valid? 

I've no idea; I was looking for Tree Control issues and found this with a title that didn't describe the bug well, so I simply changed it (no further testing from my side).

> I made a small macro to test this problem but 
> I don't know this is enough to reproduce the problem.

For comment 1 it seems it was reproducible under certain conditions, unfortunately they didn't attach any code to the bug.
In case we cannot reproduce the bug, we can leave it OPEN but UNCONFIRMED.
Comment 8 Ariel Constenla-Haile 2013-02-13 18:40:57 UTC
Setting status to UNCONFIRMED
It seems the original QA reporter had code to reproduce it, but without seeing it we can't confirm this.