[VB6] - WinRT Interfaces & XAML Islands TypeLibs for VB6/VBA x86 and VBA7 x64

This project has already been available for quite some time as a package on the twinBASIC server and I finally got around to exporting it as a TypeLib (both 32-bit and 64-bit) for whoever wants to use it in their VB6 and VBA projects. The TypeLibs contain extensive coverage of the most popular WinRT namespaces although they are far from complete.

The twinBASIC package contains a changelog with what is currently included:

Code:

---

1.0.0.5  - Preliminary public release
            Windows.ApplicationModel
            Windows.ApplicationModel.AppService
            Windows.ApplicationModel.Background
            Windows.ApplicationModel.DataTransfer
            Windows.ApplicationModel.DataTransfer.DragDrop
            Windows.Data.Json
            Windows.Data.Pdf
            Windows.Data.Xml.Dom
            Windows.Devices.Input
            Windows.Foundation
            Windows.Globalization
            Windows.Graphics.Capture
            Windows.Graphics.DirectX.Direct3D11
            Windows.Graphics.DirectX
            Windows.Graphics.Imaging
            Windows.Graphics
            Windows.Media.Ocr
            Windows.Security.Credentials.UI
            Windows.Security.Cryptography
            Windows.Storage
            Windows.Storage.Pickers
            Windows.Storage.Pickers.Provider
            Windows.Storage.Provider
            Windows.Storage.Streams
            Windows.System
            Windows.System.Threading
            Windows.UI
            Windows.UI.Core
            Windows.UI.Input
            Windows.UI.Notifications
            Windows.UI.Popups
            Windows.UI.Text
            Windows.UI.WindowManagement
            Windows.Xaml
            Windows.Xaml.Controls
            Windows.Xaml.Controls.Primitives
            Windows.Xaml.Data
            Windows.Xaml.Hosting
            Windows.Xaml.Input
            Windows.Xaml.Markup
            Windows.Xaml.Media
            Windows.Xaml.Media.Animation
            Windows.Xaml.Media.Imaging
            Windows.Xaml.Media.Media3D
            Windows.Xaml.Navigation
            Windows.Web
1.1.0.10  - Added namespaces:
            Windows.ApplicationModel.AppService
            Windows.Devices.Core
            Windows.Devices.Enumeration
            Windows.Media
            Windows.Media.Audio
            Windows.Media.Capture
            Windows.Media.Capture.Core
            Windows.Media.Capture.Frames
            Windows.Media.Casting
            Windows.Media.Core
            Windows.Media.Devices
            Windows.Media.Devices.Core
            Windows.Media.Editing
            Windows.Media.Effects
            Windows.Media.FaceAnalysis
            Windows.Media.MediaProperties
            Windows.Media.Playback
            Windows.Media.PlayTo
            Windows.Media.Protection
            Windows.Media.Streaming
            Windows.Media.Streaming.Adaptive
            Windows.Media.Transcoding
            Windows.Networking
            Windows.Networking.BackgroundTransfer
            Windows.Networking.Connectivity
            Windows.Networking.Sockets
            Windows.Security.Authentication.Web
            Windows.Security.Credentials
            Windows.Security.Cryptography.Certificates
            Windows.Security.Cryptography.Core
            Windows.System.RemoteSystems
            Windows.UI.Xaml.Documents
            Windows.Web.Http
            Windows.Web.Http.Filters
            Windows.Web.Http.Headers
1.2.0.17  - Added namespaces:
            Windows.ApplicationModel.Search
            Windows.Devices.Printers
            Windows.Graphics.Display
            Windows.Graphics.Effects
            Windows.Graphics.Printing
            Windows.UI.Composition
            Windows.UI.Composition.Effects
            Windows.UI.Xaml.Shapes
1.3.0.30  - Added namespaces:
            Windows.System.Threading.Core
            Windows.System.Profile
            Windows.UI.Xaml.Interop
            cAwait
            cBindableVector
            cPop
            mdlSubclass
1.4.0.64  - Added namespaces:
            Windows.Data.Text
            Windows.Devices.SerialCommunication
            Windows.Storage.BulkAccess
            Windows.Storage.Search
            Windows.UI.Text.Core
            Windows.UI.ViewManagement
          - Added support for ByVal UDTs as well as helper methods and properties for many UDTs:
            Color, CornerRadius, DateTime, Duration, FontWeight, GeneratorPosition, GridLength, HSTRING, KeyTime, Matrix, Matrix3D, POINTF, RepeatBehavior, RECTF, SIZEF
            UUID, Thickness, TimeSpan, WindowId
1.5.0.107 - Added namespaces:
            RoMetaDataApi (refactored mdlNamespaces to resolve runtime class names from MetaData (*.winMD files) instead of hard-coding them in a XML file)
            Windows.Data.Html
            Windows.Media.Playlists
            Windows.Media.SpeechRecognition
            Windows.Media.SpeechSynthesis
1.6.0.125 - Added namespaces:
            Windows.UI.Composition.Core
            Windows.UI.Composition.Desktop
            Windows.UI.Composition.Diagnostics
            Windows.UI.Composition.Interactions
            Windows.UI.Composition.Scenes
            Windows.Web.UI
            Windows.Web.UI.Interop

