Hi Janak I cannot reproduce it anymore - very strange... In that case, I suggest to close this issue as 'not reproducible'.
I'm sorry for the confusion. Regards, Etienne -----Original Message----- From: Janak Mulani [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 10:11 AM To: Etienne Studer Cc: [email protected] Subject: RE: [ULC-developer] (UBA-7105) ULCTable#addRowSelectionInterval() and ULCListSelectionModel#setSelectionInterval(int, int) do not fire event in the same sequence Hi Etienne, I checked the code and as far as I can see there is no change. When you call addRowSelectionInterval or setSelectionInterval, the ListSelectionEvent immediately and followed by notification of listeners. The listener is called as part of the same call (i.e. before the statement following these stmts are executed). The client does not send the event in both the cases. You can see this by printing out the stacktrace in your event listener's valueChanged method. Do you have extensions? Are you doing something special there? I hope this helps. Thanks and regards, Janak >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Etienne Studer >Sent: Wednesday, November 22, 2006 8:46 AM >To: [email protected] >Subject: RE: [ULC-developer] (UBA-7105) >ULCTable#addRowSelectionInterval() and >ULCListSelectionModel#setSelectionInterval(int, int) do not fire event >in the same sequence > > >Hi Janak > >I attach the listener during the initialization of a view. After >attaching the listener, I do more initialization. If I call >setSelectionInterval in the latter initialization, my listeners get >called earlier than if I call addRowSelectionInterval (which led to an >exception in my code because initialization was not over, yet). > >I have no self-contained example since I had no extra time to spend on >this problem. Using addRowSelectionInterval seemed like a good enough >solution when the previous selection is empty. But I'm sure you can >find in the ULC core code, that setSelectionInterval vs. >addRowSelectionInterval on a table without a previous selection are >handled differently with regard to when the listeners are notified. > >Regards, Etienne > > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Janak Mulani >Sent: Monday, November 20, 2006 4:10 AM >To: Etienne Studer >Cc: [EMAIL PROTECTED] Com >Subject: [ULC-developer] (UBA-7105) ULCTable#addRowSelectionInterval() >and ULCListSelectionModel#setSelectionInterval(int, int) do not fire >event in the same sequence > >Hi Etienne, > >Could you please explain "an event is fired but it is fired at >different points in time"? > >An event is fired in both cases, but what do you mean by "at different >points in time"? How is it affecting your program behaviour? > >I suspect it could be related to >https://www.canoo.com/jira/browse/UBA-7068 (about order of listners) >but I need more information from you to confirm this. > >Thanks and regards, > >Janak > >>-----Original Message----- >>From: Etienne Studer (JIRA) [mailto:[EMAIL PROTECTED] >>Sent: Friday, November 17, 2006 8:17 AM >>To: [EMAIL PROTECTED] >>Subject: [JIRA] Updated: (UBA-7105) ULCTable#addRowSelectionInterval() >>and ULCListSelectionModel#setSelectionInterval(int, int) do not fire >>event in the same sequence >> >> >> [ https://www.canoo.com/jira/browse/UBA-7105?page=all ] >> >>Etienne Studer updated UBA-7105: >>-------------------------------- >> >> Description: >>We observe different behavior between calling >>ULCTable#addRowSelectionInterval() and >>ULCListSelectionModel#setSelectionInterval(int, int) . I can see that >>in both cases an event is fired but it is fired at different points in >>time. >> >> >> was: >>We observe different behavior between calling >>ULCTable#addRowSelectionInterval() and >>ULCListSelectionModel#setSelectionInterval(int, int) . I can see that >>in both cases an event is fired but it is fired at different point in >>times. >> >> >> >>> ULCTable#addRowSelectionInterval() and >>ULCListSelectionModel#setSelectionInterval(int, int) do not fire event >>in the same sequence >>> >>------------------------------------------------------------------- >>--------------------------------------------------------------- >>> >>> Key: UBA-7105 >>> URL: https://www.canoo.com/jira/browse/UBA-7105 >>> Project: ULCBase >>> Issue Type: Bug >>> Components: core >>> Affects Versions: ULC 6.1.1 >>> Reporter: Etienne Studer >>> Assigned To: ULC Team >>> >>> We observe different behavior between calling >>ULCTable#addRowSelectionInterval() and >>ULCListSelectionModel#setSelectionInterval(int, int) . I can see that >>in both cases an event is fired but it is fired at different points in >>time. >> >>-- >>This message is automatically generated by JIRA. >>- >>If you think it was sent incorrectly contact one of the >>administrators: https://www.canoo.com/jira/secure/Administrators.jspa >>- >>For more information on JIRA, see: >>http://www.atlassian.com/software/jira >> >> >> > >_______________________________________________ >ULC-developer mailing list >[email protected] >http://lists.canoo.com/mailman/listinfo/ulc-developer >_______________________________________________ >ULC-developer mailing list >[email protected] >http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
