Skip to main content



      Home
Home » Eclipse Projects » Nebula » paintedItemListener behavior in CTableTree
paintedItemListener behavior in CTableTree [message #13683] Mon, 09 October 2006 13:08 Go to next message
Eclipse UserFriend
Originally posted by: alnospammajor.noboxspamspoon.com

it appears that paintedItemListener can be called before the
corresponding item (cell) is intialized. is this expected behavior? or a
bug?

al
Re: paintedItemListener behavior in CTableTree [message #13726 is a reply to message #13683] Tue, 10 October 2006 08:41 Go to previous messageGo to next message
Eclipse UserFriend
This is certainly possible behavior...
These events are fired when the container updates its internal
"paintedItems" list by determining which items will be painted to the
screen and which will not. Depending on the implementation, the cell
may wait to initialize until it is painted, in which case
paintedItemListener is called before it is ready to actually be painted.

I think the bigger problem here is that cells do not have a well defined
series of life-cycle events (partly because once you and Cal started
using them, it became apparent that the initial sequence was inadequate
:) ). This problem is also at the heart of your other issue with
getting events for your viewers' creation and disposal, and even the
order in which they initialize.

Please file a bug for this and add your thoughts on what will suit your
use cases best.

Al Major wrote:
> it appears that paintedItemListener can be called before the
> corresponding item (cell) is intialized. is this expected behavior? or a
> bug?
>
> al
Re: paintedItemListener behavior in CTableTree [message #13769 is a reply to message #13726] Tue, 10 October 2006 14:25 Go to previous message
Eclipse UserFriend
Originally posted by: alnospammajor.noboxspamspoon.com

>
> I think the bigger problem here is that cells do not have a well defined
> series of life-cycle events (partly because once you and Cal started
> using them, it became apparent that the initial sequence was inadequate

agreed. i guess that's why the widget is alpha ;-).

> :) ). This problem is also at the heart of your other issue with
> getting events for your viewers' creation and disposal, and even the
> order in which they initialize.
>
ya. what i'll do is attempt to get everything working in some fashion,
possibly with changes to the widget/viewer sources. then i'll have a
better sense of all the problems and potential solutions.

> Please file a bug for this and add your thoughts on what will suit your
> use cases best.
>

hopefully i'll be able to do the above and file the bug within a week.

al
Re: paintedItemListener behavior in CTableTree [message #566491 is a reply to message #13683] Tue, 10 October 2006 08:41 Go to previous message
Eclipse UserFriend
This is certainly possible behavior...
These events are fired when the container updates its internal
"paintedItems" list by determining which items will be painted to the
screen and which will not. Depending on the implementation, the cell
may wait to initialize until it is painted, in which case
paintedItemListener is called before it is ready to actually be painted.

I think the bigger problem here is that cells do not have a well defined
series of life-cycle events (partly because once you and Cal started
using them, it became apparent that the initial sequence was inadequate
:) ). This problem is also at the heart of your other issue with
getting events for your viewers' creation and disposal, and even the
order in which they initialize.

Please file a bug for this and add your thoughts on what will suit your
use cases best.

Al Major wrote:
> it appears that paintedItemListener can be called before the
> corresponding item (cell) is intialized. is this expected behavior? or a
> bug?
>
> al
Re: paintedItemListener behavior in CTableTree [message #566564 is a reply to message #13726] Tue, 10 October 2006 14:25 Go to previous message
Eclipse UserFriend
>
> I think the bigger problem here is that cells do not have a well defined
> series of life-cycle events (partly because once you and Cal started
> using them, it became apparent that the initial sequence was inadequate

agreed. i guess that's why the widget is alpha ;-).

> :) ). This problem is also at the heart of your other issue with
> getting events for your viewers' creation and disposal, and even the
> order in which they initialize.
>
ya. what i'll do is attempt to get everything working in some fashion,
possibly with changes to the widget/viewer sources. then i'll have a
better sense of all the problems and potential solutions.

> Please file a bug for this and add your thoughts on what will suit your
> use cases best.
>

hopefully i'll be able to do the above and file the bug within a week.

al
Previous Topic:SWTPlus controls
Next Topic:Highlighting over item bounds
Goto Forum:
  


Current Time: Fri May 09 03:44:44 EDT 2025

Powered by FUDForum. Page generated in 0.05051 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top