-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
DEXWERX
Are you able to download the controls from the first post? All the controls are downloadable at the bottom the first post.
The "Demo" includes all the code.
You only need to PM Krool if you want the distributable OCX.
Yes, I wasn't aware that it is the source code of the project. Thank you.
-
Re: CommonControls (Replacement of the MS common controls)
Major update released.
The right-to-left properties are now implemented, beside some minor and one critical bugfix.
All controls (except ImageList, IPAddress, MCIWnd, HotKey and SysInfo control) includes now a RightToLeft and RightToLeftMode property.
Some controls includes in addition a RightToLeftLayout property.
The effect is different on each control.
But in general the RightToLeft property enables bi-directional reading and the RightToLeftLayout property turns on mirror placement.
If RightToLeftLayout is enabled, it is only active when also the RightToLeft property is enabled. (Like in .net)
The RightToLeftMode property controls of how the RightToLeft property should be checked.
It can be set to following:
- NoControl
- VBAME
- SystemLocale
- UserLocale
- OSLanguage
VBAME means the check will be done by VB itself. (effectively by VBAME.DLL)
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
milan.opa
Me too ! I've just registered to this forum to be able to send the PM, but that option is not listed when clicking on "Krool". I have only "View profile" and "View forum posts" available.
Can it be that the account is too "fresh" ?
Edited: After few hours (or posting this message), the option suddenly appeared. So I guess, you just have to be patient :)
Glad I'm not the only one! I've been trying for the last week to figure out why I had no option to sen a PM either.
For any other newbies to the forum, I'm assuming you must post first before you get the PM option. (Hence this post :)).
This set of controls are awesome and have renewed my zeal to keep using VB6 for development.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
Major update released.
The right-to-left properties are now implemented, beside some minor and one critical bugfix.
I'm not very interested in RTL, but would like to know what the bugfixes are...
Karl
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
dudley
Glad I'm not the only one! I've been trying for the last week to figure out why I had no option to sen a PM either.
For any other newbies to the forum, I'm assuming you must post first before you get the PM option. (Hence this post :)).
This set of controls are awesome and have renewed my zeal to keep using VB6 for development.
With new control, like Lavolpe (Alpha Image) wich allow us to use PNG in vb6 and This new set of control, I too intend to keep develloping in Vb6. I think I will post my "Microsoft Access" Library soon. It is a Wrapper around ADO wich simplify Database related activity. Maybe if Krool want to join me, I'll build a web site just for this purpose :)
interested Krool ?
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
VbNetMatrix
With new control, like Lavolpe (Alpha Image) wich allow us to use PNG in vb6 and This new set of control, I too intend to keep develloping in Vb6. I think I will post my "Microsoft Access" Library soon. It is a Wrapper around ADO wich simplify Database related activity. Maybe if Krool want to join me, I'll build a web site just for this purpose :)
interested Krool ?
ADO is so simple, I just haven't seen a need for another abstraction.
The only VB6 ORM I know of is here --> http://www.hisystems.com.au/databaseobjects/
@Karl77 from the first post.
Quote:
Originally Posted by KROOL
28-Sep-2016
- Fixed a critical bug in the 'Bands' property page in the CoolBar control that was caused by update on 07-Jul-2016.
- Included the RightToLeft and RightToLeftMode property on supported controls.
- Included the RightToLeftLayout property on some controls. (where mirror placement is applicable)
- Included the RightToLeftMirror property in the ImageList control.
If enabled, an list image is drawn mirrored on a right-to-left device context (WS_EX_LAYOUTRTL) to preserve directional-sensitivity.
- Some internal improvements to ensure right-to-left support. (e.g. use of MapWindowPoints instead of the ScreenToClient)
- Bugfix in the TextBoxW control that the horizontal scrollbar could disappear on certain conditions.
- Removed the Orientation property in the SpinBox control.
- The internal tooltip in the ListView control respects now changes in the VisualStyles property.
- Renamed the CalendarRightAligned property to 'CalendarAlignment' in the DTPicker control.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
DEXWERX
Simple.... yes I guess it is. But are you using ADO with embeded control ? or manual ?
Because with manual utilisation, there is so much you need to take care of.
My control for example will tell you if you forgot to close a table of a database on leaving and you can therefore fix your code before it go into production.
Also, my control doesn't allow you to "try" to send the wrong data type into a field, it check it before trying to write into the Db. it also Autoload all table and field into memory before you even open a table, allowing you to know exactly the database composition. I also can open any Access Database without the password. (sorry if MS screwed the security on that one) I did that component because it is almost impossible to make a mistake that will crash your program with it. it got error handle all over. It support up to Access 2010 format (2013 is 2010 format)
-
Re: CommonControls (Replacement of the MS common controls)
Update released.
Now ListSubItems can display a ToolTipText. Also the ShowLabelTips property works as expected.
Problem with the ShowLabelTips property was that LVS_EX_LABELTIP should be the style bit which indicates if partially hidden labels lacks tool tip text, the ListView will unfold the label.
However, even if the LVS_EX_LABELTIP style bit is removed, the ListView insists on displaying the label tip. Therefore it must be an MS bug.
To solve this it was necessary to check for LVS_EX_LABELTIP on TTN_GETDISPINFO and TTN_SHOW in the ListView and on LVN_GETINFOTIP in the UserControl.
Also then it was possible to enable ToolTipText support for ListSubItems.
-
Re: CommonControls (Replacement of the MS common controls)
Why compressed files can not be extracted it?
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
ChenLin
Why compressed files can not be extracted it?
Download and use the current 7ZIP, then it works.
I also had problems because I used an older 7ZIP from 2015.
Karl
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
ChenLin
Why compressed files can not be extracted it?
Also ensure to remove the .zip extension from the .z01.zip file. (.z01.zip -> .z01)
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Karl77
Download and use the current 7ZIP, then it works.
I also had problems because I used an older 7ZIP from 2015.
Karl
Thank you, 7ZIP can be directly extracted, this is indeed very good, winzip can not be directly extracted.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
Also ensure to remove the .zip extension from the .z01.zip file. (.z01.zip -> .z01)
Thank you Krool, according to the operation you said the success of the Karl installation of 7ZIP is very good, very convenient.
-
Re: CommonControls (Replacement of the MS common controls)
Good afternoon,
I need the CommonControls control but I don't know how to contact Krool in private. I try to click on his user name (as suggested in a previous post) but I can see only "view profile" and "view forum posts".
Anyone can help, please?
Thank you,
Vittorio
-
Re: CommonControls (Replacement of the MS common controls)
All download links are in the 1st post, unless you need something specific.
-
Re: CommonControls (Replacement of the MS common controls)
Hi Arnoutdv,
Thank you for answering. I have tried to go to the first post. When I click to version 1.3 of the ocx I am redirected to another post where there is this message:
"Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference"
Thank you.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
vitweb
Hi Arnoutdv,
Thank you for answering. I have tried to go to the first post. When I click to version 1.3 of the ocx I am redirected to another post where there is this message:
"Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference"
Thank you.
At the very bottom of the first post is a Download for the Demo files. It contains the source to all the controls.
-
Re: CommonControls (Replacement of the MS common controls)
-
Re: CommonControls (Replacement of the MS common controls)
Hi Krool,
Something went wrong while sending you a private message asking for the OCX version. To avoid bloating your In-Box in case it was sent I'm asking it here, if possible.
Thank you
-
Re: CommonControls (Replacement of the MS common controls)
Need to get a copy of a VB6.exe.manifest to use updated comctl32.dll
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
GaryW
Need to get a copy of a VB6.exe.manifest to use updated comctl32.dll
http://www.vbforums.com/showthread.p...ues&highlight=
-
Re: CommonControls (Replacement of the MS common controls)
There is a problem with the CommonDialog.
For ShowSave, it doesn't return the entered filename + extension.
The original delivers the extension.
Code:
Dim CD As CommonDialog
Dim TheFile As String
'--------------------------------------------------
Set CD = New CommonDialog
With CD
.Flags = CdlOFNOverwritePrompt Or CdlOFNHideReadOnly Or CdlOFNExplorer
.Filter = "?INI files" & "(*.ini)|*.ini|" & "?All files" & " (*.*)|*.*|"
.DialogTitle = "?Export configuration"
.InitDir = GS.Inifolder
.ShowSave
TheFile = .FileName
End With
Set CD = Nothing
MsgBox TheFile
End Sub
Example:
In the dialog, I enter 'BLA'.
The original returns 'C:\SomePath\BLA.INI'.
The kroolish returns 'C:\SomePath\BLA'.
Do I miss something?
Karl
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Karl77
Do I miss something?
The DefaultExt property.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
GaryW
Need to get a copy of a VB6.exe.manifest to use updated comctl32.dll
Can you enlight me on this ?? wich updated comctl32.dll ??
I'm using v6.1.7601.18837, wich techniquely is the last that I know of. and I don't use manifest.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
Hi Krool, I looked at your post on this... I don't understand why you're using this. I'm on Win7x64 I don't have any problem with UAC (of course you need to set up your Shortcut link the proper way) What would be my gain to use Manifest ? I also tried to follow the method you described to see if any difference and Ressource Hacker refused to insert the res file. Did I miss something ?
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
The DefaultExt property.
Thanks.
I never had to use it, the original seems to make it automatic.
Also the other replacement I formerly used.
From what I see here, the 'lpstrDefExt' only must not be empty to achieve this.
It wouldn't hurt if your controls would do the same.
But not very important for sure.
I can send you the code of the other replacement if wanted.
Karl
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Karl77
It wouldn't hurt if your controls would do the same.
But not very important for sure.
I can send you the code of the other replacement if wanted.
I agree that behavior should be the same.
Please share the other replacement.
-
Re: CommonControls (Replacement of the MS common controls)
Update released.
Quote:
Originally Posted by
Karl77
From what I see here, the 'lpstrDefExt' only must not be empty to achieve this.
That was exactly the point. Thanks
I just needed to add the following code to get the expected behavior: (DefaultExt is an extra buffer)
Code:
If PropDefaultExt = vbNullString Then DefaultExt = vbNullChar Else DefaultExt = PropDefaultExt
.lpstrDefExt = StrPtr(DefaultExt)
Because when 'lpstrDefExt' is NULL (according to MSDN), no extension is appended at all.
Therefore in our case 'lpstrDefExt' should be never NULL, because we want an extension appended.
The DefaultExt property therefore only has effect when the Filter was *.*
The only scenario where no extension will be appended is when the selected filter was *.* and the DefaultExt is not set. (=vbNullChar)
-
Re: CommonControls (Replacement of the MS common controls)
This is spectacular work...wow, thank you. However, I'm having an issue with the RichTextBox playing nicely with the Find dialog control.
When I search for a word using the Find dialog box, it is not getting highlighted within the RichTextBox. However, I know it is finding it, because once I close the Find/Replace dialog box, the RichTextBox suddenly gets the focus and the proper "found" word becomes highlighted. What am I overlooking?
Also, is there a function that allows "Replace" as well or is it only restricted to the "FIND" property?
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
swambast
This is spectacular work...wow, thank you. However, I'm having an issue with the RichTextBox playing nicely with the Find dialog control.
When I search for a word using the Find dialog box, it is not getting highlighted within the RichTextBox. However, I know it is finding it, because once I close the Find/Replace dialog box, the RichTextBox suddenly gets the focus and the proper "found" word becomes highlighted. What am I overlooking?
Also, is there a function that allows "Replace" as well or is it only restricted to the "FIND" property?
Look at the Demo. There you find a working find dialog. For the replace is actually the same. Use the Find method and then set the SelText property to your replace text.
-
Re: CommonControls (Replacement of the MS common controls)
Krool, yes I tried to reproduce that and that is the exact code bank I was using from the demo, but still same issue. Part of resolution that helped was setting custom form to modeless but now there's still other errors on form load, and sometimes the RTB just grays out or won't load (not to mention all the other build dependencies as well). So honestly Krool, despite my excitement and absolute interest in this, this is beyond me and I've simply spent far too much time trying to get everything to work...feel like I'm putting together a jigsaw puzzle here constantly with missing pieces. :confused:
I'm going back to the standard controls now despite a few more .ocx and loss of visual themes - they just tend to work more straight forward and I have supporting code that covers the unicode issues anyway. I wanted to say thanks for your efforts on providing us with another option though! :cool:
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
swambast
Krool, yes I tried to reproduce that and that is the exact code bank I was using from the demo, but still same issue. Part of resolution that helped was setting custom form to modeless but now there's still other errors on form load, and sometimes the RTB just grays out or won't load (not to mention all the other build dependencies as well). So honestly Krool, despite my excitement and absolute interest in this, this is beyond me and I've simply spent far too much time trying to get everything to work...feel like I'm putting together a jigsaw puzzle here constantly with missing pieces. :confused:
I'm going back to the standard controls now despite a few more .ocx and loss of visual themes - they just tend to work more straight forward and I have supporting code that covers the unicode issues anyway. I wanted to say thanks for your efforts on providing us with another option though! :cool:
I bet your issues can be solved.
However, you might try the OCX version. (please pm me)
-
Re: CommonControls (Replacement of the MS common controls)
Hello Krool, I have downloaded and used "VBCCR13.OCX" as a replacement for "MSCOMCTL.OCX" on July 13th 2016. I had done this because of problems with that reference in my Access applications since August 2012. This problem occurred after a Windows Update from time to time. Generally, a workaround could be found in registering an older version, but lately this failed to work on certain PC's at a client site. The "VBCCR13.OCX" replacement worked fine for some time, but the client has now some new PC's that have problems with that replacement. The "MSCOMCTL.OCX" reference works fine for those PC's now. So this is confusing me of course.
I can't dowload new versions of "VBCCR13.OCX", I would need to send you a pm. I just registered as a new member but I can't send a private message so far.
Of course, would I solve my specific problem with a new version, or is this some recurring nasty registry problem that I'm suffering from?
Thanks in advance for your opinion.
-
Re: CommonControls (Replacement of the MS common controls)
Hello Krool,
how can I remove focus rect?
Thanks.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
lhartono
how can I remove focus rect?
Find and remove all kinds of WM_CHANGEUISTATE messages.
Code:
SendMessage hWnd, WM_CHANGEUISTATE, MakeDWord(UIS_CLEAR, UISF_HIDEFOCUS Or UISF_HIDEACCEL), ByVal 0&
Quote:
Originally Posted by
martin.matten
would I solve my specific problem with a new version, or is this some recurring nasty registry problem that I'm suffering from?
A new version would certainly change nothing in that regard. I think it is some registry problem on your PC.
-
Re: CommonControls (Replacement of the MS common controls)
OK Krool, thanks for your opinion.
In the meantime I have made 2 runtime versions for my application. So far, if the version MSCOMCTL doesn't work, the VBCCR13 does, or vice versa. Let's hope that this workaround will stand until we have a clear view on the registry problem behind...
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
martin.matten
OK Krool, thanks for your opinion.
In the meantime I have made 2 runtime versions for my application. So far, if the version MSCOMCTL doesn't work, the VBCCR13 does, or vice versa. Let's hope that this workaround will stand until we have a clear view on the registry problem behind...
If you use VBCCR13 with the side-by-side resource provided, you will never encounter any problem caused by registry in the user computer. Your application will always run no matter what problem there may be with the registry.
The only consideration is minimum WinXP SP2, which is no longer a problem today.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
chosk
If you use VBCCR13 with the side-by-side resource provided, you will never encounter any problem caused by registry in the user computer. Your application will always run no matter what problem there may be with the registry.
The only consideration is minimum WinXP SP2, which is no longer a problem today.
Thank you chosk. However, I have to admit that I have never used a side-by-side resource myself as an Access programmer. The projects are adp or mdb files. The exe file is "msaccess.exe" which opens the project file. From the project file I can add references, but those need to be registered by "regsvr32.exe" first. Could I use a side-by-side resource also? Thanks for your help anyway!
-
Re: CommonControls (Replacement of the MS common controls)
Sorry, I missed the part about Access. Probably won't work then.
-
Re: CommonControls (Replacement of the MS common controls)
@martin.martin:
Then you should create an installation package to distribute and install the VBCCR13 on client computers.
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Arnoutdv
@martin.martin:
Then you should create an installation package to distribute and install the VBCCR13 on client computers.
Thanks Arnout, however I must admit that I have never created an installation package so far either. I prefer to be honest even if this make me look behind reality ;-) I will go into further investigation whenever I run out of workarounds again.
-
Re: CommonControls (Replacement of the MS common controls)
Update released.
Fixed a bug in the Selected property of a Node in the TreeView control.
The issue was that a focused (but not selected) Node could not get the selected state by code.
That bug can be easily replicated by following code:
Code:
TreeView1.Nodes(1).Selected = Not TreeView1.Nodes(1).Selected
The code should toggle the selected state, but it was not working.
However, now it works. (like in the original MS control)
-
Re: CommonControls (Replacement of the MS common controls)
what is the latest version (build) of the OCX
-
Re: CommonControls (Replacement of the MS common controls)
Hi, i have project that already contain *.res file and it can't have more than one *.res file how i can implement this custom control without adding new res file from your project demo/example? because i realize that this control can't working fine without resources.res
-
Re: CommonControls (Replacement of the MS common controls)
Hello Krool, as many others have also said already, thanks for your outstanding work on this control library.
I may have found a slight difference in how VBCCR (still using 12) implements the CommonDialog.FilterIndex property as compared to Microsoft's. Our original code would specify a new value for .FilterIndex, then show the file open dialog, and then again read from .FilterIndex to see what file type the user selected.
Using VBCCR12, the .FilterIndex property does not get updated after the file selection. (It always returns back the same default which was set originally). However, reading MSDN ([1] and [2]) I'm not actually sure what it is supposed to do. It sounds like perhaps it is meant to be used ONLY for setting the default (not for reading the user's selection). But nonetheless the Microsoft version seemed to allow that and even if that was a bug on their part, it is now a difference in behavior.
I'm curious what your opinion of this issue is. Is there an approach for getting the selected filter (other than parsing the selected filename)?
Thanks again!
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
This is the 1.3 ActiveX Control version. (Revision 10)
Not available for the moment, due to forum policy. Please PM me to get it by another way.
I cannot pm you, could you send me the latest ocx please
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
DaveInCaz
I may have found a slight difference in how VBCCR (still using 12) implements the CommonDialog.FilterIndex property as compared to Microsoft's. Our original code would specify a new value for .FilterIndex, then show the file open dialog, and then again read from .FilterIndex to see what file type the user selected.
Using VBCCR12, the .FilterIndex property does not get updated after the file selection. (It always returns back the same default which was set originally). However, reading MSDN (
[1] and
[2]) I'm not actually sure what it is supposed to do. It sounds like perhaps it is meant to be used ONLY for setting the default (not for reading the user's selection). But nonetheless the Microsoft version seemed to allow that and even if that was a bug on their part, it is now a difference in behavior.
I'm curious what your opinion of this issue is. Is there an approach for getting the selected filter (other than parsing the selected filename)?
Update released.
Thanks
-
Re: CommonControls (Replacement of the MS common controls)
-
1 Attachment(s)
Re: CommonControls (Replacement of the MS common controls)
Update released.
Fixed a bug in the NoImage property of a Button in the ToolBar control.
It was not possible to set the NoImage property of a Button to True when no ImageList was set.
Beside that, I have noticed another "point":
When an ImageList is set for a ToolBar control and this is changed to Nothing then the spaces for the Images are removed.
However, a ToolBar that has already no ImageList will display these spaces for the Images even when setting again the ImageList property to Nothing.
Only setting a valid ImageList and then setting to Nothing will remove these "spaces". But the spaces will come again if the ToolBar gets re-created.
Attachment 142177
So, there are then three options, which I hope to get some opinions:
1. keep as described above. (same as MS ToolBar)
2. Never show spaces for the images when there is no ImageList set.
3. Always keep the spaces for the Images in all scenarios.
-
Re: CommonControls (Replacement of the MS common controls)
I am not sure where this fall into which of the three options.
When an imagelist is set for the toolbar and there are buttons with images and there are also buttons without images, then for those buttons that do not have images there be no space for the image.
Edit to add:
This to apply only when TextAlignment is set to 1-Right. When TextAlignment is 0-Bottom, then images are expected for all buttons.
-
Re: CommonControls (Replacement of the MS common controls)
When ImageList is set all buttons expect images, to exclude a button there is the NoImage property.
But whats for the case when no ImageList is set?
You say for TextAlignment 0-Bottom keep the spaces and for 1-Right remove the spaces, right?
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
When ImageList is set all buttons expect images, to exclude a button there is the NoImage property.
But whats for the case when no ImageList is set?
You say for TextAlignment 0-Bottom keep the spaces and for 1-Right remove the spaces, right?
Yes.
-
Re: CommonControls (Replacement of the MS common controls)
Krool,
I have run into an issue that results in VB crashing upon stopping my test app in debug or closing my test app.
I have narrowed it down to this:
If you place as ListView control and a Button control on a form the add this code to the button:
Private Sub CommandButtonW1_Click()
Dim loItem As LvwListItem
For Each loItem In ListView1.ListItems
loItem.Ghosted = False
Next
End Sub
When you close the form or click Stop in debug mode VB6 will crash.
I can workaround this code by doing this:
Private Sub CommandButtonW1_Click()
Dim loItem As LvwListItem
Dim i as integer
For i = 1 to ListView1.ListItems.Count
Set loItem = ListView1.ListItems(i)
loItem.Ghosted = False
Next
End Sub
As I am evaluating using your control, it seems the intent is to have your control replace the CommonControls.
I am just wondering if there was a known list of differences so that I can be sure to make adjustments in my code and avoid any issues?
Any help here would be appreciated.
Thank you
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
dtencer
Krool,
I have run into an issue that results in VB crashing upon stopping my test app in debug or closing my test app.
I have narrowed it down to this:
If you place as ListView control and a Button control on a form the add this code to the button:
Private Sub CommandButtonW1_Click()
Dim loItem As LvwListItem
For Each loItem In ListView1.ListItems
loItem.Ghosted = False
Next
End Sub
When you close the form or click Stop in debug mode VB6 will crash.
I can workaround this code by doing this:
Private Sub CommandButtonW1_Click()
Dim loItem As LvwListItem
Dim i as integer
For i = 1 to ListView1.ListItems.Count
Set loItem = ListView1.ListItems(i)
loItem.Ghosted = False
Next
End Sub
As I am evaluating using your control, it seems the intent is to have your control replace the CommonControls.
I am just wondering if there was a known list of differences so that I can be sure to make adjustments in my code and avoid any issues?
Any help here would be appreciated.
Thank you
Never noticed such thing. Can you make a demo? (Ensured the issue comes up)
Also do you use the Std-EXE or OCX version?
Beside that, pushing IDE stop button is not recommended, however closing form has to work..
-
1 Attachment(s)
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
Never noticed such thing. Can you make a demo? (Ensured the issue comes up)
Also do you use the Std-EXE or OCX version?
Beside that, pushing IDE stop button is not recommended, however closing form has to work..
I am using the .ocx.
Here is the behavior I am seeing: http://screencast.com/t/jx58rQBWI0C
I've attached a sample program:
Attachment 142237
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
dtencer
I have tested on WinXP and Win7 and it worked fine.. hmm.
Does this happen when sample program is compiled? Does it also happen when using the Std-EXE version?
Did you test on other controls? (e.g. TreeView)
Anyone else having this issue?
-
Re: CommonControls (Replacement of the MS common controls)
hi, Thanks Krool (again, I can't stop thanking you)
How often do you update the OCX? I see in the latest revision (10) some thing are not included (like RTL support)
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
I have tested on WinXP and Win7 and it worked fine.. hmm.
Does this happen when sample program is compiled? Does it also happen when using the Std-EXE version?
Did you test on other controls? (e.g. TreeView)
Anyone else having this issue?
It does not happen when compiled. But I have seen an issue like this before and if it does this in debug it will have a negative effect latter on the application. One example is if I compile to a .dll then call from another .exe it will throw an exception.
I have not tried the Sdt-EXE version.
It works fine with the TreeView control, it seems to be isolated to the ListView.
Thanks
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
dtencer
It does not happen when compiled. But I have seen an issue like this before and if it does this in debug it will have a negative effect latter on the application. One example is if I compile to a .dll then call from another .exe it will throw an exception.
I have not tried the Sdt-EXE version.
It works fine with the TreeView control, it seems to be isolated to the ListView.
Thanks
Ok, difference between TreeView and ListView is following.
TreeView uses native Collection enumeration. ListView uses custom enumeration. (Enumeration.cls)
Because ListView need to be enumerated in visible order and not order of the collection.
I think that some reference is not terminated, thats why the crash.
I await your try with the Std-EXE version. There we can get closer to the cause and find out a solution.
However, as already said, I can not replicate the issue and thus I am dependent on you. :-)
-
Re: CommonControls (Replacement of the MS common controls)
Quote:
Originally Posted by
Krool
Ok, difference between TreeView and ListView is following.
TreeView uses native Collection enumeration. ListView uses custom enumeration. (Enumeration.cls)
Because ListView need to be enumerated in visible order and not order of the collection.
I think that some reference is not terminated, thats why the crash.
I await your try with the Std-EXE version. There we can get closer to the cause and find out a solution.
However, as already said, I can not replicate the issue and thus I am dependent on you. :-)
Please direct me to instruction on how to test/use the Std-EXE version. I have only just discovered your .ocx.
Thank you