On Wed, 11 Jul 2012 12:34:04 -0300, Norman Franke wrote:
I've got those before as well, and that was the problem. Perhaps
Tapestry could handle that better and just select the first item in this
case?
Pallete is a multiple object selection component, so, in my humble
opinion, this soluti
I've got those before as well, and that was the problem. Perhaps Tapestry could
handle that better and just select the first item in this case?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Jul 10, 2012, at 8:11 AM, Thiago H de Paula Figueiredo wrote:
> On Tue, 10 Jul 2
Thanks Thiago I'll bear that in mind, next time the problem occurs
On Jul 10, 2012 1:11 PM, "Thiago H de Paula Figueiredo"
wrote:
> On Tue, 10 Jul 2012 08:54:25 -0300, Jabbar wrote:
>
> I think I found the problem, although I'm not 100% sure. I deleted the
>> data which populated the selected p
On Tue, 10 Jul 2012 08:54:25 -0300, Jabbar wrote:
I think I found the problem, although I'm not 100% sure. I deleted the
data which populated the selected property of the palette component and
then
added the data back into the database. The problem has disappeared.
NPEs in Palette happen
I think I found the problem, although I'm not 100% sure. I deleted the data
which populated the selected property of the palette component and then
added the data back into the database. The problem has disappeared.
The strange thing is I couldn't see anything wrong with the original data.
On 10
