Wt

class WtTableCell : public Wt::WTableCell

{

private:

DataView* view;

int Row;

int Column;

public:

WtTableCell( DataView& TheView, int row, int column );

void double_click( const Wt::WMouseEvent& e );

};

@WtTableCell::WtTableCell( DataView& TheView, int row, int column )

: view( &TheView ),

Row( row ),

Column( column )

{

doubleClicked().connect( this, &WtTableCell::double_click );

}

void WtTableCell::double_click( const Wt::WMouseEvent& e )

{

@

I've narrowed it down to the row value being passed in as: 0xffffffff

The Wt function rowNum seems to be culprit.

WTableCell *WTableRow::createCell(int column)

{

return table_->createCell(rowNum(), column);

}

I'm stuck on this point. There is simply not enough documentation about how cells get created.

This function is getting called multiple times with row basically set to --1 (0xffffffff). I thought maybe this was for a header row, but it happens whether I call setHeaderCount or not. Even if it were for a header, why more than one?

Frustrated to not get any response. Searching wt examples, createCell is never used. Should I not be using this approach:

auto tableCell = gridCtl->elementAt( Rec, left() ); // triggers WtTable::createCell

tableCell->addWidget( staticWnd );

In the debugger, I see that createCell is called multiple times for one call to elementAt. I realize that it's expanding to fill cells up to where I've accessed. However, if I start with 0,0 which calls CreateCell with 0,0, then later call elementAt(1,0), I would not expect it to call CreateCell with 0,0 again.

It appears to be a bug, but I could be looking at this all wrong. ANY help would be greatly appreciated.

This change fixed the issue I was seeing. There are no --1s being passed in now. All is well. Thank you so much!