---

The backbone of any VB6 project using WinRT classes is the NewObject function that instantiates an activatable WinRT class and provides access to its interfaces. On the first call it also parses the system .winmd metadata files and builds a collection of activatable classes (this process is very fast, well under 100ms) so that subsequent instantiations are pretty much instant.

Here's an example of how to instantiate the MediaPlayer runtime class:

Code:

---

' Sample usage:
Dim MediaPlayer As IMediaPlayer
    Set MediaPlayer = NewObject("MediaPlayer")

---

I'll be updating this collection with some sample projects described below showcasing the usage of these TypeLibs with various WinRT classes:

Download the Attachment 196110

Here are the TypeLib files:

• Attachment 196111 - for VB6/VBA (32-bit)
• Attachment 196112 - for VBA7 (64-bit)
• twinBASIC users should continue using the package (although these TypeLibs work just fine as well)

Requirements: Windows 10 or later!

How are you getting things to show up in a typelib... I know just compiling as an ActiveX DLL isn't enough.

If it becomes easy enough I might do it with WDL though the tB-only features are really piling up.

Here are 3 sample projects using the WinRT TypeLib in VB6:

- Windows Hello Demo (verifying user's identity via PIN or biometrics)

This project demonstrates the usage of "Windows Hello" in WinRT to verify the identity of a user (by means of entering the user's PIN or biometrics such as fingerprint scanner or face recognition if available).

Attachment 195780

In case the user hasn't set up a PIN or biometrics (fingerprint or face recognition), the app will fall back to Username/Password verification:

Attachment 195781


- Stream Sockets SSL Demo (here we are connecting to the Gmail SMTP server and issue various SMTP commands as an example)

Attachment 195778

The screenshot above shows how a usual session might unfold:

• We start with the ubiquitous HELO greeting (or its dyslexic sibling EHLO).
• Then we attempt authentication with AUTH LOGIN to which Gmail says no, we need an encrypted connection for that so we comply with the STARTTLS command!
• After that the AUTH LOGIN command works fine and we are prompted for a username and password (these need to be BASE64 encoded).
• Here we enter bogus credentials but a valid username and app password (not your main Gmail password!) will work correctly!
• Next steps would be sending various MIME encoded headers composing your actual message and recipients list (not included here for brevity).
• Finish with QUIT!

- Media Player Audio

This project shows how to use the WinRT MediaPlayer class to play audio files (MP3, FLAC, AAC, M4A, etc). It can play local files as well as files from the web.

Basic functionality includes: Play, Pause, Volume Adjustment, Playback Rate (faster/slower) as well as Duration Remaining:

Attachment 195779


These sample projects are all included in the WinRT Samples Collection.zip archive linked in the first post above.

Requirements: Windows 10 or later!

Quote:

---

Originally Posted by fafalone

How are you getting things to show up in a typelib... I know just compiling as an ActiveX DLL isn't enough.

If it becomes easy enough I might do it with WDL though the tB-only features are really piling up.

---

An ActiveX DLL is exactly all you need. Interface definitions are included by default. API function declarations are exported successfully with [ComExport]. Aliases, Types and Enums are exported ONLY if they are used somewhere (for example in an interface method or API function).

It is not unusual to define Aliases, Types or Enums that are not used anywhere so in order to get these exported I've added a bogus interface just for this purpose:

Code:

---

[Hidden] Interface DummyInterface Extends Nothing
[Restricted] Sub A(A As APPBARDATA)
[Restricted] Sub B(B As BITMAP, B As BITMAPINFO, B As BITMAPINFOHEADER)
[Restricted] Sub C(C As CLIPBOARD_FORMATS, C As COMMON_CONSTANTS, C As CorTokenType, C As CorTypeAttr, C As CREATION_DISPOSITION)
[Restricted] Sub D(D As DIALOGCOMMANDIDS_CONSTANTS, D As DIB_COLORS, D As DRAWTEXT_FLAGS)
[Restricted] Sub E(E As EDIT_MESSAGES, E As EDIT_NOTIFICATIONS, E As EDITSTYLES_FLAGS)
[Restricted] Sub F(F As FILETIME, F As FONTDESC, F As FILEATTRIBUTE_FLAGS, F As FONTWEIGHT_CONSTANTS, F As MENU_FLAGS)
[Restricted] Sub G(G As GENERALINPUT, G As GENERICACCESSRIGHTS_FLAGS)
[Restricted] Sub I(I As ICONIDS_CONSTANTS, I As INPUT_FLAGS)
[Restricted] Sub K(K As KEYBDINPUT)
[Restricted] Sub M(M As MENUITEMINFOW, M As MOUSEINPUT)
[Restricted] Sub P(P As PICTDESCBMP, P As POINTL, P As POINTSHORT, P As PLAYSOUND_FLAGS)
[Restricted] Sub R(R As RECTL, R As RECTSHORT, R As RGBQUAD, R As REGISTRY_PREDEFINED_KEYS)
[Restricted] Sub S(S As SHFILEOPSTRUCTW, S As SYSTEMTIME, S As SAFE_ARRAY_FEATURES)
[Restricted] Sub T(T As TRACKMOUSEEVENT, T As TOOLTIPICON_CONSTANTS)
[Restricted] Sub U(U As UISTATE_CONSTANTS)
[Restricted] Sub V(V As VS_FIXEDFILEINFO)
[Restricted] Sub W(W As WIN32_FILE_ATTRIBUTE_DATA, W As WINDOWPLACEMENT, W As WINTRUST_DATA, W As WINTRUST_FILE_INFO, W As WAIT_CONSTANTS, W As WINDOWACTIVATION_CONSTANTS, W As WINTRUSTDATA_CONSTANTS)
End Interface

---

As you can see this DummyInterface contains alphabetic methods with parameters including all types and enums that didn't fit elsewhere for the sole purpose to be exported in the TypeLib. It does the job just fine for this WinRT TypeLib since only limited Win32 coverage is needed but for your WinDevLib you may need a whole lot more dummy methods! :D

Might be a new feature to export interfaces... didn't in the past. I tried but got a 'can't finalize interface' error for ID2D1RenderTarget, which works fine when I use it. UDTs yeah, there's like 400 "unused" UDTs alone just for a few QueryInfo APIs like NtQuerySystemInformation lol

Oh well, back to my position that people should just use tB :D

Here's another sample project, this time showcasing how to use a XAML Island inside a VB6 Form! This project is an Animated GIF Player, playing a list of some random animated GIFs directly from the Internet. You can easily expand this menu to include additional images (GIF or any other format) either from the Internet or from your computer:

Attachment 195783

A XAML Island can be embedded in any VB6 control that has a hWnd property (including the Form itself), here we are using a vanilla PictureBox as a container for the XAML Island. As for the actual XAML controls, we are using a Grid control (for setting the background color to match the Form's color so that transparent GIFs don't play against a black background) and an Image control to display the actual GIF image (not to be confused with the classic VB6 Image control!).

You can compile and run the executable as it is but if you want to run this project from the VB6 IDE then there's an additional step that needs to be performed:

- If your VB6.EXE file is not manifested then simply copy the included VB6.EXE.manifest file in the same folder as VB6.EXE (usually: C:\Program Files (x86)\Microsoft Visual Studio\VB98). Probably requires a computer restart so that the manifest takes effect.

- If your VB6.EXE is already manifested then you need to edit its manifest (with Resource Hacker for example) and add the <maxversiontested Id="10.0.18362.0"/> attribute as shown in the included manifest file.

Download this project from the WinRT Samples Collection archive linked in the first post above!

prjGIFPlayer.vbp wouldn't compile in VB6 with MAKERES.BAT (or manually) but fails on Line 4 of frmGIFPlayer.frm.

Where is LongPtr enum declration supposed to come from? I cannot find it in WinRT Interfaces x86.tlb. Is there a dependency typelib I'm missing on my machine?

cheers,
</wqw>

You need to extract the whole archive not just the GIFPlayer project folder, it needs the modules from the Common folder since they are used by all included projects.

There are no other dependencies. LongPtr is present in the TypeLib but it's not an Enum:

Code:

---

    typedef [public]
    long LongPtr;

---

It was old version of the TLB I had registered on my system somewhere. It's such a PITA to upgrade these. Even after registering the new one the project refused to change project reference to it. Had to remove project reference, save project and exit IDE. Then reload and add new reference to manually upgrade to the new one. All this is self-inflicted of course, should have just unzipped the sources with overwrite the second time. Aaaanyway. . . all working now (not in the IDE as my VB6 manifest is apparently incomplete and I'm just too lazy to fix it:-)).

