VB6 ListView: Why oh why oh why...
Quote:
> I've just recently moved on to VB6 from VB5 and found it far better than
it
> has been cracked down to be.
I'm with you there.
Quote:
> But some things make me wonder. For example, I tend to use the ListView
> control a fair bit. In 5 I had to use API calls for stuff like swapping
> columns, full row select etc. Now in 6 this functionality is exposed
directly
> by the control. But if it was already there via the API, why wait until
now
> to expose it?
The API is for comctl32.dll. Some of the functionality was never a part of
this dll until recently (IE updates). The mscomctl.ocx in VB6 can take
advantage of this new stuff because it has the newer comctl32.dll functions
built-in (which is also why it's almost twice the size of comctl32.ocx from
VB5.)
Quote:
> And the most useful API call is to sort the ListView
> numerically instead of alphabetically - but this is not exposed by the 6
> control! Are Microsoft simply delaying exposing this method until VB7 so
they
> can attract us to convert again with more quick wins?
All of the common controls have features available through API that aren't
properties or methods of the OCX. Like all of VB, you get what you get from
MS and build from there.
Quote:
> And another thing. How do you tell which service pack you have installed
in
> VB6. In VB5 it appeared in the Splash and the About. I work as part of a
team
> of developers coding on different sites, and we are all out of synch
because
> nobody can tell what they've got.
There really are no service packs for VB6. The first SP was a compatibility
fix for VC runtimes and the second to make VJ comply with legal rulings. The
VB6 IDE and runtime never changed.
