[VB6] Modern Shell Interface Type Library - oleexp.tlb

[fafalone]

Hi Jon,
it starts to confuse me: this thread slightly tends to be more and more a tB thread. Although the work for oleexp is the base for both universes they are not the same. I am not using tB (besides some experiments) but extensively use olexep.tlb in my VB6 projects. So I have to sort out here which posts are refering VB6 and which tB. IMO theese should be devided into two separate threads.
Another example for this is your github rep. The source for oleexp is included there but not updated to the current version(s). So it makes no sense for me to collaborate on github.
Background: At the moment I am working on a DirectShow project. I decided to switch back to DS from MF because it is not supported in the same way as DS was. For more advanced tasks it is much easier to develop using DS - MF is a nightmare here. (I constantly watch the blog posts on alax.info). So I found several missing DS components in oleexp (e.g. IMediaSeeking, IMediaParamInfo, IMediaParams, DMO parts, ...) and expanded ext_dshow.odl myself to make my own TLB. Works now but it is cumbersome to update this include component in every new version of oleexp you publish.
If the oleexp source would reside on github I could participate instead of always doing my private work. But only if it was separate from tB. Sure I could post my modifications to ext_dshow.odl here in the thread but it would be more comfortable to make changes on github (commited by you). You called it an opensource project, so github would be the right way. Your opinion?

Apart from followups to specific comments I always say 'in tB' or similar. It's not exactly the same but it's in the sense of VB3 is still the same language; it's de facto VB7, albeit in a beta stage of the kind Microsoft doesn't do publicly. So there's just too much overlap to fully sequester the two, especially since WinDevLib is the official follow-up to oleexp, suggested to use in place of oleexp in tB, and oleexp is the base for its interfaces and I try to keep them reasonably compatible (also APIs, lots of work adding overloads for oleexp compat).

I know some people don't use tB yet and some projects aren't compatible yet, but I'm not going to pretend it's like I'm here talking about Python, .NET, or some other off topic different language. oleexp.tlb adds LongPtr to VB6 and the code differences range from none to minor such that I consider tB code a perfectly serviceable response to questions... this is my hobby not my job.

The copy of oleexp in the WDL repo is purely for reference; you'll find no links to it anywhere and I haven't even mentioned it. Definitely not meant as the main source or for editing; it's not even complete, no addon bas files or compiled tlbs.

I've been keeping my VB6 projects to the VB6 CodeBank... but even with tB I'm still a bit of a luddite with git for my hobby projects... when someone submits a PR I just manually merge it into my local source by copy/paste from the diff, source has no automatic sync ability.

If you've expanded DirectShow I'd be excited to include it in the main source and credit you for it (I've recently started some expansion too); but are the changes so much more than exp_show.odl that you couldn't just attach it here? Then i'll make sure the new releases are in sync with the latest file posted here (and yes you don't care but they'll also appear in WDL first, signatures matched with your version).

If the changes involve a bunch of files yeah I guess github makes more sense; let me know if that's the case and I'll make a dedicated git repo so it's easier for you.

[SaschaT]

Ok, understood.
No, in summary there are not so much modifications and additions I did to the source. As for you VB6 is just a hobby and I spend most of my time with python. Unfrequently I stumble upon an interesting topic and launch VB6 because there is no faster way for me to develop some routines.
But I really forgot all the places where I added or altered the source, so I will have to do a text comparison to the orginals and extract them. Will post them here - probably along with a graph based DirectShow demo similar to this one: https://www.vbforums.com/showthread....=1#post5612190
(BTW: I can reveal that I change most lpwstr/bstr parameters I find to long . There a still many places.)

[VanGoghGaming]

(BTW: I can reveal that I change most lpwstr/bstr parameters I find to long . There a still many places.)

Long is king, he just doesn't want to admit it!