Edit: Manifest fixed

Edit2: Need to upgrade my UMMM manifest creator to include maxversiontested if anyone is going to be using XAML islands with it.

cheers,
</wqw>

Good stuff! :thumb:

Usually TypeLib files are pretty painless to upgrade, just overwrite the old TLB file with the new one and you're done. There is no additional registration needed, the GUID stays the same.

Quote:

---

Originally Posted by wqweto

Edit2: Need to upgrade my UMMM manifest creator to include maxversiontested if anyone is going to be using XAML islands with it.

cheers,
</wqw>

---

You've got a bunch of hard-coded processorArchitecture=""X86"" in it too, shouldn't limit it to 32bit as it would be useful for tB too if you needed more than visual styles. "*" works for both 32 and 64bit; a 64bit app with x86 won't run on 64bit Windows.

Quote:

---

Originally Posted by wqweto

Edit2: Need to upgrade my UMMM manifest creator to include maxversiontested if anyone is going to be using XAML islands with it.

---

I did this for you in the latest UMMM source from GitHub but before I commit it, I would like to to run my approach by you for your approval/rejection:

The SupportedOS INI param will now accept a version number as one of the values, and if detected will set the maxversiontested Id attribute to that version for the compatibility->application section, e.g.:

Code:

---

SupportedOS vista win7 win8 1.2.3.4

---

In the INI will produce this in the .manifest:

Code:

---

    <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
        <application>
            <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" />
            <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" />
            <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" />
            <maxversiontested Id="1.2.3.4" />
        </application>
    </compatibility>

---

It's smart enough to check that the version # is 4 sections of numbers only, and if more than one version # is passed, it will error out.

