Re: Bug with exceptionally long values.

Again, I don't know wxWidgets, but usually a custom renderer wouldn't affect
copy/paste because it is merely affecting what's drawn to the screen, not
the value actually "in" the cell. And right now there isn't anything
rendered at all.

On Wed, Jul 28, 2010 at 9:28 AM, Michael Shapiro <mshapiro51(at)gmail(dot)com>wrote:

> I think changing the background but leaving the current value "as is" is
> better than changing the value. That way you indicate that the value is
> there (and can be retrieved with copy/paste) but that you can't show it (and
> perhaps add a pop-up hint when the mouse is moved over the cell)
>
>
> On Wed, Jul 28, 2010 at 8:19 AM, Guillaume Lelarge <guillaume(at)lelarge(dot)info
> > wrote:
>
>> Le 28/07/2010 13:59, Jeff Adams a écrit :
>> > The class that I experience the problem with is the ctlSQLGrid, which
>> > extends wxGrid. I don't know wxWidgets at all, but in the grid sample
>> class
>> > they have an example of setting a cell renderer, perhaps you could add a
>> > cell renderer that changes the background color [or even renders a
>> string
>> > that says "Sorry, too long!"] based on the strlen? That should have
>> fairly
>> > minimal performance impact since it will only affect the N rows being
>> > actually rendered, not the entire result set.
>> >
>> > The example is /wxWidgets-2.8.11/samples/grid/griddemo.cpp line 299.
>> >
>>
>> Well, I think it would hurt the performance. But, we should check that.
>> And it would be a pretty good way to show a NULL value.
>>
>>
>> --
>> Guillaume
>> http://www.postgresql.fr
>> http://dalibo.com
>>
>
>