I've looked at the AbstractTreeItem implementation, and it looks like
changing the 'parent' property does nothing on its own. Rather, you have
to use the 'remove' and 'add' methods (which then in turn update the
'parent' property), as indicated in the comments of my Playground code.
T.
On 08/0
This is indeed interesting. I have a slightly modified Playground
sample, for better inspection:
*http://tinyurl.com/l7xatu7
T.
*
On 08/07/2013 09:49 PM, walle wrote:
> I tried to create an example showing what I thought was a bug in the
> Playground. To illustrate my point in the bug report.
I tried to create an example showing what I thought was a bug in the
Playground. To illustrate my point in the bug report.
But now I can't create a version that works, even though it's pretty much
the same code I use in my project.
Am I missing something obvious because I'm tired? Or is this kin
Ok, thanks! I will do that.
Regards,
Fredrik
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Using-model-data-in-tree-to-create-context-menu-etc-tp7584277p7584305.html
Sent from the qooxdoo mailing list archive at Nabble.com.
-
On 08/07/2013 10:28 AM, walle wrote:
>> Daniel, you are a core developer right? I found something that might be a
>> bug, or intended behavior. How do I go about to find out which it is?
Asking on the mailing list is a good first step :-).
>> The issue is that if you call setParent() on a treeIt
> Sounds good to me. One improvement could be to only create two context
> menu instances (one for files and one for folders) and assign them to
> the tree items as needed. From within the menu, you can access the
> "opener" widget (the tree item that was right-clicked) and then get the
> model
Hi Fredrik,
On 03.08.2013 21:57, walle wrote:
> So, I have found a solution to the problem regarding different context menues
> on different types of items.
>
> Now I only use one contextmenu, that is built when the contextmenu event is
> emitted on the tree item. Then I have access to the model d
So, I have found a solution to the problem regarding different context menues
on different types of items.
Now I only use one contextmenu, that is built when the contextmenu event is
emitted on the tree item. Then I have access to the model data and can make
every context menu unique if I would wa
Hello,
I have just started out with qooxdoo. Seems like a really nice framework!
Great work!
Unfortunately, I'm stuck with a problem now. One that I can't find the
solution to in the documentation. I've been reading through the
documentation the last couple of days.
I'm using qooxdoo desktop.
I w
