next »

[hawkwind]

Whats the design concept with NearestPickListeners type stuff??  I just resync'd with xith and my picking is now different.  I was wondering what led to this change??

[Marvin Fröhlich]

Whats the design concept with NearestPickListeners type stuff??  I just resync'd with xith and my picking is now different.  I was wondering what led to this change??

I have changed the picking system to be absolutely GC-friendly. Thsi was only possible by caching the PickResult instances. To not force the user to push the used instances on the heap (which he would forget and which would lead to memory leaking) I used the listener system, which was anyway there for scheduled picking.

btw. If anyone has a better name for "AllPickListener", please tell me.

Marvin

['n ddrylliog]

Marvin, why the need to have two different pick listeners ? One interface is sufficient and can be used by the two methods..

[Marvin Fröhlich]

Marvin, why the need to have two different pick listeners ? One interface is sufficient and can be used by the two methods..

There's "NearestPickListener" and "AllPickListener". And there's "PickListener", that unites the two. This is usefull to avoid having always one empty phantom method stub, that you won't use. But you can simply use PickListener and you will have what you want.

Marvin

[hawkwind]

thanx for the info