Printable View
Hello Mojtaba.
Not currently possible. I realize that there are some orientations that are possible but not available now:
TopRight
BottomRight
LeftBottom
RightBottom
The motivation to do that... it usually have been for fun. Not sure when or if I ever will add those tab orientations.
Thanks Eduardo, I'm adding this feature with the help of artificial intelligence.Quote:
Originally Posted by Eduardo-
I don't want to change your source. Would you give me permission for personal use?
You can change the source all that you wish, it is open source with MIT license.Quote:
Originally Posted by Mojtaba
If AI bots can do that already... feel free if you want to post the source code here.
Thank you very muchQuote:
Originally Posted by Eduardo-
Update released.Quote:
Originally Posted by Eduardo-
I added these orientations:
Code:ntTabOrientationTopRight = 6
ntTabOrientationBottomRight = 7
ntTabOrientationLeftTop = 8
ntTabOrientationRightBottom = 9
ntTabOrientationLeftTopHorizontal = 10
ntTabOrientationRightBottomHorizontal = 11
Thank you very much for your timeQuote:
Originally Posted by Eduardo-
Excellent
Hello
I'm using your great component ocx, but in some clients it gets the error "Automation Error". How can i fix it?
Hello, I never experienced that error with this control and it does not use any automation.Quote:
Originally Posted by visualorc
Why do you think it is this control that is causing that error? I would guess it is something else that is causing the error, not this control.
In what situation do the users get the error? What code is involved in that moment?
Hello
Those clients get the error when loading the application.
Attachment 194945
Attachment 194946
i've already unregister the ocx but the problem mantains
update: as the attach goes to invalinl link, those are the messages:
Run-time error -2147024770 (8007007e)
Automation error
The specified module could not be found
and the second message:
Run-time 440
automation error
As I said: it must be something else (most probably).Quote:
Originally Posted by visualorc
Please share a minimum sample project where I could reproduce the problem and see what happens.
Also: when the error occurs? What code is involved?
Hello,
is it possible that the "SxS" data is no longer correct?
I created the following new file using the MT.exe program.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<file name="newtab01.ocx" hashalg="SHA1">
<comClass clsid="{D9DACE39-8348-4FC3-8BBF-9178D817C34B}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" description="NewTab: tabbed control"/>
<comClass clsid="{F1589FE5-83AD-4CF4-83BA-BC3F9CA9D4DC}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{C151F8A1-BDE9-428D-AB1F-853885BD217F}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{14412CBC-CC08-42D7-AF44-80515C81FFF5}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{8CD7846C-8C2C-4454-846C-A9AFE36BC848}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{50096335-0F8C-4B25-ADF0-474C83D7E863}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{053857C3-2254-49A7-8470-E1E592AB936A}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<comClass clsid="{C93BEF1C-CC53-473E-A071-2B35D825643B}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" description=""Themes" are a set of property settings stored together."/>
<comClass clsid="{FA9E3E82-F40B-44FA-A6C1-A4A68ACECE15}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" description="Returns the colection of "Themes"."/>
<comClass clsid="{DB58ACE7-209E-4816-9DC3-32440EAE3651}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}"/>
<typelib tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" resourceid="1" version="14.0" helpdir=""/>
</file>
<comInterfaceExternalProxyStub name="_NewTab" iid="{54CA58AD-7E98-4EC9-9A92-F25D96FE19AF}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagNewTabGeneral" iid="{3199FF05-EFFD-41B0-9AC6-B210E1AC3637}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagNewTabTabs" iid="{0F7186D1-3B66-4C7D-8BE9-4EBE1895E08E}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagNewTabIcons" iid="{50814C37-2C7B-4551-A15C-E3F8CE9271B4}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagNewTabHelp" iid="{D8B20FF1-7383-4485-AD0E-9D3FA49D5BF0}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_IBSSubclass" iid="{5758E611-8AE7-4D47-ADF8-3E2803F06BC0}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagNewTabThemes" iid="{33480ECE-573E-46B8-B1C2-7816289A6977}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_NewTabTheme" iid="{D3FAEBAD-CA05-4EFD-A212-F7E00555512D}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_NewTabThemes" iid="{5005D5F6-7579-4D9C-B4CB-F6BDB2BA204C}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="_pagHighlightMode" iid="{6AB59FE6-AB95-4C55-BEA6-D4184A815605}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020424-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="__NewTab" iid="{A2914931-9333-409C-80A6-FB58B0DAB109}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020420-0000-0000-C000-000000000046}"/>
<comInterfaceExternalProxyStub name="__NewTabThemes" iid="{FA285BE3-6E45-4A6F-81AA-C1FE653F2F7D}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" proxyStubClsid32="{00020420-0000-0000-C000-000000000046}"/>
</assembly>
Yes, it was wrong (outdated).
Now it is fixed.
The correct information is:
Thanks for reporting.Code:<file name="NewTab01.ocx">
<typelib tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" version="14.0" flags="control" helpdir="" />
<comClass clsid="{D9DACE39-8348-4FC3-8BBF-9178D817C34B}" tlbid="{66E63055-5A66-4C79-9327-4BC077858695}" threadingModel="Apartment" progid="NewTabCtl.NewTab" miscStatusIcon="recomposeonresize,cantlinkinside,insideout,activatewhenvisible,alignable,simpleframe,setclientsitefirst" description="NewTab: tabbed control" />
</file>
I have not looked back at earlier posts so forgive me if this has been answered... This control seems to be available as a package in twinBasic - are the changes made in here also made in the twinBasic package version? I ask because I was just about to start using this control in my latest tB project.
Not for now. It has a version from the beginning of 2025 so it is not too outdated. But for now it is not updated with the VB6 version.Quote:
Originally Posted by AAraya
Here I asked Wayne about this subject (you need to have a Discord account to read it):
Wayne's answer:Quote:
Now when I fix bugs in the VB6 version, the tB version will be 'set on stone' until some update that I guess won't be frequent?
The changes I that made this year won't probably affect most users. They were:Quote:
I'll happily pass the package over to you for any future maintenance once we've got something more stable (and probably quite important to get the property pages support in)
1) Minor visual issues that appeared in some rare configurations: like having more than one row of tabs, with ShowRowsInPerspective set to True (emulation of SSTab) and setting flat themes. They were special situations where I corrected some line position or color. AAnd other things like that.
2) Improvements and also some bug fixes in TDIMode.
3) Added some methods that I needed, like ControlsGetTab (to get the collection of controls that are in a tab).
4) Changed some parameter, from numeric to variant, making available to select the tabs not only by its index by also by its key (keys can be defined for each tab in the Tabs property page or by code).
5) Added some tab orientations like TopRight, BottomRight...
You can see that it is unlikely than in a normal situation something of that will affect you. And you can see if you observe any problem or bug, and report it.
In conclusion: it will be updated in the future, unless someone reports something that needs to be addressed before.
Thanks Eduardo
If I open and maximize the form, the status bar ends up being positioned at the top, above newtabctl instead of at the bottom of the form (StatusBar has "Align = vbAlignBottom"). Why?
Hello. Post a sample.
Normal window with arrow pointing to statusbar:
https://drive.google.com/file/d/12WZ...ew?usp=sharing
Maximized window with arrow pointing to statusbar:
https://drive.google.com/file/d/1cW6...ew?usp=sharing
In the Form_Resize event I added the following line; no advantage:SB1 is StatusBar1Code:If SB1.Visible Then SB1.Align = vbAlignBottom
That's how Align works in VB6. The last control aligned goes after the previous control aligned to the same position (to bottom, to top, to left, whatever.Quote:
Originally Posted by fabel358
Align the Statusbar first, then the NewTab:
Code:Private Sub Form_Resize()
If SB1.Visible Then SB1.Align = vbAlignBottom
NewTab1.Align = vbAlignNone
NewTab1.Align = vbAlignBottom
End Sub
Really a great job, Eduardo!
Another question: I tried some settings and I can't restore the initial conditions :mad:. Is there a possibility of a reset?
I don't know what you mean by "settings", "initial conditions" and "reset".Quote:
Originally Posted by fabel358
Unless you are very, very specific about what you did, what you expected and what you got...
For initial conditions delete the control and add a new one.
Or close the project without saving and open it again.
Sometimes with controls that have many properties, and properties that we don't know what they do, we can get to a situation that we want to go back but don't know how.
Unfortunately VB6 does not provide a way to undo changes in properties.
Controls could keep track of the changes and offer a way to go back or to go forward, like a "history".
I never saw a control like that, but is possible.
The only thing I do when I get to that "state", is to close the project without saving. In case that you didn't do other important changes that need to be preserved... That's why I save the project frequently while it is in a good state.
I'll start by saying that "NewTab01.ocx" is a great job, however I found what I think is a "bug".
If I place a flexgrid with MsFlexGrid on NewTab, populate it with data and with the Flex_MouseMove subroutine, set a different tooltiptext for each cell and a Toolitip in the NewTab, it happens that in the IDE everything works as expected. If I compile the code, moving the mouse over the flexgrid, instead of the flexgrid tooltiptext appearing, the newtab tooltiptext continues to appear.
I add the code; to make it work open a new form, place NewTab1 on it and inside this MsFlexGrid with the name Flex and verify.
In a Form:
Code:Option Explicit
Private Sub Flex_MouseMove(Button As Integer, Shift As Integer, x As Single, y _
As Single)
Dim lRow As Integer
Dim lCol As Integer
Dim Tip As String
With Flex
lRow = .MouseRow
lCol = .MouseCol
Tip = .TextMatrix(lRow, lCol)
If LenB(Tip) Then
.ToolTipText = Tip
End If
End With
End Sub
Private Sub Form_Load()
Dim x As Integer
Dim y As Integer
With Flex
For y = 1 To .Cols - 1
For x = 1 To .Rows - 1
.TextMatrix(x, y) = CStr(x) & " - " & CStr(y)
Next x
Next y
End With
NewTab1.ToolTipText = "This is NewTAB01"
End Sub
It seems there is a bug in the MSFlexGrid. It also happens with a bare UserControl. But with the UserControl of the same project it also happens in the IDE.
On other hand, a PictureBox works fine.
Attached is the test project.
Anyway, why do you want to put a ToolTipText for the whole NewTab control? Perhaps you rather woud like to put tooltip text to the individual tabs. For that use the TabToolTipText property.
However, with TabCtl32.ocx, this problem does not happen, regardless of whether tooltiptext or TabToolTipText is used in NewTab01.ocxQuote:
Originally Posted by Eduardo-
Yes, it seems to be a problem of VB6's UserControl (in what is based the NewTab) with MSFlexGrid or maybe with any third party control (that would require to check and see).Quote:
Originally Posted by fabel358
Anyway, I don't see any usefulness in setting the ToolTipText property in the NewTab control. That property is automatically added by VB, I didn't add the feature myself. I think it makes no sense for this kind of control.
What I did add, is the TabToolTipText property.
The SSTab did not have the TabToolTipText property.Quote:
Originally Posted by fabel358
In summary: I don't think there is much I can do since it is a VB6 bug. On the other hand, I don't think it is a real issue, because I don't see a real life case when setting the ToolTipText on a NewTab control would make much sense.
What were you trying to do?
We don't quite understand each other. What I was interested in was not so much having the ToolTipText property for the "TAB"; I was interested in being able to have ToolTipText working in the flexgrid (as I showed in the example); adding msFlexGrid to NewTab - whether or not it has "ToolTipText" set, does not make the ToolTipText of the msFlexGrid appear - or rather: it works in the IDE but not in the compiled program. I repeat that the problem, with TabCtl32.ocx (which is less performant and less beautiful than NewTab01.ocx) does not happen; to verify what I write it is sufficient to change NewTab01.ocx with TabCtl32.ocx and exactly what I am describing happens. So I do not believe it is a bug of VB6.
Fortunately, these kind of things are much easier than believing or not believing. We can test them:Quote:
Originally Posted by fabel358
And when I say VB6, it is because NewTab is made in Vb6. Yes, it is a bug in NewTab, but one I'm not able to fix because it is a VB6 bug.
I don't have any control regarding how Vb6 handles the tool tips.
So, the only solution I see is to use another tool tip system.
Well, there is another solution. Use the VBFlexGrid. I just tested and the problem seems to be with MSFleGrid, MSHFlexGrid, and maybe all third party non-VB6 generated OCX, or at least MS-ones, but not with third party controls created with VB6.
It does not happen with intrinsic controls either (such as TextBox, PictureBox, etc.)
The VBFlexGrid is a MSFlexGrid replacement created by Krool and with many advantages (for example supporting Unicode and many other improvements).
Now I understand what you meant when you explained that it is a bug of VB6. I can't use VBFlexGrid because I had to implement functions in msFlexGrid, which Krool's VBFlexgrid doesn't have (I had already asked Krool about this months ago); I mean I don't want to get bogged down in re-adapting and rewriting a lot of the code. So I'm staying with TabCtl32.ocx, even if your control is much better.
Many thanks.
I tested a workaround and it worked: just place the MSFlexGrid inside a PictureBox:Quote:
Originally Posted by fabel358
PS: I'm curious, what is the feature that the VBFlexGrid lacks and MSFlexGrid has?
Neither Grid has the function I wanted, so I created it for MsFlexGrid because I didn't want to get bogged down in adapting the code for VBFlexGrid. I needed a function that would allow me to have text in different styles and even different colors within the same cell. I achieved this through the use of pictureboxes with relative manipulation of row heights.Attachment 195109
Here's the effect I wanted; I've removed some of the names for privacy but there's enough visibility to see what I mean.
Attachment 195110
P.S. If you don't see it, I'll provide the Google Drive links
I also verified what you wrote: I introduced the FlexGrid in a PictureBox and now the custom ToolTipText actually works. Congratulations!
Ah, OK, then the MSFlexGrid didn't support what you wanted either. But I mean, why the same code (the same workaround) that you used with MSFlexgrid could not be used with VBFlexGrid?Quote:
Originally Posted by fabel358
:thumb::thumb:Quote:
Originally Posted by fabel358
I already gave the answer.
My project is finished. It has 21 tabs, with 5 flexgrids per tab, plus more in other forms; just replacing TabCtl32.ocx with your NewTab01.ocx, despite the ease of replacing one ocx with the other, gave me the nasty surprise of the impossibility of custom tooltiptexts in the grid (at least there was a FAQ that would have warned me of the problem - but I think you didn't even know about this defect); not to mention the different sizes of the various themes, hence the use of the most generic theme (i.e. sstab).
Imagine replacing more than 100 flexgrids on an already finished project: any difference in the management of anything, would cost me hours and hours to re-adapt all the code.
No thanks!
I'm not saying that you should do it, but just for the record, you could replace the MSFlexGrid with The VBFlexGrid quite easily.
1) Make a backup copy of the whole project (just in case that things go wrong, to be able to go back).
2) Get some tool to make text replacements on multiple files. I use TexRep.
3) Register VBFlexGrid v18.
4) Replace in the vbp file
withCode:Object={5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0; MSFLXGRD.OCX
5) Replace in the frm filesCode:Object={075212A8-C1CF-444E-939D-F6046CCDBC08}#1.0#0; VBFLXGRD18.ocx
withCode:Object = "{5E9E78A0-531B-11CF-91F6-C2863C385E30}#1.0#0"; "MSFLXGRD.OCX"
andCode:Object = "{075212A8-C1CF-444E-939D-F6046CCDBC08}#1.0#0"; "VBFLXGRD18.ocx"
withCode:MSFlexGridLib.MSFlexGrid
And... if everything goes right, the project should open now using all VBFlexGrids instead of MSFlexGrids.Code:VBFLXGRD18.VBFlexGrid
And if not... delete and put the backup back.
5 minutes.
OK, 10 minutes for being the first time.
We don't understand each other.
My project has many "forms" and more than 31 thousand lines of code; "texrep" does not allow to select specific extensions, such as .vbp or .frm; even replacing the files with *.*, in several files the MsFlexGrid control remained, despite "TexRep" having indicated the replacement.
I would have liked to trust your advice, but your suggestion is valid for maybe a few hundred lines of code and half a dozen controls.
Or I should have started my application already with the NewTab01.ocx and VBFLXGRD18.ocx controls perfectly working and not "work in progress", building all the architecture around them.
Thanks for your patience and do not feel offended if I do not follow your suggestions.
Yes, it does.Quote:
Originally Posted by fabel358
You can replace any number of controls in any number of forms at once (in less than 1 second).Quote:
Originally Posted by fabel358
No, of course. As I said "just for the record".Quote:
Originally Posted by fabel358
Sorry Eduardo. I don't understand how to remove the "New Custom X" themes. May you explain it me?
Attachment 195206
Select the custom theme and you need to untick these three checkboxes and then click the OK button in the property page.
BTW, I've made an update, I fixed something regarding the file name for the themes.
Hello Eduardo, I hope you are well.
I always download the latest version from GitHub.
This version has a problem with the right-to-left tab order.
If you select the right-to-left characteristic
error :
RightToLeft is only available for Top orientation.
When I set the Tab Orientation section
Attachment 195365
Tabs should start from the right and the X symbol
Previous versions did not have this problem. I will send a picture of the old version.
Attachment 195366
And notice another problem: when we're in the home tab, the corners of the controls are perfectly rounded
but when I switch to another tab, they lose their shape and beauty.
Also, the number of tabs increases, which messes up the layout and appearance.
This problem is the same in both left-to-right and right-to-left tab directions. If you have a lot of tabs open, it will look messy.
Attachment 195368
I don't know if the theme settings have changed in the new version!
And the right-to-left problem has also appeared.
In the default theme, there is a white frame around the tank, which is really ugly.
Use colored backgrounds for better visibility. It is not as visible on a white background.
Attachment 195370
Sample project :
Hello Mojtaba. I'll check it (maybe tomorrow) and come back ASAP.
I'm ready to test it again.Quote:
Originally Posted by Eduardo-
OK, I'm working on it.Quote:
Originally Posted by Mojtaba
Fixing one issue I found many other related to right-aligned tab orientation that was the last feature I added.
I have to study the other issues.
What DPI setting did you have when you took those screen shots? (the Windows screen scale).
I only take screenshots of the form. Not the whole page.Quote:
Originally Posted by Eduardo-
If you want more details
Windows 10
Resolution: 1600 * 900
If you want me to take a video ?
No, no. Thanks.Quote:
Originally Posted by Mojtaba
OK, as mentioned in the previous post I fixed several issues mostly related when the tabs are right-aligned.
But when I'm testing and changing properties I find some other issues, just for example: for client area, the top have to consider the FlatBodySeparationLineHeight to start the client area (the ClientTop for top aligned TabOrientations). It is not taking that into accout now. It is just an example.
For the TDI Forms mode I'll have to make a Region for the PictureBox containing the forms, so the rounded corners show well.
For the issue that RightToLeft is not supported for bottom TabOrientations, it is because I handle the bottom orientation in a special way. But I have an idea to fix that, that will involve changing how the bottom orientations are handled.
These things I guess they could take a couple of more days.
But... I'm thinking in changing how the TDI Mode Forms handle icons. Because it actually shows two icons, one is the X to close the tabs and I added another icon for the forms icons.
I'm thinking in completely change that, making a Closable property that could be used for all the tabs, not just the TDI mode, not using the normal icon for the X. And then for the TDI mode use that feature, not having a custom icon anymore but using the normal icons.
That is a big change, and could take more time.
I'm currently busy working in a program that I have to finish I hope in a couple of months.
So... I can't spend so many days now on this control. It is fun for me, I enjoy working on this control, but maybe I'll have to do it in free time or when I'm tired of working in the other program. Then it could take longer.
Also the TDI MOde is limited to Top and Bottom orientations, but why? If everything is fine and when structured it should also work in any TabOrientation (we'll see, I don't remember now what what the problem with that that lead me to put that limitation)
So, if you need some fix soon, I could do just that now, but maybe what you need involves things that will take more time, like fully fixing RightToLeft.
I can share the OCX with the current fixes if you want, but I think I only fixed one of the several issues that you posted.
I'll keep working now a bit more I guess, but I won't be able to fix them all right now because I can't delay the other program's work a week or so that maybe all these fixes will take.
Eduardo, thank you for your time. I have a project where I use newtab a lot and the other parts of the program are not yet complete and I am not in a hurry to finish it. Please fix the control problems in your free time.Quote:
Originally Posted by Eduardo-
OK, fine. I'll report back when I have something to test.Quote:
Originally Posted by Mojtaba