1. Listviews and time....
global function addLVItem(integer id,atom iIcon,sequence text)
Bahh, RECURSIVE AS HELL
What's wrong with it? Everything if you have alot of info to feed your LV!
I was hopeing someone might have an idea how to load in a couple thousand
items to a Listview in a timely manner....
Euman
2. Re: Listviews and time....
Well now, this sounds great......
OfCourse those of us who insist on fast will re-write code/
I haven't had a win32lib that I didnt have to re-code for...
Euman
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Subject: RE: Listviews and time....
>
>
> Euman wrote:
> > global function addLVItem(integer id,atom iIcon,sequence text)
> >
> > Bahh, RECURSIVE AS HELL
> >
> > What's wrong with it? Everything if you have alot of info to
> > feed your LV!
> >
> > I was hopeing someone might have an idea how to load in a
> > couple thousand
> > items to a Listview in a timely manner....
>
> Done.
>
> This has been coded for the new version.
>
> result = Dispatch( integer id, "addItems", sequence items)
>
> where 'id' is the ID for a Listview, Treeview, List, Combo, or imagelist
> 'items' is a list of items.
> For text only items, each element is a text sequence,
> image only items, each element is either a hWnd to a bitmap, or a
> filename.
> text + image items (like listviews) , each element is a 2-element
> sequence
> of atom(Icon) and sequence(Text)
>
> eg.
> sequence result
> result = Dispatch(myListView, "addItems",
> { {wipIcon, {"lib101","Bug","setTextColor() for edit
> controls."}},
> {doneIcon, {"lv027","Enhanc", "New addItems()"}},
> {doneIcon, {"tv012","Enhanc", "New addItems()"}},
> })
> if result[1] = -1 then
> -- Function not supported
> ... do it the long way ...
> end if
>
> This also demonstrates the new Dispatch() function, which allows for
> optional functionality to be implemented. This means that a mild form of OO
> polymorphism is available. It also enables "light" versions of win32lib to
> be created.
>
> This is all optional as all the current functions still exist and no-one has
> to go a rewrite their win32lib code 
>
> Oh, except if your are creating your own imagelists. The current
> implementation only allowed for 32x32 or 16x16 pixel images. To cater for
<snip>
>
>
3. Re: Listviews and time....
There's only one minor problem,
Most of the changes occured before I can get it finished....
I gave up...trying to keep up.
eventually thou, I'll have a Windows Gui worth submital.
Euman
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Subject: RE: Listviews and time....
>
>
> Euman wrote:
>
> > OfCourse those of us who insist on fast will re-write code/
> > I haven't had a win32lib that I didnt have to re-code for...
>
> Please feel free to send in your improvements. I don't want win32lib to be
> slow either!
>
> Other changes in the new version include
> a) the "_full" code has extra error and parameter checking embedded but
> the stripped down editions don't. I achieved this by adding ...
>
> --ASSERT
> . . .
> --END ASSERT
>
> segments in the code and the EuCompress program strips these segments out.
>
> b) I tried to use faster datatypes were possible, eg integer rather than
> atom or object.
>
> c) The inner stack operations used by event handlers are now much faster
> due to a pre-allocated stack size rather than use growing and shrinking
> sequences.
>
>
> -----------
> cheers,
> Derek Parnell
>
>
>
>
>
>
>
