LiveCode Forums

Hi Mats,
Is there a mechanism to ensure that only a single node can be selected - so that hilitedNodeIDs contains zero or one (the last clicked) node id?

A native rTree property would save having to identify and suppress all the potential handlers that could attempt multiple selections - shift/control/command/whatever-click.
Thanks,
Keith..

Hi Keith!

Is there a mechanism to ensure that only a single node can be selected - so that hilitedNodeIDs contains zero or one (the last clicked) node id?

rTree uses a LC field control to display it´s content. So you can control the hiliting behavior by setting the fields multipleLines (synonym of multipleHilites) and noncontiguousHilites properties to your liking.

All the best!
Mats

Hmm...
The containing field's autoHilite and listBehavior properties are set to true (otherwise there is no node highlighting). Both multipleHilite and nonContiguousHilites are set to false, but it's still possible to hilite multiple contiguous nodes with shift-click (on OSX).

This is what led me to think that there is a hilite behavior being set by rTree?!?
Best,
Keith..

Hi Keith!

I have looked into this. You are right! It seems that rTree is in fact changing the hilite behavior of the field! This is not intended and I will do some bug hunting and get back as soon as I have a resolution. Thanks for bringing my attention to this!

With my best regards!
Mats

Hi Mats,
Thanks for investigating and I'm glad it's not my code for once!
Good luck with tracking it down.
Best,
Keith..

Hi Keith!

I have fixed the bug causing multiple hiliting of nodes. Please download maintenance version 1.5.2 from Tapirsoft or the RunRev store. Thanks again for bringing this to my attention and my apologies for the inconvenience!

With my best regards,
Mats

Hi Mats,
Thanks for the release.
I can confirm that with v1.5.2, shift+click now respects the rTree container field's multipleHilites property setting regarding contiguous highlights.
Best,
Keith..