|
-
Jun 16th, 2017, 10:53 AM
#1
Hyperactive Member
Re: CommonControls (Replacement of the MS common controls)
Thanks, that's what I thought. I have a VB6 version of the utility I posted a couple of days ago that allows a developer to switch from the OCX version to the Std-EXE version. I will post it in the next day or so. I hope you don't mind the add-on. I know this is your thread and if you would prefer I won't post it but it seems like the best place to keep it since it is specifically designed to work with what you've done.
-
Jun 16th, 2017, 01:16 PM
#2
Hyperactive Member
Re: CommonControls (Replacement of the MS common controls)
Krool,
One more question. The utility I am writing re-compiles the project after switching all of the references in the project from the OCX to the Std-Exe controls. The compilation occurs using the commandline compiler and does not use the IDE. Do I need to include the line "Call ComCtlsInitIDEStopProtection" since we aren't using the IDE? I am writing some code to find the .BAS file in the project that contains Sub Main but it gets to be a bit of a hassle knowing where exactly to drop in this line in that subroutine. It would be nice to not have to include it if we don't need it.
-
Jun 16th, 2017, 01:30 PM
#3
Re: CommonControls (Replacement of the MS common controls)
 Originally Posted by MountainMan
Krool,
One more question. The utility I am writing re-compiles the project after switching all of the references in the project from the OCX to the Std-Exe controls. The compilation occurs using the commandline compiler and does not use the IDE. Do I need to include the line "Call ComCtlsInitIDEStopProtection" since we aren't using the IDE? I am writing some code to find the .BAS file in the project that contains Sub Main but it gets to be a bit of a hassle knowing where exactly to drop in this line in that subroutine. It would be nice to not have to include it if we don't need it.
The Sub ComCtlsInitIDEStopProtection does only have an effect when running in IDE. In that Sub is a InIDE() test and does nothing when False.
So when you debug with OCX and compile with Std-EXE you certainly do not need to call that sub.
Means: ignore it completly.
And: Yes, please share that utility you are working right now.
-
Jun 18th, 2017, 09:32 AM
#4
Addicted Member
Handling EM_LINESCROLL
Hi Krool,
I have your TextboxW as Text1. When I call...
xx = SendMessage(Text1.hWnd, EM_LINESCROLL, 0, 1)
The textbox scrolls to the end, not just one line!
I stepped through your code and there was no handling for EM_LINESCROLL.
It is some time since I updated so this may have been added. If it has, please let me know. If not, is there any chance of a patch to add to handle it?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|