Feels a bit clunky to overload the SupportedOS INI parameter this way though, but the other option of having a second MaxVersionTested INI param would require a bit of refactoring of how the manifest is built (we'd have to store the SupportedOS and MaxVersionTested values and only build the manifest once the whole file has been processed and all of the SupportedOs/MaxVersionTested values were read). If you'd prefer this approach, let me know and I can do it. If you have an even better idea, I'll leave you to it ;)

@wqweto - I wasn't happy with overloading the SupportedOS command with a version # value for maxversiontested, so I went ahead and added an AppCompat section cache that is used to build the appropriate manifest section after reading all SupportedOS and MaxVersionTested commands. Also went ahead and committed it to the main repo, but feel free to revert of course if you had something better in mind.

Can we please leave the manifest commits and pull requests out of this thread if we're not interested in the topic at hand? Cheers jpbro! ;)

This maxversiontested attribute is just a Microsoft nuisance the same as the PtrSafe keyword, it doesn't actually do anything other than hindering you. The "10.0.18362.0" number is suggested by Microsoft and probably marks the Windows version that first introduced the UWP controls to unpackaged desktop apps via XAML Islands. For all intents and purposes it should be treated as a constant. A lower number won't let you instantiate the DesktopWindowXamlSource object, while a higher number will restrict users with older Windows versions even though your app would run just fine on their systems in all likelihood. So just hard-code this magic number in your manifest and call it a day, there are numerous other ways to test whether a specific feature is present or not on the target computers.

On a more related note, here's another sample project where we are using the XAML MediaPlayerElement control to play various media files (".mp4", ".mkv", ".wmv", ".avi", ".mov", ".3gp", ".mp3", ".m4a", ".wma", ".flac", ".wav" and many others). It has built-in controls for selecting Volume, Casting to other devices, Aspect Ratio and other metadata properties that may be present in the file (such as Subtitles, Director Commentary, etc).

This screenshot looks like something you'll hear from ChatGPT or Claude in the near future! :bigyello:

Attachment 195785

The project is also showcasing the FileOpenPicker class to show a modern interface for selecting files (double-click on the form to start). The FileOpenPicker doesn't like the IDE running elevated (as administrator) so compile this project and run the executable to see it in action. Alternatively if you are aren't running VB6 elevated then it will also work in IDE.

Download this MediaPlayerVideo project from the WinRT Samples Collection archive linked in the first post above!

Sorry, thought it was related to the WinRT XAML islands stuff since the MS docs say that maxversiontested "is intended to be used by desktop applications that use XAML Islands and that are not deployed in an MSIX package.". 'Twas only trying to help spare some headaches down the road for anyone building their own XAML Islands apps using your techniques while using uMMM to compile their manifests, but I shall leave :)

It's fine mate don't worry about it, as I mentioned above it's just a nuisance that needs to be hard-coded in the manifest when you plan to use XAML Islands (all these sample projects already have it) and not worth dwelling on since it doesn't offer any benefits to make it editable.

good job

The following sample is an upgrade to this OCR Text Recognition from a PictureBox Image project from two years ago when there was no WinRT TypeLib and DispCallFunc was king! It's actually more of a complete rewrite of this project using the modern WinRT Canvas and ScrollViewer controls instead of the classic PictureBox of yonder years. Now you can Ctrl+MouseWheel to Zoom In/Out and also scroll around the picture (both horizontally and vertically).

The bounding rectangles for recognized words have attached tooltips showing the word they encompass and also benefit from built-in antialiasing (more visible for angled text). There's also some basic preprocessing done on the image to help with better recognizing text in lower quality images. The image is enlarged 1.5x times and converted to grayscale. This does improve results although nothing groundbreaking.

Attachment 195795

It also showcases the WinRT Clipboard object that exposes a handy event which fires whenever the clipboard contents are changed. Whenever the clipboard contains an image with recognizable text, it is automatically processed.

Another novelty worth noting is that we don't need an Image control for this. The Clipboard image is painted directly on the background of the Canvas control using an ImageBrush object. Also the Canvas control acts as a container for any number of children controls like the bounding rectangles for recognized words and as such we can assign individual tooltips for each rectangle. Much of the trigonometry required to draw angled rectangles is abstracted away by a RotateTransform object that calculates everything automatically.

Finally the ScrollViewer control provides hardware-accelerated Zoom In/Out capabilities as well as scrolling in both directions.

Download this OCR project from the WinRT Samples Collection archive linked in the first post above!

Why do you need AllowUnsafeObjectPassing for the OCR sample?

Btw, cEventsSink seems quite backwards. It could raise an event when some of the handlers is invoked (instead of forwarding to yet another callback).

cheers,
</wqw>

AllowUnsafeObjectPassing is needed when you use a regular class (instead of a form) for handling events or async operations callbacks. There are two events in the OCR sample (ClipboardContentChanged and PointerWheelChanged).

cEventsSink acts as a sort of aggregator for events. It puts them all in one place and assigns an "identifier" or "tag" so that you can tell which event was invoked. Each event is assigned a separate instance of cEventsSink so that you could tell them apart.

If there was only one instance of cEventsSink (declared WithEvents as you suggested) then (in some cases) you wouldn't know which event was raised since in WinRT many events share the same type. For example PointerRoutedEvents are all of type IPointerEventHandler so without identifier tags you wouldn't know if the event was a mouse down, mouse up, mouse move, etc, so I came up with the idea of aggregation (not necessarily sure whether it's the best approach but it works great so far).

Quote:

---

Originally Posted by VanGoghGaming

cEventsSink acts as a sort of aggregator for events. It puts them all in one place and assigns an "identifier" or "tag" so that you can tell which event was invoked. Each event is assigned a separate instance of cEventsSink so that you could tell them apart.

---

You could have multiple WithEvents instances of cEventsSink.

It's unusual to have objects ending up in ROT. Apparently there is some cross-process shenanigans going on with WinRT or just multi-threading in the same process, not sure.

cheers,
</wqw>

Well yeah, you could have multiple WithEvents instances of cEventsSink but I guess it's a matter of preference, I'd rather have them all aggregated in one place than scattered all over. Either way you'd still need AllowUnsafeObjectPassing unless you use a form instead of a class.

There are no shenanigans, it's all one process but the XAML Framework does run in separate threads. In fact, when you instantiate the DesktopWindowXamlSource object it automatically calls the WindowsXamlManager.InitializeForCurrentThread method for you.

For example if you try to use a XAML object before initializing the XAML Framework on the current thread you get a runtime error 0x8001010E: "The application called an interface that was marshalled for a different thread". Try this before the call to Set m_DesktopWindowXamlSource = NewObject("DesktopWindowXamlSource"):

Code:

---

SolidColorBrushFactory.CreateInstanceWithColor 0

---

I just tried setting AllowUnsafeObjectPassing = False and it works just fine in this case. I guess I was overly cautious setting it to True by default, there are definitely situations when it doesn't work without it.

I have just completed a more in-depth analysis of this issue. The cOCR class in this project uses a total of five AsyncOperations and all of them are handled inline by the included cAwait class.

I have rewritten the cOCR class to completely eliminate using the cAwait class and handle all AsyncOperations via callbacks using a MachineStates solution (fancy name for what it does but this is the recommended "by the book" approach)! :bigyello:

Here's the MachineStates solution: Attachment 195800 (this project definitely needs the AllowUnsafeObjectPassing setting, it won't work without it)

Now comparing both solutions side-by-side I'd say the cAwait approach is definitely more elegant but there are pros and cons to each of them. What is your opinion vis-a-vis this conundrum?

In MachineState impl you can get away with this simple style of continuations only because you can distinguish complete handlers on their interface. The moment you have to implement two continuations on IAsyncOperationCompletedHandlerIBitmapDecoder for instance you have to implement logic depending on current state i.e. if the callback is reached/invoked on step 2 or on step 15 and so forth other complications.

Keeping these gory details to the compiler is the sane thing to expect so lambdas and capturing context is badly needed for these to feel seamless. Async/await baked into the language would help too.

cheers,
</wqw>

Well, there's not much chance of VB6 (or tB for that matter) getting any of these features any time soon so for the time being we have to get by with what we have. Not a very long time ago this machine states approach was the "de facto" standard when it came to async operations. It's true that the logic flow can get complicated in certain scenarios leading to the so called "callback hell", probably that's what prompted the invention of the Await syntax in .NET.

In the meantime VB6 keeps marching on, if callbacks are getting a little too hairy there's always the cAwait option to smooth things over, there's no reason you can't mix and match to your heart's content! :bigyello:

Just added a PDF Viewer project to the WinRT Samples Collection above. The user interface is created entirely as a XAML Island on an empty form, while the necessary plumbing is wired in code-behind. This serves as a great example of the features and flexibility of XAML code for creating a fluid and responsive UI in VB6.

Navigation is provided by a MenuBar at the top which includes a File menu for opening PDF files using the FileOpenPicker class, a Rotation menu to rotate pages at different angles and a Background color menu for setting various background colors for the PDF pages. The Background menu template is also stylized in XAML code to show color swatches as visual cues for the color names.

Since there is no concept of grouping menu items in arrays (as you would in the classic VB6 menu editor) and we don't want a separate click event for each menu item, a single XamlUICommand object is bound to each of them in XAML code with functionality provided by a single event in code-behind.

The main workhorse for displaying PDF pages is a ListView control with its DataTemplate edited in XAML code to contain a Border and Image controls for each item container. One of the main selling points of XAML controls is their ability to Bind one or more properties to various data sources providing the ultimate flexibility. Here the ListView's ItemsSource property is bound to a custom implementation of IBindableVector, while each container's Image control is bound to a BitmapSource object rendered on-the-fly.

The whole functionality is entirely asynchronous and event driven providing silky-smooth performance even when scrolling through hundreds of PDF pages all rendered in real time. Old pages are gradually destroyed while new ones are rendered when scrolling through the document.

Attachment 195822

The project starts by loading a sample PDF document from a URI (an Icelandic dictionary, random choice I found online but great for testing) so it may take a couple of seconds while this large file is buffered. After that you can open other PDF documents from the File menu.

Scrolling can be either fine-tuned with the mouse wheel or in bulk chunks by dragging the vertical scroll bar handle within large documents. There's also the possibility to Zoom In/Out with the Ctrl-MouseWheel shortcut. Zooming is focused on the current position of the mouse pointer. While the page is zoomed in, a horizontal scroll bar at the bottom allows for horizontal scrolling.

The code is heavily commented to help whoever wants to dip their toes in the XAML world. :bigyello:

Download this PDF Viewer project from the WinRT Samples Collection archive linked in the first post above (also requires re-downloading the TypeLib since it fixes a bug with a wrong method signature in the IContainerContentChangingEventArgs interface)!

@VanGoghGaming I took the liberty of using your WinRT Interfaces x86.tlb to write a MediaTranscoder (Windows.Media.Transcoding) for a user from another forum. He wants to convert an MP4 file with an H.264 video stream and AAC audio stream to an MP4 file with an H.264 video stream and MP3 (mpga) audio stream. The conversion works for me, but not for the user. He gets an error in mdlHelpers: InitNameSpaces: Automation error at the line Set m_RuntimeClasses = TempObject: ResolveNamespaces CreateObject("CLRMetaData.CorMetaDataDispenser.2"). You yourself wrote: "On the first call it also parses the system .winmd metadata files and builds a collection of activatable classes." My question is, therefore, does the user also need to install the Win11 SDK because of the winmd?


Otherwise: Very good work regarding the TLB and your examples. A few interfaces/classes from Windows.Media.MediaProperties are still missing, but these will surely be included in a future version of your TLB. :thumb:

That has already been fixed for a few days by now (when I posted the PDF sample above), download the module again (CreateObject was failing for that ProgId on some versions of Windows 11)! :thumb:

No worries, probably you are the only one using this TypeLib anyway, so go wild with it! It wouldn't have existed in the first place if it weren't for your WinRT mega project :D

What interfaces are missing from MediaProperties so I can add them? I can't find any omissions but my SDK files are from 3 years ago.

Hi. I've forwarded the request so the user can download mdlHelpers.bas again and replace it in my project. Let's see if that fixes the problem.


For example, the following classes/interfaces are missing from the Windows.Media.MediaProperties namespace: Av1ProfileIds, HevcProfileIds, and Vp9ProfileIds. These classes aren't important for my project. I just noticed that a few classes are missing.

He also needs to download the TypeLib again, it contains the MetaDataGetDispenser API declaration that was added.

Yeah, those ProfileIds classes are not present in my SDK, they were added in newer versions of Windows 11, guess I need to download a new SDK then.

Positive feedback. After replacing the TLB and the files from the "WinRT Samples Collection\Common", my example now works for the user. :thumb:

Here's a small demo showcasing the use of Composition in VB6. There's no XAML involved here, it can be used directly on a Form thus enhancing your current user interfaces with various visual elements all hardware accelerated and there are lots of cool things you can do with them. This is an example of a cube spinning on two of its axis while the scene contains a dim AmbientLight and a bright PointLight slightly above, shining on the cube.

Also if the classic CommandButton controls are too flat for your taste you can easily add a DropShadow to them and animate it on MouseDown/MouseUp to create a realistic Press/Release effect:

Attachment 195856

Download this Composition Demo project from the WinRT Samples Collection archive linked in the first post above (also requires re-downloading the TypeLib since it contains the new CompositorDesktopInterop interfaces that were added in the latest iteration)!

Hi
I can't run PDF Viewer project, because I get the error User-defined type not defined in m_PdfListView As IItemsControl

Pretty sure that's not the right error as IItemsControl is very much defined in the TypeLib (you can verify in the Object Browser (press F2)). You cannot run this project in the VB6 IDE unless you have the correct manifest as explained in post #6 above (read the instructions).

For a quick fix compile the EXE and run that to verify it works. Also open the Project->References menu in IDE and check nothing is missing there.

Great work VanGogh.
All examples work perfectly in windows 11.

Quote:

---

Originally Posted by Nanni

Hi
I can't run PDF Viewer project, because I get the error User-defined type not defined in m_PdfListView As IItemsControl

---

Check the references, I had an old tlb that caused conflict.

greetings

Quote:

---

Originally Posted by yokesee

Great work VanGogh.
All examples work perfectly in windows 11.


Check the references, I had an old tlb that caused conflict.

greetings

---

Thanks, resolved.Wrong typelib references.

In Windows 11, right-clicking a file in Explorer brings up the "Share with..." or "Share" menu item in the context menu. This cannot be accessed via IContextMenu::InvokeCommand (Verb Windows.ModernShare) -> Error 0x80070578 (ERROR_INVALID_WINDOW_HANDLE). I'm now trying to access the dialog using your TLB via IDataTransferManager. Your TLB is missing the IDataTransferManagerInterop interface. I added it myself using a QueryInterface and then used DispCallFunc to call the functions. So far, so good, and I can display the dialog. Using IDataTransferManager::AddDataRequested adds a corresponding event where an IDataPackage needs to be populated. This is all covered in the Microsoft documentation. What I'm having trouble with is passing an IIterable_IStorageItem to IDataPackage.SetStorageItems or IDataPackage.SetStorageItemsReadOnly. I need a new and empty IVector_IStorageItem that implements IIterable_IStorageItem, to which I can then add files or folders. For example, using IStorageFolder2.TryGetItemAsync. My question is: How do I create a new and empty IVector_IStorageItem using your TLB?

If this isn't possible, I'll probably use IFolderLauncherOptions.ItemsToSelect to create a new and empty IVector_IStorageItem. :D

As it turns out, IDataTransferManagerInterop is a recent addition to the twinBASIC package but looks like I forgot to copy it to the VB6 TypeLib as well. This is the ShareUI twinBASIC project where I used this interface:

Attachment 195882

You cannot create an IVector of anything in VB6 or twinBASIC since WinRT does not have a built-in instantiation class for vectors like it has for maps so your best bet would be to find an already existing object that does it for you like FolderLauncherOptions in this case as you've aptly deduced yourself. Other language projections have built-in mechanisms for instantiating vectors (like New List<T> in C# or single_threaded_vector in C++) but in VB6 you'd have to go with the nuclear option of implementing it yourself in a BAS module.

Also please feel free to post your creations in this thread as well instead of exclusively on the German forum! ;)

