On 16/12/11 03:04, sub wrote:
> So what do you actually need to do once to get a handle on these objects?
>
> If you are talking about manipulating form data then you really should be
> looking at the data binding packages and examples in the demo browser. With
> data binding you don't really inte
On 12/16/2011 08:31 AM, thron7 wrote:
> You could use the ObjectRegistry, where you can get the hash of a qx
> object (your "ID"), and later look it up from there using this hash. But
> these wouldn't be self-assigned names (strings).
>
> Going away from this.w and this.m you need also be concern
You could use the ObjectRegistry, where you can get the hash of a qx
object (your "ID"), and later look it up from there using this hash. But
these wouldn't be self-assigned names (strings).
Going away from this.w and this.m you need also be concerned that
objects go out of scope and are garbag
So what do you actually need to do once to get a handle on these objects?
If you are talking about manipulating form data then you really should be
looking at the data binding packages and examples in the demo browser. With
data binding you don't really interact with the form widgets but you bind
Might be just my Google-fu, but I haven't really found a way to access
form elements or other Objects by name. In short, I'd find it pretty
convenient if there was a function/method/hash available somewhere (eg.
on the Root, or within a Window, or per container, or something like
that), where I co
