[VB6] ucShellBrowse: A modern replacement for Drive/FileList w/ extensive features

[IliaPreston]

Thanks again for ucShellBrowse.
With ucShellBrowse 6.2.1, Pre-release with temp mitigations, most of the issues have been resolved.
However, a few small issues remain (The numbers below are new. They do not follow the list of issues specified in previous posts):

1. When I start my test vbp project, and (without clicking on any file thumbnail) press Alt+F (to invoke the "Select &File") commandbutton, it no longer causes the next keystroke (LeftArrow) to perform an unwanted navigation. The next keystroke (whether LeftArrow or any other arrow key) sets the focus to the first thumbnail (instead of an unwanted navigation). So that is good.

But, the Alt+F ITSELF (even before I press LeftArrow or any other arrow key) is supposed to set the focus to the thumbnail because there is this event function:

Private Sub cmdSelectFile_Click()
   ucShellBrowse1.SetFocusOnFiles
End Sub

When I press Alt+F, the thumbnail does NOT show a light blue rim. It shows absolutely no rim at all not even a gray one.
But, then when I press an arrow key, the thumbnail will show a light blue rim, and I can see that the thumbnail genuinely has focus (because then pressing Enter will execute the file, or alternatively, pressing other arrow keys will highlight adjacent thumbnails).
This is a very small issue, because when I press Alt+F and it does not set the focus to the thumbnail, I can simply press an arrow key to achieve that, but still Alt+F itself is supposed to do this and it doesn't.

2. The other commandbutton called "&Process Selected File" has this code associated with it:

Private Sub cmdFileProcess_Click()
   Dim Main_File_Path       As String
   
   Main_File_Path = ucShellBrowse1.BrowserPath & "\" & ucShellBrowse1.SelectedFile
  'CreateObject("Shell.Application").ShellExecute Main_File_Path, , , "open", SW_SHOWNORMAL
  'MsgBox "Selected item not found:  " & ucShellBrowse1.SelectedFile, vbOKOnly, "Process"

   ucShellBrowse1.SetFocusOnFiles
End Sub

Please note that two lines in there are commented out.
Here is how to recreate the problem:

Step 1: Uncomment only the MsgBox. Then run the application. Select a video file (for example by clicking on it). Press Alt+P in order to invoke the above code. The messagebox appears. close the messagebox.
Result: The application sets focus to the thumbnail that you had initially selected. This is good and expected behavior.

Step 2: Comment the Msgbox again, and instead, uncomment the CreateObject line. Then run the application. Select a video file (for example by clicking on it). Press Alt+P in order to invoke the above code. The video plays in its default video player. Close the video player.
Result: The application does NOT set focus to the thumbnail that you had initially selected. This is the problem.

3. When I set the following constant to False:

Private Const dbg_PrintToImmediate As Boolean = False

most of the debug info (almost 100% of it) will be suppressed.
But still the following two lines are printed when the application starts:

-->UC_INIT_OUT
-->PvCreate

And the exact same two lines are printed when the application terminates (so, 4 lines in total).

4. I have a feeling (not 100% sure though, just a feeling) that there could be some memory leak and/or unhandled window problem (Invalid window handle) in ucShellBrowse.
I experienced them earlier and reported both of them in this thread (post# 46). (in that post: problems 1 and 2)
I haven't encountered them recently (except just once), but, it is also worth mentioning that recently, I haven't tested ucShellBrows as much as I had tested it earlier.

Something caught my attention though:
In another unrelated thread (http://www.vbforums.com/showthread.p...n-a-Picturebox)
In post#19 of that thread you said something:

Did you change the picturebox's AutoRedraw property to True? Probably want to change ScaleMode to vbPixel as well. These are on the design-time Properties box like where the Name is.

And also see the SetPreviewPictureWithHBITMAP function that's setting it in my code?

picturebox.Cls
hBitmapToPictureBox picturebox, hBmp
picturebox.Refresh

(Don't forget the DeleteObject call when you're done with the hbitmap as well.)

And cx and cy are width/height. You definitely don't want a 0x0 image. Gotta change that picturebox scalemode to vbPixels if you're using picturebox.width/height as the size too, or you'll get a giant image.

I have a feeling that this could have something to do with the memory leak or the unhandled window problem (Invalid window handle).
I don't have very strong proof for that. It is just a hunch.
But, it is probably worth investigating.

Thanks.
Ilia