Quote:

---

Originally Posted by VanGoghGaming

but in VB6 you'd have to go with the nuclear option of implementing it yourself in a BAS module.

---

Ah yes, I did the same thing in my large WinRT project for IVector_(H)String. I actually wanted to avoid that. It really needs something like an IList<T> as a helper function.

Usually you can find other objects that give you the vector you want. For example both ClipboardContentOptions.HistoryFormats and RemoteLauncherOptions.PreferredAppIds give you an IVector_HSTRING.

And for XAML Binding of control properties you can use a custom implementation of IBindableVector in a class like I did in the PDF Viewer example above.

I know. It's a bit cumbersome, but it's also the best way instead of creating an IVector_xxx in a .bas file.

Quote:

---

Originally Posted by -Franky-

My question is: How do I create a new and empty IVector_IStorageItem using your TLB?

---

Since IDataPackage.SetStorageItems wants only an IIterable_IStorageItem parameter and does not require a full IVector_IStorageItem implementation then the problem is simplified a lot and we can implement these IIterable interfaces in a regular cStorageItems class using a vanilla Collection object as backing storage for the vector's elements:

Code:

---

Class cStorageItems

Implements IIterable_IStorageItem, IIterator_IStorageItem

Private BackingStorage As Collection, m_CurrentIndex As Long

