Seems the Option object comes to play. But the Option object must be updated for 0.8.0.
A workaround is to define them as two separate UI modules and check if the defined element exists at runtime, if not switch to the the other definition. Once the Option object has been updated, you can define with one UI module. Thanks, Jian On Fri, Oct 15, 2010 at 9:48 AM, Jade <[email protected]> wrote: > We have a table that has a column of both submit buttons and plain > text. When the user clicks a button, the cell contents change to plain > text. > > If the column were only composed of submit buttons, I would model it > like this: > > SubmitButton(uid: "{row: all, column: 1} as addButtons", clocator: > [name: "*submit_add_eperson_"]) > > and if were all <td> of plain text, then I would model it like this: > > TextBox(uid: "{row: all, column: 1} as addButtons", clocator: [tag: > "td"], self: true) > > The cell values depend on data from the database and whether or not a > person is already a member. > > Also, it seems like I should be able to refer to the SubmitButtons as > "TableUid.addButtons[index]" but I get an error when doing so. > > Thank you, > > Jade > > -- > You received this message because you are subscribed to the Google Groups > "tellurium-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<tellurium-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tellurium-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en.
