**** BEGIN LOGGING AT Sun Apr 21 02:59:58 2013 Apr 21 03:33:05 Is there a "enyo is a descendant of" function in enyo? Apr 21 03:33:05 I'm specifically having a problem with the tree control. If I have an object selected and then click an object above that one, the object I just clicked collapses, when really I just want it to become selected. Apr 21 12:48:45 Trex005: not sure if i'd know the answer, but i'm fairly certain i don't understand the question Apr 22 00:20:54 Hey guys, I remember reading somewhere that it was advised against to use Arrays and Objects as published properties of an enyo kind because the changed function couldn't tell the difference between them Apr 22 00:21:17 so what would be the "correct" way in Enyo to use an array? Apr 22 00:21:23 in the kind Apr 22 00:21:26 that is user-definable Apr 22 00:21:53 I need to have one for a combobpx that I am building Apr 22 00:22:52 highlighting: sugardave rrix LarrySteeze madnificent fxspec06 cryptk dkirker Trex005 Apr 22 00:23:06 oh, and summatusmentis Apr 22 00:38:30 I'm not sure I understand what you'rea sking Apr 22 00:50:26 Ok Apr 22 00:50:47 So have you ever heard of Chosen, the jquery/prototype plugin? Apr 22 00:52:42 http://harvesthq.github.io/chosen/ Apr 22 00:52:49 Look at the multiple select examples Apr 22 00:53:01 I'm trying to make something like that for enyo Apr 22 00:53:31 however, I'll need to pass a list of choices that the user can choose from to the element for it to search and populate them Apr 22 00:53:40 which would mean that I would need an array Apr 22 01:07:07 I have heard of chosen, yes Apr 22 01:09:23 so, the thing you remember reading is at https://github.com/enyojs/enyo/wiki/Published-Properties Apr 22 01:09:26 at the bottom Apr 22 01:09:36 I think Apr 22 01:09:49 yes Apr 22 01:10:46 I see 2 ways of dealing with this: 1) do what that suggests, and use .clone(), and just know that it'll call propertyChanged() even if the value doesn't change Apr 22 01:11:08 or 2) give it a string delimited by a character you don't expect to see, and split() when you need to actually handle it Apr 22 01:22:15 Those are both solutions, however, the first option has obvious problems, and the second option is not very friendly for anyone who would try to use my Combobox in their own apps Apr 22 01:23:41 it's not clear that 1 has obvious problems Apr 22 01:23:47 there's a little bit of extra work Apr 22 01:24:10 I agree that 2 isn't super generalizable Apr 22 01:25:19 propertyChanged being triggered twice may not be that big of a deal Apr 22 01:44:45 It's not that propertyChanged will be called twice, but that it will be called every time you use the setter Apr 22 02:10:27 yes, true enough Apr 22 02:10:34 do you expect the setter to be called a lot? Apr 22 02:16:13 Not for my current purposes, but I could see cases where it could in other projects Apr 22 02:21:01 I don't see other options, I suppose you could figure out a way to have multiple properties, where you specify length, and individual properties for the length Apr 22 02:21:08 or rather, for each item Apr 22 02:21:17 but that's unwieldy, and I don't know how it handles changes Apr 22 02:21:30 :\ Apr 22 02:21:56 hwere does propertyChanged trigger? Apr 22 02:23:00 my guess is that during the autogeneration of setters, it adds a check that triggers propertyChanged if they are not equal Apr 22 02:23:20 that's probably true Apr 22 02:24:13 I mean, programmatically, the right way would be to compare the arrays manually, and then trigger propertyChanged Apr 22 02:24:17 if they differ Apr 22 02:25:16 but I don't know if there's a way to override the underlying stuff Apr 22 02:34:33 since we can pass functions in Javascript similar to how you can in C, why didn't they add in support for users to define a compare function for their properties, I wonder? Apr 22 02:35:08 or even so, because of inheritance, we wouldn't even have needed to "pass" such a function Apr 22 02:35:11 just override it Apr 22 02:35:17 or look for it **** ENDING LOGGING AT Mon Apr 22 02:59:58 2013