Friend Function This(vFiles As Variant) As IIterable_IStorageItem
Dim vFile As Variant
    Set This = Me: If Not IsArray(vFiles) Then vFiles = Array(vFiles)
    With New cAwait
        For Each vFile In vFiles
            If .Await(StorageFileStatics.GetFileFromPathAsync(StrRef(vFile))) = AsyncStatus_Completed Then BackingStorage.Add .GetResults(Of IStorageFile)
        Next vFile
    End With
End Function

Private Function IIterable_IStorageItem_First() As IIterator_IStorageItem
    m_CurrentIndex = 0: Set IIterable_IStorageItem_First = Me
    Debug.Print "IIterable_IStorageItem_First"
End Function

Private Property Get IIterator_IStorageItem_Current() As IStorageItem
    Set IIterator_IStorageItem_Current = BackingStorage(m_CurrentIndex + 1)
    Debug.Print "IIterator_IStorageItem_Current"
End Property

Private Property Get IIterator_IStorageItem_HasCurrent() As BooleanByte
    IIterator_IStorageItem_HasCurrent = Abs(m_CurrentIndex <= BackingStorage.Count - 1)
    Debug.Print "IIterator_IStorageItem_HasCurrent"
End Property

Private Function IIterator_IStorageItem_MoveNext() As BooleanByte
    m_CurrentIndex = m_CurrentIndex + 1: IIterator_IStorageItem_MoveNext = IIterator_IStorageItem_HasCurrent
    Debug.Print "IIterator_IStorageItem_MoveNext"
