It sounds like you were using generate build - this produces minified code
and you'd normally debug/develop with generate source which is entirely
readable. I'm not sure what you were doing wrong but it sounds like there
was one or two fundamental misunderstandings or you were trying to do
Hi Greg,
I tried to run your code but this line:
list.setSelection(a.getItem(0));
threw an exception because the selection expects an instance of
qx.data.Array but getItem returns a number. After replacing it with
slice(0, 1), everything works as expected:
http://tinyurl.com/ntuyyrp
FYI,
Sorry for not having already post a replay... I'm preparing a little bundle
to reproduce the problem, but I need also to work on my project... so I hope
to post all you need asap!
Thx in advance
--
View this message in context:
Greg,
thanks for you feedback.
On 08/29/2013 06:04 AM, Gregory Beaver wrote:
Dear qooxdoo,
I wrote a very complicated application based on qooxdoo a few years
ago. It still works great but there are some kinks that I was trying
to work out. I spent 13 hours over the past week trying to
Hi,
I'm having some problems dealing with a custom config.json.
I plan to use qx.core.Environment outside of a qooxdoo app and I was
planning to create a custom Bootstrap that extend this class by removing the
qx.* keys (except the mandatory ones qx.debug) just to have a really small
final build
Thank you all for the quick feedback. A few responses:
1) the prettify feature in chrome was a new one and will make debugging the
generated accessors possible, one problem solved
2) I debug in source mode, sorry that was not explicit. I am not a
masochist in that way :)
3) although I was
Ack! Accidentally clicked send.
I have a database of composers, the pieces they wrote and the movements of
those pieces. It is sent to qooxdoo as Json, and using a Json marshal made
into 3 classes. The kids property in composers stores the array of pieces,
and the same is true for the kids
On 08/29/2013 10:28 AM, benco wrote:
Hi,
I'm having some problems dealing with a custom config.json.
I plan to use qx.core.Environment outside of a qooxdoo app and I was
planning to create a custom Bootstrap that extend this class by removing the
qx.* keys (except the mandatory ones
Are you using the binding mechanism? There are occasions where the binding
can be a pain with selections, particularly in cases where the selection can
become empty and there is a whole tree of bound widgets; while binding knows
how to apply a value, I often find I have to handle empty selection
Just a thought for when you get back to it then is there a chance that two
bits of code were trying to change the model(s) at the same time? I have
had something similar where recursive binding can cause conflicts and the
wrong things get added/removed - e.g. An event changes the model which
use this Gregory
list.getSelection().push(a.getItem(0));
instead of
list.setSelection(a.getItem(0));
or list.getSelection().removeAll() for no selection
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/stuck-with-qx-ui-list-List-tp7584489p7584503.html
Sent from the qooxdoo
thanks for your time Wagner. This is the most important question, I need
resolve somehow.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/question-about-a-mobile-project-behavior-tp7584484p7584504.html
Sent from the qooxdoo mailing list archive at Nabble.com.
Correct. The selection model is looking for an array, not an object. So,
setSelection([a.getItem(0))]) would also work.
On Thu, Aug 29, 2013 at 11:27 AM, rsantiagopaz rsantiago...@gmail.comwrote:
use this Gregory
list.getSelection().push(a.getItem(0));
instead of
http://tinyurl.com/pqvzhmt
Perfecto. So easy!. ...Sometimes the brain is blocked..
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/question-about-problem-with-command-and-table-tp7584482p7584506.html
Sent from the qooxdoo mailing list archive at Nabble.com.
warning, because if you use setSelection for set other arrays, if you add
listeners previously (like this code below), the events lost.
var list = new qx.ui.list.List(model);
//Pre-Select Item No 20
list.getSelection().push(model.getItem(20));
//log selection changes
Very true, and duly noted. Always better to work with a single selection
model.
On Thu, Aug 29, 2013 at 11:58 AM, rsantiagopaz rsantiago...@gmail.comwrote:
warning, because if you use setSelection for set other arrays, if you add
listeners previously (like this code below), the events lost.
It suddenly occurred
to me this evening, well after I had given up and
erased my code, that there is a simple and elegant solution to my
problems with using a single qx.ui.list.List and swapping the model to
avoid all the headaches with incorrect selection:
qx.ui.container.Stack
So, I
17 matches
Mail list logo
