Jesus Reyes wrote:
--- Al Boldi <[EMAIL PROTECTED]> escribió:
Jesus Reyes wrote:
--- Mattias Gaertner <[EMAIL PROTECTED]> escribió:
Can TStringGrid handle 30.000 rows?
Because this is easily created by compiling with -vt and
TListBox
can not handle it fast enough.
I think it can do it, though, atm it's not optimized to handle
very
huge number of rows.
I guess it reduces then to know if replacing the listbox with a
stringgrid actually improves something (the less we would want is
to
do a back step) by trying with a big case, if it works but still
have
problems, I might help by building a new grid (something like
dbgrid
but not tied to db) to handle it.
I think we would need a/some voluteers with very big projects to
actually test this (I have not seen a very huge list in messages
view
btw)
That's because the messages view hides/overwrites most lines,
because
TListBox can't handle that much. Right click on the messages
window, then
select "Copy all and hidden messages to clipboard", and you may see
a lot
more messages especially when compiled with -vt or -va.
Thanks!
--
Al
That means that we already have all those strings in some other place
and only some strings are sent to the listbox? (I have no idea on how
messages works), in this case another approach could be made, a
drawgrid with custom scrollbar handling could do it.
If the TreeView solution is not implemented by the next week I will
take a look.
Jesus Reyes A.
I know that it's maybe crazy idea but what about using sqlite database
or even sqlite in-memory database ?
Records could be cached and displayed only a couple of records, next
loaded on request when user scrolls view (listview or grid or listbox -
).Btw: virtual TListview could be perfect but need to be implemented.
Regards
Boguslaw
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
