Forums Home / ComponentOne / ActiveX Edition
Posted by: tnielsen.dk on 30 November 2023, 4:29 am EST
tnielsen.dk
Posted 30 November 2023, 4:29 am EST
Hi,
For some reason I can’t get ToolTipText to work in VSFlexGid 8.0 (OLEDB/Unicode)
I’ve tried to follow https://helpcentral.componentone.com/docs/vsflexgrid8/tooltipdemo1.htm
I’ve tried the support, but no one seems to be there ;-(
The ToolTipText Property is not even showing!?!
Any inputs on why I have this problem?
BR, Thomas from Denmark
greg.lutz
Posted 11 December 2023, 7:55 am EST
Hello,
Did this work before and stopped working? It’s possible that some underlying Windows feature stopped working with a new update.
Also are you building a VB6 or MFC application?
Regards,
Greg
tnielsen.dk
Posted 11 December 2023, 9:33 pm EST - Updated 11 December 2023, 9:38 pm EST
Hi 
And thanks for finally responding.
The tooltip functionality has newer been used at my work, but now I need it in the flexgrid.
Your flexgrid is heavily used at my work. It’s used in 64 bit VBA in a legacy spreadsheet. I know VBA it isn’t officially supported, but everything else works.
I’ve tried to use it in Visual Studio (see image), but here the property isn’t showing either.
My next step will be to check if it works in VB6. Can you show me a working VB6.exe with a working flexgrid with tooltips?
In the manual from 2006 the following is mentioned:
“The samples on the distribution CD include other useful classes, such as CToolTip, and a file named
AtlControls.h that is part of a Visual Studio sample and defines ATL wrapper classes for all Windows
common controls.”
tnielsen.dk
Posted 12 December 2023, 6:23 am EST
Oh thought that this was finally an answer from support. But is from the forum
Thanks man!! - Sorry for writing your FlexGrid 
andrew.paxinos
Posted 15 December 2023, 9:39 am EST - Updated 15 December 2023, 9:44 am EST
Hello Thomas.
I did some testing and I was able to copy and paste the example code and it works just fine in a VB6 application.
Since VBA isn’t a supported environment, I don’t have any documentation or resources but based on some testing I did in ExcelVBA the .TooltipText property doesn’t seem to exist. There is a property in VBA called .ControlToolTip that seems to work correctly. Please try that and see if that works.
tnielsen.dk
Posted 18 December 2023, 12:48 am EST - Updated 18 December 2023, 12:53 am EST
Thank
Think I at some pint fiddled with ControlTipText. Only problem is that it seems, that you have to move the cursor outside the form to have the ControlTipText to refresh. And then is kind of hard to have text shown in the middle of the flexgrid.
If you have a Debug.Print "Row: " & nr & " Col: " & nc line you can see, that the cursor moving is detected, but the ControlTipText dosen’t change. Besides I guess it should be nr and nc that is used in the ControlTipText.
By the way the ControlTipText property isn’t mentioned in the 2006 manual.
BR, Thomas
andrew.paxinos
Posted 18 December 2023, 8:48 am EST
When you put an ActiveX control on a .NET form, it uses something called an Interop layer that Microsoft created that basically creates a little bubble of VB6 where the control lives on the form. Any code or interaction with the control basically has to be translated to something the control will understand and then translated back to the host program. We don’t control this Interop layer and that’s one of the reason we can’t support ActiveX controls in .NET. I know that some properties and methods are not longer accessible in this situation as well. .TooltipText is not accessible in a VB.NET project either.
I don’t know if VBA does a similar implementation as well. It’s possible that .ToolTipText is a default VBA property and the IDE can’t determine if you want to set the control specific property or the default VBA control property so it suppresses it so it can’t be used or cause confusion.
.ControlToolTip is not a property of vsFlexGrid, it’s something the IDE in VBA is creating so I’m assuming this is coming from whatever implementation of the Interop layer VBA uses. Unfortunately since VBA is not a supported environment for our ActiveX controls, I don’t have any documentation or samples that would help explain.
Our ActiveX controls are also in maintenance meaning they are no longer being updated so I do not have internal developer resource to even ask and we are discontinuing all ActiveX support Dec 31st 2023. I’m sorry but I don’t have any other options.
