On Tue, 17 Aug 2010 18:08:27 -0300, Pierce Wetter
wrote:
Er, yeah, but my point was that the first zone doesn't get a random
suffix, its only the nested zone that does.
Yep, I wasn't clear in first place: I should have said that zones (and
other ClientElement objects) get a random suf
On Aug 17, 2010, at 12:21 PM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 17 Aug 2010 15:33:09 -0300, Pierce Wetter wrote:
>
>>> To avoid creating elements with repeated ids, when you don't provide one
>>> explicitly, the components generate an id with a random suffix.
>> Well, that's not
On Tue, 17 Aug 2010 15:33:09 -0300, Pierce Wetter
wrote:
To avoid creating elements with repeated ids, when you don't provide
one explicitly, the components generate an id with a random suffix.
Well, that's not quite true. That's why it seems like a bug to me.
Will get generated a
On Aug 17, 2010, at 8:53 AM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 17 Aug 2010 10:40:36 -0300, Pierce Wetter wrote:
>
>> Yes, but id kind-of-sort-of gets set by t:id already if its not set.
>> Setting the client id as a workaround to force the id seems bassackwards to
>> me. I'm won
It is a politically correct attempt at saying "ass backwards" ... :-)
mrg
On Tue, Aug 17, 2010 at 11:53 AM, Thiago H. de Paula Figueiredo
wrote:
> I'm not an English native speaker, so what's 'bassackwards'? :)
-
To unsubscrib
On Tue, 17 Aug 2010 10:40:36 -0300, Pierce Wetter
wrote:
Yes, but id kind-of-sort-of gets set by t:id already if its not set.
Setting the client id as a workaround to force the id seems bassackwards
to me. I'm wondering if this is related to 1096.
To avoid creating elements with repeat
On Aug 16, 2010, at 8:14 PM, Thiago H. de Paula Figueiredo wrote:
> On Mon, 16 Aug 2010 23:51:00 -0300, Pierce Wetter wrote:
>
>> Ah, just found that in Jira.
>> So shouldn't setting t:id set the id as well?
>
> They're different ids: t:id is server-side, id is client-side, so I really
> don'
On Mon, 16 Aug 2010 23:51:00 -0300, Pierce Wetter
wrote:
Ah, just found that in Jira.
So shouldn't setting t:id set the id as well?
They're different ids: t:id is server-side, id is client-side, so I really
don't know if that would be a good idea all the time.
You can force a client
On Aug 16, 2010, at 6:50 PM, Thiago H. de Paula Figueiredo wrote:
> Hi!
>
> Provide the zones' ids explicitly and you don't probably have more problems.
>
> There was a recent similar discussion here:
> http://tapestry.1045711.n5.nabble.com/Component-with-a-Zone-and-ActionLink-in-a-loop-td2634
Hi!
Provide the zones' ids explicitly and you don't probably have more
problems.
There was a recent similar discussion here:
http://tapestry.1045711.n5.nabble.com/Component-with-a-Zone-and-ActionLink-in-a-loop-td2634998.html#a2634998,
but with zones inside a loop.
--
Thiago H. de Paula
I found a cool Safari Extension called "Better Source" that helped me get
closer on this problem, I'm hoping someone can help me beyond this. .
Basically, the idea is that I want a grid that is initially hidden. Clicking
on a button reveals a grid, clicking on an item in the grid reveals a d
11 matches
Mail list logo