End Function

Private Function IIterator_IStorageItem_GetMany(ByVal Length As Long, ByVal Items As LongPtr) As Long
    ' Not Implemented
End Function

Private Sub Class_Initialize()
    Set BackingStorage = New Collection
End Sub

End Class

---

As you can see the implementation is a lot simpler because these interfaces are already declared and we don't need a BAS module anymore. However we still need memory allocation for the IIterable_IStorageItem elements, hence the need for a Collection.

Here's the updated Attachment 195880 project showcasing this new approach.

I'd still go with the previous FolderLauncherOptions method of obtaining a full-fledged vector implementation as it's still a lot easier and probably performs better than a Collection (although not by much).

Quote:

---

Originally Posted by VanGoghGaming

I'd still go with the previous FolderLauncherOptions method of obtaining a full-fledged vector implementation as it's still a lot easier and probably performs better than a Collection (although not by much).

---

I also believe that's the best way. I partly did it that way in my large WinRT project as well.

Quote:

---

Originally Posted by VanGoghGaming

Also please feel free to post your creations in this thread as well instead of exclusively on the German forum! ;)

---

Since the question about how to access this ShareUI dialog was asked in a German forum, I'm naturally posting my example there as well. However, I'm not using your TLB in this example. Yes, I know it would be clearer and simpler with TLB. I hope you can forgive me. :rolleyes:

