Hey Paul, you are so fast, awesome! Just in case you haven't noticed, when Google Chrome is maximized, the top borders of the tabs touch the top border of the screen, so one don't have to move his/her mouse pointer precisely on the Y axis. That's very convenient, IMHO.
Edwin Yip - I need to get back to paid work soon or the kids won't be eating next week :)
Yes, I've been looking at the way Chrome maxmises the form. I'm pretty close to finishing the new code. It works better than I imagined. I'll hopefully commit something later today.
Hey Paul Thornton , I checked out ChromeTabs yesterday and I'm amazed at the work you've done, they look great! I couldn't find a feature to tie them into the window title bar, so it's nice to see you're working on that. Are you planning to make a form that has to be subclassed rather than TForm? As I recall, that's how DevExpress did it for their ribbon forms.
I was also wondering, are you planning to add a page control aside from the tabs? I'm just curious because I've never actually worked with tabcontrols before, the only thing that comes to mind on how to use them, is making a borderless pagecontrol that is linked to the tabs through events.
I've just committed the update for the title bar tabs (along with quite a few fixes):
Update: Added TChromeTabsGlassForm - Allows Chrome title bar tabs with one line of code. Update: Added ContrainDraggedTabWithinContainer property. Update: Added title bar tabs functionality to Demo. Fixed: Floating Right Add button was position far right if only pinned tabs were displayed. Fixed: Drag tab image not scaled down or alpha blended if no control image displayed. Fixed: Drag tab background wasn't transparent when only dragging tab. Fixed: Settings files contained deleted properties. Fixed: Default properties are set when the control is first created.
You'll need to grab the latest version from subversion to try out the new functionality.
I always use SVN copies of components, so no problem there, just have to update ^^
EDIT: Looking good in my test, the arrow buttons look a bit odd when the window isn't maximized, but I'm not sure how that works in Chrome, as I don't use it.
Hey Paul, you are so fast, awesome! Just in case you haven't noticed, when Google Chrome is maximized, the top borders of the tabs touch the top border of the screen, so one don't have to move his/her mouse pointer precisely on the Y axis. That's very convenient, IMHO.
ReplyDeleteEdwin Yip - I need to get back to paid work soon or the kids won't be eating next week :)
ReplyDeleteYes, I've been looking at the way Chrome maxmises the form. I'm pretty close to finishing the new code. It works better than I imagined. I'll hopefully commit something later today.
Hey Paul Thornton , I checked out ChromeTabs yesterday and I'm amazed at the work you've done, they look great! I couldn't find a feature to tie them into the window title bar, so it's nice to see you're working on that. Are you planning to make a form that has to be subclassed rather than TForm? As I recall, that's how DevExpress did it for their ribbon forms.
ReplyDeleteI was also wondering, are you planning to add a page control aside from the tabs? I'm just curious because I've never actually worked with tabcontrols before, the only thing that comes to mind on how to use them, is making a borderless pagecontrol that is linked to the tabs through events.
Frédéric Hannes - Thanks - Yes, all you do is change the parent class of the form from TForm to TChromeTabsGlassForm then set the form's ChromeTabs property to the tabs that you want to display in the title bar. Everything else is automatic.
ReplyDeleteI've been thinking about adding a paired page control to the components. I'll see what I can do.
I've just committed the update for the title bar tabs (along with quite a few fixes):
ReplyDeleteUpdate: Added TChromeTabsGlassForm - Allows Chrome title bar tabs with one line of code.
Update: Added ContrainDraggedTabWithinContainer property.
Update: Added title bar tabs functionality to Demo.
Fixed: Floating Right Add button was position far right if only pinned tabs were displayed.
Fixed: Drag tab image not scaled down or alpha blended if no control image displayed.
Fixed: Drag tab background wasn't transparent when only dragging tab.
Fixed: Settings files contained deleted properties.
Fixed: Default properties are set when the control is first created.
You'll need to grab the latest version from subversion to try out the new functionality.
Please test and report back any issues :)
I always use SVN copies of components, so no problem there, just have to update ^^
ReplyDeleteEDIT: Looking good in my test, the arrow buttons look a bit odd when the window isn't maximized, but I'm not sure how that works in Chrome, as I don't use it.
Frédéric Hannes Chrome's tabs don't actually support scrolling. When the tabs reach their minimum size, they just disappear off the side of the control.
ReplyDeleteHi Paul, have you plans to autowidth each tab individually depending on the content or set width manually ?
ReplyDeleteJair Garza - I've just committed an experimental implementation of your feature request. The new property is options.display.tabs.tabwidthbycontent.
ReplyDeletePaul Thornton You should consider removing ExceptionLog from the demo project, it causes compiling errors.
ReplyDeleteEDIT: My bad, it looks like it's already gone.