I wasn't talking about the ShareUI dialog, you couldn't have posted that since the IDataTransferManagerInterop interface wasn't included in the TypeLib at the time. You could have posted your video conversion example though, that could have been interesting for many other users.

Anyway, I have now updated the TypeLib with this missing interface and added the ShareUI sample to the collection linked in the first post above.

This update also includes the FolderWatcher project that demonstrates how you can monitor a folder for file changes and receive events when such changes occur.

Monitored changes include:

• file created (or copied into the folder)
• file deleted
• file renamed (reported as creation + deletion)
• file size changed (like editing a text file)
• file date changed (usually happens during editing as well)
• file attributes changed

The code for this video converter was written for a specific problem and can be found here: https://www.vb-paradise.de/index.php...esen/?pageNo=3 <- Last post on this page. On page 4, I'll show a few more small changes to the code.

Quote:

---

Originally Posted by VanGoghGaming

This update also includes the FolderWatcher project that demonstrates how you can monitor a folder for file changes and receive events when such changes occur.[/LIST]

---

Error when try to run in cFileQuery.cls:

Code:

---

Set StorageFolderStatics.GetFolderFromPathAsync(StrRef(sWatchedFolder)).Completed = Me

---

Open another project from the samples collection (like the GIF Player for example) and copy the 3 lines of code with the registry key check from Form_Load, looks like I forgot to add them in the FolderWatch project! :D

Quote:

---

Originally Posted by VanGoghGaming

copy the 3 lines of code with the registry key

---

Runtime error13 Type mismatch in line

Code:

---

If RegValStr(HKEY_CURRENT_USER, "SOFTWARE\Microsoft\Visual Basic\6.0", "AllowUnsafeObjectPassing") <> APITRUE Then

---

A little help maybe, what exactly is causing type mismatch for you, that line of code is very straightforward and it works just fine for everyone else...

@VanGoghGaming: I believe the error occurs when the setting for how errors are handled is configured under "General" in the IDE options. You are comparing a string with WinRT.BOOL.APITRUE here, which triggers the error. CStr(APITRUE) resolves the issue when reading and writing the value..

Quote:

---

Originally Posted by VanGoghGaming

A little help maybe, what exactly is causing type mismatch for you, that line of code is very straightforward and it works just fine for everyone else...

---

APITRUE and HKEY_CURRENT_USER are not declare ... when i declare in a module every thing is ok

Code:

---

Public Const HKEY_CURRENT_USER As Long = &H80000001
Public Const APITRUE As String = "1"

---

Quote:

---

Originally Posted by -Franky-

@VanGoghGaming: I believe the error occurs when the setting for how errors are handled is configured under "General" in the IDE options. You are comparing a string with WinRT.BOOL.APITRUE here, which triggers the error. CStr(APITRUE) resolves the issue when reading and writing the value..

---

I can't reproduce it for any of the error trapping options in the General tab, probably because this isn't an error, the compiler is supposed to automatically coerce Long to String in this case. That's why I am at a loss for why this is happening in some cases.

Quote:

---

Originally Posted by cliv

APITRUE and HKEY_CURRENT_USER are not declare ... when i declare in a module every thing is ok

Code:

---

Public Const HKEY_CURRENT_USER As Long = &H80000001
Public Const APITRUE As String = "1"

---

---

Those values are definitely declared as Enums in the TypeLib, just right-click one and select Definition. Maybe you have an ancient version of the TypeLib that you need to overwrite with the latest one from the first post above.

One should not leave it to the compiler to correctly cast values during a comparison. In .NET, with "Option Strict On," a comparison between a string and for example an integer would immediately be flagged as an error in the code.

.NET is for the weak, that's why we keep on trucking in VB6! The compiler is perfectly capable to coerce value types as needed:

Code:

---

Debug.Print 1 = "1" ' Prints True

---

I am more interested why exactly it produced Type mismatch only for @cliv above. Maybe it's an issue with SP6 not being installed or more likely an outdated TypeLib, either way it should work correctly all the time.

That's right! Embrace language constraints, strive for brevity and dream about direct machine opcodes via Emit :-))

SP6 missing is possible but unlikely (everything will bomb out). I bet it's a case of having an old version of the typelib lying around registered in a temporary folder and now cannot untangle the registry mess.

cheers,
</wqw>

Quote:

---

Originally Posted by VanGoghGaming

I am more interested why exactly it produced Type mismatch only for @cliv above. Maybe it's an issue with SP6 not being installed or more likely an outdated TypeLib, either way it should work correctly all the time.

---

I am also encountering this error. SP6 and all other available updates for VB6 have been installed as well. Using CStr(APITRUE) resolved the error. I am also using your latest TLB.

One really shouldn't speak negatively about other programming languages. Everyone who programs in VB.NET pokes fun at VB6 those who program in C# poke fun at those who program in VB.NET, and so on. Ultimately, it doesn't matter which language you program in. Every programming language has its own advantages and disadvantages. For instance, I personally would have liked to have had "Option Strict On" available in VB6 right from the start.

It was a joke mate, just for laughs. Maybe you have some Add-Ins that cause this error, otherwise I really don't know what's happening. You were always able to compare strings with integers, it's a core feature.