TCoolBar lazarus / 31-LCL ---------------------------------------------------------------------- JuhaManninen · 2013-01-10 12:41 Hi I would like to add the TCoolBar component to LCL and to Lazarus component palette. Question: Has someone made such component? If not, would someone like to make a basic rudimentary version of it? I have not used TCoolBar myself and I have not yet studied its properties well. My motivation now is to convert more Delphi programs automatically. TCoolBar is used in many of them. The same problem was with TValueListEditor. I made a very rudimentary version already few years ago. Recently Bart and myself have improved it. yesterday I got the PickList feature working. Now it supports all features that my test-case app (DeleD) uses. DeleD is a big 3-D design application. I have almost all pieces together to port it for Lazarus.  http://delgine.com/ Juha ---------------------------------------------------------------------- Blaazen · 2013-01-10 13:35 I add one link about TCoolBar: http://delphi.about.com/od/vclusing/a/tcoolbar.htm ---------------------------------------------------------------------- JuhaManninen · 2013-01-10 14:18 Quote from: Blaazen on January 10, 2013, 02:35:02 pmI add one link about TCoolBar: http://delphi.about.com/od/vclusing/a/tcoolbar.htm It says that TControlBar is similar with TCoolBar in features. It is also missing from LCL but it would maybe be enough to implement it and then convert TCoolBar -> TControlBar by the Delphi converter. Then it is only a naming issue. So, would someone like to make a TControlBar? Juha ---------------------------------------------------------------------- Hydexon · 2013-01-10 15:21 I find a attempt of a TCoolBar here (i don't tested yet) but i see has only basic functionality. http://svn.zdechov.net/svn/PascalClassLibrary/CoolBar/ Quote from: JuhaManninen on January 10, 2013, 03:18:56 pmQuote from: Blaazen on January 10, 2013, 02:35:02 pmI add one link about TCoolBar: http://delphi.about.com/od/vclusing/a/tcoolbar.htm It says that TControlBar is similar with TCoolBar in features. It is also missing from LCL but it would maybe be enough to implement it and then convert TCoolBar -> TControlBar by the Delphi converter. Then it is only a naming issue. So, would someone like to make a TControlBar? Juha This thing not are a Win32 exclusive control ? (i mean an COMCTRL32.dll control) ---------------------------------------------------------------------- howardpc · 2013-01-10 16:29 Quote from: Hydexon on January 10, 2013, 04:21:33 pmI find a attempt of a TCoolBar here (i don't tested yet) but i see has only basic functionality. Extremely basic functionality, and not really Delphi-compatible, since the only property added that is the same as TControlBar is RowSize, and instead he has the non-Delphi properties Bands and BandIndex. To be compatible with TControlBar you would need (just in terms of newly implemented properties on top of TCustomControl) the following 30 properties: AutoDock AutoDrag BevelEdges BevelInner BevelKind BevelKind BevelOuter BevelWidth Canvas CornerEdge DrawingStyle GradientDirection; GradientEndColor; GradientStartColor; OnBandDrag; OnBandInfo; OnBandMove; OnBandPaint; OnBeginBandMove; OnCanResize OnEndBandMove; OnGesture OnMouseActivate OnPaint ParentBackground ParentCtl3D Picture RowSize RowSnap Touch I list these just to show that this is not a trivial component to be dashed off in a hurry. Well, 29 new properties are needed really since ParentCtl3D is not applicable in Lazarus and would be a property to skip. Of course you would also need to implement all the supporting methods as well, which I have not bothered to list since the property list suffices to show it is a non-trivial task. I'm not trying to put anyone off, but I think it's better to start with a realistic vision of the scope of the task ahead. ---------------------------------------------------------------------- JuhaManninen · 2013-01-10 18:45 Quote from: howardpc on January 10, 2013, 05:29:28 pmExtremely basic functionality, and not really Delphi-compatible, since the only property added that is the same as TControlBar is RowSize, and instead he has the non-Delphi properties Bands and BandIndex. I checked Delphi 7 and those 2 components don't look the same at all. I don't know why the page wrote so. Maybe you can do the same things with both but in different ways and using different properties. For example TCoolBar has "Bands" and "Bitmap" but TControlBar not. TControlBar has "Bevel..." properties but TCoolBar not. Now first I would need TCoolBar, not TControlBar. I am planning to write to the author (Chronos) and ask about using the component as a base. I found this in the sources: Template generics ================= Tutorial and basic information:   http://wiki.freepascal.org/Templates Version: 0.3 Release date: 2011-01-01 Author: Chronos Email: robie@centrum.cz Main subversion repository: http://svn.zdechov.net/svn/PascalClassLibrary/Generics/TemplateGeneric s This template generics lib is used in CoolBar. Lots of effort has been put to it, although I think that real generics in recent FPC versions can do the same thing in a more elegant way. QuoteTo be compatible with TControlBar you would need (just in terms of newly implemented properties on top of TCustomControl) the following 30 properties: AutoDock AutoDrag BevelEdges BevelInner BevelKind BevelKind BevelOuter BevelWidth Canvas CornerEdge DrawingStyle GradientDirection; GradientEndColor; GradientStartColor; OnBandDrag; OnBandInfo; OnBandMove; OnBandPaint; OnBeginBandMove; OnCanResize OnEndBandMove; OnGesture OnMouseActivate OnPaint ParentBackground ParentCtl3D Picture RowSize RowSnap Touch I list these just to show that this is not a trivial component to be dashed off in a hurry. Well, 29 new properties are needed really since ParentCtl3D is not applicable in Lazarus and would be a property to skip. Of course you would also need to implement all the supporting methods as well, which I have not bothered to list since the property list suffices to show it is a non-trivial task. I'm not trying to put anyone off, but I think it's better to start with a realistic vision of the scope of the task ahead. It does not look so bad. For example all the "Bevel..." stuff comes directly from TPanel if you inherit it from TPanel. A "realistic vision" is to make a simple version first where the interface (public and published propertied/methods) is ready but only the important things work. That is what we did with TValueListEditor. The first version was very basic. After some gradual improvements it is quite good already. Anyway, I have an urge to port this DeleD thing because I feel I am so close already. I get "kicks" from such a challenge. I try to make some kind of version of TCoolBar. Regards, Juha ---------------------------------------------------------------------- Blaazen · 2013-01-10 19:07 svn co http://svn.zdechov.net/svn/PascalClassLibrary/Generics/Template Generics/ TemplateGenerics I found it too (it is required package) but I cannot compile with FPC trunk. Chronos is member of this forum, you can try PM. ---------------------------------------------------------------------- JuhaManninen · 2013-01-10 19:37 Quote from: Hydexon on January 10, 2013, 04:21:33 pmI find a attempt of a TCoolBar here (i don't tested yet) but i see has only basic functionality. http://svn.zdechov.net/svn/PascalClassLibrary/CoolBar/ Thanks for the link. QuoteThis thing not are a Win32 exclusive control ? (i mean an COMCTRL32.dll control) The LCL component must be cross-platform. Fortunately the COMCTRL32.dll dependency in the original Delphi's CoolBar component does not really show in the programming interface. Borland has made a good job to hide the Windows specific stuff. Quote from: Blaazen on January 10, 2013, 08:07:09 pmI found it too (it is required package) but I cannot compile with FPC trunk. I would replace the template generics with ObjectList in fgl unit in any case. No big deal. Juha ---------------------------------------------------------------------- Chronos · 2013-01-10 20:43 Generics in recent stable FPC is not capable of handling the same as I tried implement in generics library using old way with templates and macros. And fgl implements only very limited part of all generics staff. So for the record I had tried to to implement such library using fpc generics for past years but there was various compilation and implementation problems even with trunk version. I called this package as NativeGenerics https://app.zdechov.net/PascalClassLibrary/b rowser/Generics/NativeGenerics In mentioned CoolBar component implementation my task was not to create Delphi compatible component and I think LCL should not be try to be as much compatible as it can be. But rather go in own way and do multiplatform stuff much more generic and multiplatform than original win32 based Delphi LCL. Then there is no need to be compatible. Rather take all good from original VCL and make it better. It is work for VCL to LCL converter to do the job. And my implementation is very basic and is used as multiple toolbars arranged side by side. Aim was to have "main big toolbar" with multiple little toolbars (bands) where every band can have visible flag turned on/off which can be toggled from menu by user and stored in registry as persistent. Then somebody with heavy knowledge of VCL and LCL who have spare time should create TCoolBar from scratch to fit LCL. ---------------------------------------------------------------------- JuhaManninen · 2013-01-11 00:24 Quote from: Chronos on January 10, 2013, 09:43:12 pmGenerics in recent stable FPC is not capable of handling the same as I tried implement in generics library using old way with templates and macros. And fgl implements only very limited part of all generics staff. So for the record I had tried to to implement such library using fpc generics for past years but there was various compilation and implementation problems even with trunk version. I called this package as NativeGenerics http://svn.zdechov.net/trac/PascalClassLibrary/browser/ Generics/NativeGenerics I looked at your NativeGenerics. Looks good. You have clearly put lots of energy for it. I have understood that FPC's generic support is improving all the time so maybe the problems are gone. I am only thinking that it may become duplicate and obsolete work when FPC's standard generics library gets improved. Yes, fgl is limited but there is another effort for a standard generics library. I know nothing much about it, except that the design is good but there are currently no people working on it. Pity! A proper generics container library is sorely missing. This is one reason why Pascal is loosing popularity and not taken seriously by many people. As you have skills and motivation for the library, you could maybe help with the FPC's library... (just an idea). QuoteIn mentioned CoolBar component implementation my task was not to create Delphi compatible component and I think LCL should not be try to be as much compatible as it can be. But rather go in own way and do multiplatform stuff much more generic and multiplatform than original win32 based Delphi LCL. Then there is no need to be compatible. Rather take all good from original VCL and make it better. It is work for VCL to LCL converter to do the job. I agree that LCL must be more than a copy of VCL but Delphi compatibility is also important. VCL compatibility is kind of the first step. The second step is to extend the existing components and create new ones. LCL has improved some things beyond VCL already but some components are still completely missing, like this CoolBar. My converter experiments prove that the "first step" is not completed yet. What should the VCL to LCL converter do when there is no similar component in LCL? Should it create the component for you using some artificial intelligence methods? However I think compatibility for one direction is enough, meaning that old Delphi programs should be possible to convert but new LCL features can happily break the compatibility. Otherwise it would restrict the design and development too much. QuoteAnd my implementation is very basic and is used as multiple toolbars arranged side by side. Aim was to have "main big toolbar" with multiple little toolbars (bands) where every band can have visible flag turned on/off which can be toggled from menu by user and stored in registry as persistent. Then somebody with heavy knowledge of VCL and LCL who have spare time should create TCoolBar from scratch to fit LCL. Thanks for the permission to use your code which you gave in a mail. I am still thinking how to implement TCoolbar. Now it looks better to inherit from TToolWindow, and Bands must be a TCollection because it must show in Object Inspector.  Etc... Regards, Juha ---------------------------------------------------------------------- Leledumbo · 2013-01-11 02:59 QuoteYes, fgl is limited but there is another effort for a standard generics library. I know nothing much about it, except that the design is good but there are currently no people working on it. Pity! A proper generics container library is sorely missing. This is one reason why Pascal is loosing popularity and not taken seriously by many people.No one is working on fcl-stl? I wonder who did those commits then... ---------------------------------------------------------------------- JuhaManninen · 2013-01-11 09:32 Quote from: Leledumbo on January 11, 2013, 03:59:54 amNo one is working on fcl-stl? I wonder who did those commits then... Yes, the name is fcl-stl. It is on my ToDo-list to look at it more closely. My knowledge is only from reading some discussions in FPC mailing list. More specifically, "Ask" (the TAChart author) wanted to have a precision math lib included in FPC and then there was talk about generics. The FPC devels themselves wrote that nobody is actively developing it. I can look for the mail thread. What I understood, fcl-stl is not ready yet to compete with generics libs in other languages. [Edit:] This is the thread : http://www.mail-archive.com/fpc- devel@lists.freepascal.org/msg27531.html However I did not find the mention of fcl-stl quality. Maybe it was another thread... Must ask from the mailing list. Juha ---------------------------------------------------------------------- Leledumbo · 2013-01-11 11:35 QuoteWhat I understood, fcl-stl is not ready yet to compete with generics libs in other languages.Don't worry, it will eventually if we work on it. I'm planning on adding some data structures, esp. those not found in other languages, e.g.: prefix tree, suffix tree, binary tree, k-ary tree (the backend for gset which in turn used by gmap is a red black tree, but the tree itself can't be used standalone AFAICS). Some simple methods like HasNext for iterator is also missing, so I'll add it as well. ---------------------------------------------------------------------- JuhaManninen · 2013-01-11 12:14 Quote from: Leledumbo on January 11, 2013, 12:35:11 pmDon't worry, it will eventually if we work on it. I'm planning on adding some data structures, esp. those not found in other languages, e.g.: prefix tree, suffix tree, binary tree, k-ary tree (the backend for gset which in turn used by gmap is a red black tree, but the tree itself can't be used standalone AFAICS). Some simple methods like HasNext for iterator is also missing, so I'll add it as well. Ok, thanks for the info. Good to know it is improving. BTW, reply to my question in the mailing list says: Patches are definitely welcome for that library. (Chronos, hint...) Regards, Juha ---------------------------------------------------------------------- Leledumbo · 2013-01-11 12:24 QuoteBTW, reply to my question in the mailing list says: Patches are definitely welcome for that library. Yeah I read that as well. Hope I can make it, I have some free time for (I hope) quite a long time. ---------------------------------------------------------------------- Ocye · 2013-01-11 15:47 Isn't user driven configuration (add/remove functions, aka actions, to the bar)  inherent part of a TCoolBar? AFAIR, there opens a dialog on right-click... Or in other words: it would be great to have those stuff. I'm wondering if it works with themes under Linux since coolbars might not have been defined by Gtk/Qt and Cocoa as well. ---------------------------------------------------------------------- JuhaManninen · 2013-01-11 19:06 Quote from: Ocye on January 11, 2013, 04:47:06 pmIsn't user driven configuration (add/remove functions, aka actions, to the bar)  inherent part of a TCoolBar? AFAIR, there opens a dialog on right- click... No, there is no default action at run-time when right-clicking. Just testing with Delphi 7. The user can move and reorder the bands with drag-and-drop but that is all. You may have seen an derived component with added pop-up support. QuoteOr in other words: it would be great to have those stuff. I'm wondering if it works with themes under Linux since coolbars might not have been defined by Gtk/Qt and Cocoa as well. It must be built from other GUI components (TPanel etc.). It could also use bindings and implement a native COM Control on Windows, but I don't see any benefit doing that. The CoolBar in Delphi 7 already behaves strange, I guess because of the COM Control itself. So, this will be a pure LCL component, no bindings. Delphi already has TControlBar which is a pure VCL component and behaves better. I am thinking how the same code could be used for both TCoolBar and TControlBar. Maybe implement TControlBar first and then implement TCoolBar as a wrapper on top of it. In any case, the first versions will be ugly and primitive. Don't hold your breath. Juha ---------------------------------------------------------------------- Chronos · 2013-01-11 20:11 Be or not to be compatible with Delphi and VCL? That's the ultimate question. It is hard to decide it exactly. It is easier to mimic existed VCL library than create completely new from scratch. And if LCL would be only nearly 1:1 interface compatible then it cannot be better than VCL in any aspect. Then halfway solution would be: basically be compatible and differ only in some cases where change could bring new feature as multiplatform support. But some characteristics of VCL components come from win32 api so it should be modified, replaced, even removed. But what about FireMonkey compatibility? Will be lazarus converter able to translate such code to LCL? Should be LCL enhanced to new abilities of FMX? Back to topic: TCoolBar seems to me is better component than TControlBar. Both may not exists in other widgedsets but for windows apps it would be definitely good to have it. Question is what features it should have? Completely same as VCL variant? Hard part is drag and drop feature. Who tried to implement custom docking system knows how complicated it could be. And TCoolBar is basically "super toolbar" with draggable horizontal or vertical autoarranged subtoolbars or better to say bands as container for other TWinControl descendants. I would like to contribute with own code but both Lazarus and FPC is not well organized project. It has bugtracker, forum, wiki but all is rather unperfect and everything is moving very slowly. I have three bug reports opened for few months some even with submitted patch but nobody cares. There are no human resources. There are other priorities. Core programmers work only in spare time. Am I idealist or something is wrong? Some significant example how things could work? Look at LibreOffice or some linux distributions. Maybe I am willing to update czech localization but need access to repository just to language files. I dont want to bother anyone with every file update to be merged. Look at Launchpad and other projects how it can work easily. Many things could be better. TCoolBar is just only one pease which wont save whole project. It is for another long offtopic discussion ---------------------------------------------------------------------- JuhaManninen · 2013-01-11 21:26 Quote from: Chronos on January 11, 2013, 09:11:02 pmBe or not to be compatible with Delphi and VCL? That's the ultimate question. ... There are 2 different things : _change_ the interface and _extend_ the interface. Extending it does not break compatibility with existing Delphi apps. And yes, then LCL can be better than VLC. QuoteBut what about FireMonkey compatibility? Will be lazarus converter able to translate such code to LCL? Should be LCL enhanced to new abilities of FMX? No. At least I have no plans to do that. If someone has big enough "itch" for it, then he will implement such converter. But, I doubt it will happen any time soon, knowing the limited amount of contributors and their available time. QuoteBack to topic: TCoolBar seems to me is better component than TControlBar. Both may not exists in other widgedsets but for windows apps it would be definitely good to have it. Did you test TCoolBar with Delphi. In my tests it behaved wrong sometimes, hiding the bands and moving to wrong place. At design-time I could move the attached control away from the band. It was a mess. TControlBar behaved better for me. There will not be a specific widgedset binding for these components. So, there will not be TWSCoolBar or TWSControlBar. They will be built from basic LCL components, like TPanel, which obviously have a widgedset binding. QuoteQuestion is what features it should have? Completely same as VCL variant? Hard part is drag and drop feature. Who tried to implement custom docking system knows how complicated it could be. And TCoolBar is basically "super toolbar" with draggable horizontal or vertical autoarranged subtoolbars or better to say bands as container for other TWinControl descendants. The interface defined by Borland must be identical, more or less. "Interface" here means everything in protected, public and published sections. Yes, let's see how drag and drop goes. It will be another exercise. QuoteI would like to contribute with own code but both Lazarus and FPC is not well organized project. It has bugtracker, forum, wiki but all is rather unperfect and everything is moving very slowly. I have three bug reports opened for few months some even with submitted patch but nobody cares. There are no human resources. There are other priorities. Core programmers work only in spare time. Am I idealist or something is wrong? Some significant example how things could work? Look at LibreOffice or some linux distributions. I saw you have 2 open issues, both with patches. I try to look at them soon (Paul Ishenin seems to be busy). I am sorry on behalf of Lazarus developers. Bug reports with patches should not be ignored. It is bad. Otherwise I don't see such big problems in the development process or tools. I also don't believe that other projects can do it significantly better. All big projects have thousands of open tickets. It is not unusual. QuoteMaybe I am willing to update czech localization but need access to repository just to language files. I dont want to bother anyone with every file update to be merged. Look at Launchpad and other projects how it can work easily. Many things could be better. TCoolBar is just only one pease which wont save whole project. It is for another long offtopic discussion Maxim seems to apply translations happily. Why is it a problem? But yes, let's not make it off-topic. Please open a new topic, especially if you have specific ideas how to improve things. Juha ---------------------------------------------------------------------- Chronos · 2013-01-12 10:38 This is mostly matter of work organization and priorities. Lazarus/FPC is classic pure open source project where work depends on contributors which have probably their daily job and contribute to project only occasionally. Then no expectation could be made about any deadline and requested features. And sure this have advantages and disadvantages. Main disadvantage is that community suffer because many problems take years to solve and nothing is certain. TCoolBar or TControlBar is only on of many missing and "late" features which should be done years ago. What about Gtk3, windows 8 and metro compatibility, docked IDE, native networking components, audio components, gestures, multi-touch support, and so on. Yes, these are big expectations from small project without active full time job development but people are coming here and get some false impression. Yes, coolbar in delphi have their own problems but if I remember correctly it is simpler and more intuitive for use then TControlBar. Drag & drop is core part of it. Docking is not really necessary but there are some examples of advanced application which allow to dock toolbars to form sides or just have all of them in single top section or all toolbars could be floated as tool window. I thing Adobe Photoshop and Paint Shop Pro use such behaviour. There is some documentation about drag & drop with LCL http://wiki.freepascal.org/LCL_Drag_Drop But docking part is much harder because docking LCL is still not completed and look like mess (also thanks to VCL compatibility and some different concept). What about visual style of grab handle? Does multi-platform theme manager know something like this? This apply for docking too. There are lot of work to be done before coolbar could be completed and ready to use. I will look forward to your results. It will be definitely bonus for all advanced GUI designers. ---------------------------------------------------------------------- JuhaManninen · 2013-01-17 08:58 Chronos: BTW, I applied your patch from issue #23251 some days ago. Now I had to revert it. See the issue report for details. [Edit:] The problem is apparently not caused by your patch but I will hold it back until things work with GTK2. Juha ---------------------------------------------------------------------- timppl · 2013-01-18 06:29 I don't know if it would be of interest, but I have an implementation of TControlBar I have made. It does not have full functionality ( at least I am fairly sure it does not. I have not got a copy of delphi and have never seen the full delphi one working ). I would be happy to contribute it if it is wanted ( although I would have to reveiw it and get rid of some of my worst mistakes  ). Regards Tim ---------------------------------------------------------------------- JuhaManninen · 2013-01-18 08:17 Sure, I would be happy to look at your code and maybe use it as a starting point. I promise not to be too critical about it, if you have some experimental stuff there. I looked at the Delphi's TControlBar component. I was planning to use its ideas in a reverse-engineered manner. However, the code is really strange, obfuscated and overly complex. We can do better. I have ideas how to implement the layout alignment for TControlBar and TCoolBar (using LCL's anchors) but nothing is tested yet. I hope I can use time for this during weekend. Regards, Juha ---------------------------------------------------------------------- timppl · 2013-01-22 06:38 Here is my ( incomplete but working ) implementation of TControlBar. Not it registers to my own tab in Lazarus. regards Tim ---------------------------------------------------------------------- JuhaManninen · 2013-01-24 00:14 Quote from: timppl on January 22, 2013, 07:38:51 amHere is my ( incomplete but working ) implementation of TControlBar. Not it registers to my own tab in Lazarus. Thanks. Based on my first looks it does not do much yet. There is no alignment algorithm nor dragging nor other TControlBar features. There is basically just what TCustomControl provides by default. But it is a starting point, yes. I will take a better look when I have time. Regards, Juha ---------------------------------------------------------------------- timppl · 2013-01-24 06:21 Hi Juha Yes I only needed a minimal implementation to work in the application I am portin to lazarus/fpc. Improving it ( and other components I have put together ) are on the todo list when I have got the applications working adequately. Tim ---------------------------------------------------------------------- JuhaManninen · 2013-01-28 00:26 Hi I finally implemented TCoolbar and it even works (somehow). Next I will try how the DeleD 3-D app looks when ported to use it. The component is still rudimentary and basic. Many things are missing: - Dragging the bands by user is not possible yet. There will be a small dragging area on the left. Actually I am looking for examples how to do it. Anybody has good examples? As you can see I don't have much experience writing these components. - A control associated with a band can be moved at design-time away from the band. Actually it behaves as poorly as the original Delphi's COM-based component, but I want to make this one more polished. - Bitmaps can be created and assigned but they are not shown yet. - A new band is not automatically created when a new component is dropped onto a CoolBar. It should be. Yet, you can already add and remove bands in a collection editor, select an associated control from a drop-down list and use the associated control. It is usable already. On a positive side, it is fully cross-platform. It is a pure LCL component, built using the more primitive LCL components as construction blocks. I also added a skeleton version of TControlBar. It does not do much more than what a TPanel already does. It will require lots of work before it is good. May I ask help? I know here are many graphically talented people. I would need icons for the component toolbar for both TCoolBar and TControlBar. Now there are just "placeholder" icons copied from TToolBar. And yes, patches are of course welcome to improve TCoolBar. It should be rather easy to improve now that the basic functionality is there. If somebody wants to take TControlBar as a challenge, please do, but it is a more difficult beast than TCoolBar. Regards, Juha ---------------------------------------------------------------------- wjackson153 · 2013-01-28 05:08 What kind of icons art work are you looking for? could you provide more details , im pretty fluent in gimp ---------------------------------------------------------------------- JuhaManninen · 2013-01-28 08:40 Quote from: wjackson153 on January 28, 2013, 06:08:45 amWhat kind of icons art work are you looking for? They can be similar than in Delphi, but not necessarily. You can improvise if you like. Juha ---------------------------------------------------------------------- Avishai · 2013-01-30 13:28 TCoolBar generates an Access Violation on startup if the component is made RightToLeft using RightToLeftLayout on MSWindows. procedure RTLCtrl(ACtrl: TObject); { Make TWinControl RightToLeft - Windows ONLY! } const   RightToLeftLayout = $400000;    NoInheritLayout = $00100000; begin {$IfDef Windows}   if ACtrl is TWinControl then     with TWinControl(ACtrl) do begin       SetWindowLong(Handle, GWL_EXSTYLE, GetWindowLong(Handle, GWL_EXSTYLE)         or RightToLeftLayout or NoInheritLayout);   end; {$EndIf} end; Edit: My apologies.  It wasn't making the control RightToLeft that caused the access violation.  It failed when my code tried to add Bands to TCoolBar.  I tried adding Bands to a LeftToRight TCoolBar and still got the Access Violation so it doesn't seem to be related to RightToLeft. ---------------------------------------------------------------------- Avishai · 2013-01-30 13:41 TControlBar becomes Black when it is made RightToLeft using RightToLeftLayout on MSWindows. ---------------------------------------------------------------------- teos · 2013-01-30 20:27 I keep Delphi because of the huge component sets like JCL and JVCL, knowing that they have sort of alike components. The coolbar is not holding me back from a move to Lazarus. The property grid also does not (there is an alternative property grid available). I don't think that the components that are part of Delphi are really what is missing. IMHO a lot of people use JCL and JVCL in Delphi and I really think that your effords are better spent on filling that gap.. Sorry if I'm off topic but every time I go back to Delphi, it's because of the extra components, not because of the standard ones.. ---------------------------------------------------------------------- JuhaManninen · 2013-01-30 23:09 There was a crash in the initial version of CoolBar. It was fixed soon. I should not make last minute changes at night. More functionality is coming ... Quote from: teos on January 30, 2013, 09:27:41 pmI don't think that the components that are part of Delphi are really what is missing. IMHO a lot of people use JCL and JVCL in Delphi and I really think that your effords are better spent on filling that gap.. Sorry if I'm off topic but every time I go back to Delphi, it's because of the extra components, not because of the standard ones.. LCL is supposed to be (mostly) compatible with VCL. It means you should be able to port a Delphi application easily for Lazarus if it uses only VCL components. Otherwise this claim for VCL compatibility has no substance. Replacing a component with another fall-back component does not work well because the properties are different. Trying to convert DeleD 3-D was a good example. Now it should be possible. I will try it again when I gather some energy. I understood there are many high quality components for Lazarus. Ofter they are not compatible with Delphi components though. Please forget JCL and JVCL if you want to work with Lazarus. They have so many dependencies for Windows that they will never be ported. The code has very poor quality, everything depends on everything. Small parts can be ported after heavy refactoring and cleaning. For example the bzip2 lib interface I ported already supported *nix with IFDEFs and everything, but still depended on Windows unit. So there was no way to compile it for Linux (Nuts!). I extracted it and removed maybe 2/3 of the code and now it works. This was a simple example, the GUI components are worse. Juha ---------------------------------------------------------------------- JuhaManninen · 2013-03-01 18:18 Quote from: JuhaManninen on January 28, 2013, 01:26:04 amMay I ask help? I know here are many graphically talented people. I would need icons for the component toolbar for both TCoolBar and TControlBar. Now there are just "placeholder" icons copied from TToolBar. Anybody interested in helping with the icons? They can be similar than in Delphi, but not necessarily. BTW, CoolBar has been in a good shape already for some time. Only important part missing is the run-time dragging of the bands. Now the bands' order can be changed only at design-time. ControlBar is still rudimentary. Regards, Juha ---------------------------------------------------------------------- Blaazen · 2013-03-01 19:26 Hi, I cannot force the CoolBar bands to be more in one row. Now (Qt4) each band is in its own row only. I can try to paint some cool icons in GIMP. I don't know what icon it has in Delphi but it does not matter. ---------------------------------------------------------------------- taazz · 2013-03-01 19:41 you want something like this or a bit more funcy? Oh and how many? EDIT added a second one with more gradients the delphi icon can be seen here if any one is interested http://www.krech.de/Grafix/search.jpg ---------------------------------------------------------------------- Avishai · 2013-03-01 19:49 This is a bit off topic, but I tested TCoolBar using RightToLeftLayout on MSWindows and I'm happy to say that it seems to work fine.  However, for other OS's maybe it should have BiDiMode published and implemented?  I really don't know if this is true or not because I work only with MSWindows. Anyway, very nice work ---------------------------------------------------------------------- Avishai · 2013-03-01 20:38 I guess I spoke too soon when I said it works fine with RightToLeftLayout.  When I try to resize the Form at RunTime, I get this Error: "TWinControl.WMSize loop detected, the widgetset does not like the LCL bounds or sends unneeded wmsize message: Edit1:TEdit.BoundsRealized=l=61,t=3,r=593,b=27 NewBoundsRealized=l=593,t=3,r=1125,b=27" ---------------------------------------------------------------------- JuhaManninen · 2013-03-01 21:35 Quote from: Blaazen on March 01, 2013, 08:26:56 pmI cannot force the CoolBar bands to be more in one row. Now (Qt4) each band is in its own row only. I can try to paint some cool icons in GIMP. I don't know what icon it has in Delphi but it does not matter. Blaazen, that is how CoolBar works. The bands are top aligned, each occupying one row. At least that is my understanding. Typically the component on a band is ToolBar. The other component, ControlBar, allows you to put many bands / components on one row, but the layout algorithm is not implemented yet. Quote from: taazzyou want something like this or a bit more funcy? Oh and how many? taazz, your pics look more like file or folder icons. I think they should represent the bands somehow. Quotethe delphi icon can be seen here if any one is interested Yes, that is CoolBar. ControlBar is in the Additional tab and its icon looks almost the same. Juha ---------------------------------------------------------------------- Blaazen · 2013-03-01 21:59 QuoteBlaazen, that is how CoolBar works. The bands are top aligned, each occupying one row. At least that is my understanding. Typically the component on a band is ToolBar.I am not sure. I have no Delphi, I only can search screenshots on web. Here: http://prof-xaker.at.ua/load/iskhodniki/raznoe/ispolzovanie_komp onenta_tcoolbar/88-1-0-1123 are more bands in one row (but I agree: one component in each band). ---------------------------------------------------------------------- Avishai · 2013-03-01 22:04 You can have multiple controls in one band  in you add them to a TPanel and then make the TPanel the Band.Control:= the TPanel. ---------------------------------------------------------------------- JuhaManninen · 2013-03-01 22:16 Quote from: Avishai on March 01, 2013, 08:49:22 pmThis is a bit off topic, but I tested TCoolBar using RightToLeftLayout on MSWindows and I'm happy to say that it seems to work fine.  However, for other OS's maybe it should have BiDiMode published and implemented?  I really don't know if this is true or not because I work only with MSWindows. I published BiDiMode in r40455 for both CoolBar and ControlBar. It is unfortunate it gives an "TWinControl.WMSize loop detected" error with RightToLeftLayout on Windows. QuoteAnyway, very nice work Thanks for the feedback. I have no time to solve RightToLeftLayout problems now but maybe you could debug the code. The code for CoolBar is quite clean and compact. The implementation part is less than 600 lines now. The whole band and associated component placement is done in AlignControls. Please take a look. Juha ---------------------------------------------------------------------- Avishai · 2013-03-01 22:22 I will take a look but I am not too hopeful.  I have the same problem and error with TComboBox if any component is anchored to anything and RightToLeftLayout is used.  I've looked for this problem for weeks and can't find where things go wrong. ---------------------------------------------------------------------- Blaazen · 2013-03-01 22:47 I found this article: http://stackoverflow.com/questions/6543213/delphi-tcoolbar- ttoolbartedittcheckbox It is described there: If property Break = True then Band starts at a new row. Otherwise it continues on the same row next to previous Band. ---------------------------------------------------------------------- JuhaManninen · 2013-03-01 22:53 Quote from: Blaazen on March 01, 2013, 10:59:59 pmI am not sure. I have no Delphi, I only can search screenshots on web. Here: http://prof-xaker.at.ua/load/iskhodniki/raznoe/ispolzovanie_komp onenta_tcoolbar/88-1-0-1123 are more bands in one row (but I agree: one component in each band). That looks like a TControlBar. Maybe they mixed the name. I did not find a way to put bands on one row in Delphi. If someone finds a way, please tell me. [Edit:] I saw your new post: >  If property Break = True then Band starts at a new row It means the layout system needs much more work. It starts to resemble the ControlBar layout algorithm (which is not implemented either). You don't have any Delphi version? There are some "backup" copies old old Delphi versions in internet. Downloading such backup copy even for testing purposes is not legal so I don't recommend it of course. My employer bought the copies I use myself. Juha ---------------------------------------------------------------------- Avishai · 2013-03-01 23:07 I just checked with Delphi 6.  What Blaazen said seems to be true.  When Break:= False, Bands are continued on the same line.  When Break:= True, the following band is on a new line. ---------------------------------------------------------------------- taazz · 2013-03-02 04:06 Oh you mean something like this? The previous icons show a single band of a coolbar, I chose the folder icon because is most used an easily recognized to be the button on the band. ---------------------------------------------------------------------- taazz · 2013-03-02 06:33 The last one. I'm out of ideas at this point. ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 10:11 Thanks taazz! I used your icon numbers 3 and 7 for TCoolBar and TControlBar. Committed in r40458. First they looked a little foggy, maybe because of the amount of details, but in the component bar they look very good. Please check and see yourself. How much time you spend for such pic? Other improvements for these components are welcome, too. For example CoolBar has a bitmap property but it does not do anything yet. I must look at the layout algorithm some time. Regards, Juha ---------------------------------------------------------------------- taazz · 2013-03-02 10:25 I'm not an artist so it took me overall 2 hours for all the icons you see here. I have an extensive library of svg files that can be used as icons and a couple icons ready which I combined. The fogginess is a result of the resizing in the icon editor it can be removed but it needs pixel by pixel corrections at that small sizes and I am a bit overwhelmed with my tasks so I opted not to spend more time on them I'll try to clean them up when time permits. ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 11:06 Quote from: taazz on March 02, 2013, 11:25:56 amThe fogginess is a result of the resizing in the icon editor it can be removed but it needs pixel by pixel corrections at that small sizes and I am a bit overwhelmed with my tasks so I opted not to spend more time on them I'll try to clean them up when time permits. It is not really a problem because the component toolbar shows only small icons. If they could be scaled then it would become a problem. Juha ---------------------------------------------------------------------- Avishai · 2013-03-02 11:20 I just updated Lazarus and the BiDiMode properties are there as you said.  However, setting BiDiMode:= bdRightToLeft does not mirror the TCoolBar.  Child controls do pick it up as ParentBidiMode, but it looks very strange when part is RightToLeft and part is LeftToRight. ---------------------------------------------------------------------- Blaazen · 2013-03-02 11:29 For my own app., I designed icons using Inkscape (vectors, *.svg). I convert them to *.png with a command line utility "rsvg" using bash script: Code: [Select]#!/bin/bash for i in *.[Ss][Vv][Gg]; do rsvg-convert $i -w 64 -h 64 -o ../default64normal/`echo $i | sed -e 's/svg$/png/'`; done for i in *.[Ss][Vv][Gg]; do rsvg-convert $i -w 48 -h 48 -o ../default48normal/`echo $i | sed -e 's/svg$/png/'`; done for i in *.[Ss][Vv][Gg]; do rsvg-convert $i -w 32 -h 32 -o ../default32normal/`echo $i | sed -e 's/svg$/png/'`; done for i in *.[Ss][Vv][Gg]; do rsvg-convert $i -w 24 -h 24 -o ../default24normal/`echo $i | sed -e 's/svg$/png/'`; done for i in *.[Ss][Vv][Gg]; do rsvg-convert $i -w 16 -h 16 -o ../default16normal/`echo $i | sed -e 's/svg$/png/'`; done    I'm pretty sure it come useful when Retina displays will come. ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 11:49 Quote from: Avishai on March 02, 2013, 12:20:51 pmI just updated Lazarus and the BiDiMode properties are there as you said.  However, setting BiDiMode:= bdRightToLeft does not mirror the TCoolBar.  Child controls do pick it up as ParentBidiMode, but it looks very strange when part is RightToLeft and part is LeftToRight. The bands and their associated controls are now top aligned. The only thing that should be affected is the optional Text in a band. It is now left-aligned and the control is aligned to its right edge. It should be reversed when BiDiMode <> bdLeftToRight. Is this correct? Juha ---------------------------------------------------------------------- Avishai · 2013-03-02 12:18 This is an Image of a RightToLeft TCoolBar.  You will see that everything is Mirrored.  Because it is MSWindows I am using RightToLeftLayout and not BiDiMode.  Under MSWindows, BiDiMode has been obsolete for a long time. ---------------------------------------------------------------------- Avishai · 2013-03-02 12:32 RightToLeftLayout mirrors the Canvas making to origin (0,0) on the Right and increases to the Left.  It also takes care of RightToLeft Text. ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 13:18 Quote from: Avishai on March 02, 2013, 01:18:25 pmThis is an Image of a RightToLeft TCoolBar.  You will see that everything is Mirrored.  Because it is MSWindows I am using RightToLeftLayout and not BiDiMode.  Under MSWindows, BiDiMode has been obsolete for a long time. Ok, but BiDiMode must be used for this component because it is essentially custom drawn. Delphi's CoolBar is only a wrapper for the Windows COM component. It desperately tries to communicate with the actual component using messages. If you look at its source code, it is quite a mess. It never worked properly. For example at design-time you can move the associated controls away from their bands which is quite fundamental flaw. In my custom drawn solution an overridden AlignControls relocates the controls. It prevents them moving, no other logic is needed for that. Clean, right? I guess Borland realized how problematic this Windows COM component was. That's why they made (or bought) ControlBar which solves similar problems than CoolBar but is pure Pascal. I wanted to understand how the the layout algorithm in ControlBar works. For some reason its code is also a big mess. For example it uses nested "with" statements, both of them referring to variables of same type but different instance. Uhhh! I used a feature found in Cody package to explode those "with" statements, then I refactored the code to split the nearly 1000 line functions into smaller pieces. Still, even after debugging the code I did not understand how it worked! My diagnosis is that it has a big amount of useless code, originally made for some other purpose. Maybe they bought it from some hacker who then disappeared, and then nobody dared to touch the code. It has bugs that still have not been fixed in the 10+ years. Delphi has lots of good design and code, but it also has some horribly low quality code. That is why it bothers me sometimes that everything in LCL must be compatible with VCL, including bugs. No, we can do better. Juha ---------------------------------------------------------------------- Avishai · 2013-03-02 13:42 Delphi has lots of good design and code, but it also has some horribly low quality code. Haha! Yes, I couldn't agree more   It seems that at some point Delphi stopped improving existing code and concentrated on adding huge amounts of new business related capabilities.  The problem being that if the core foundation doesn't work, the new capabilities can't work either. I understand that BiDiMode must remain a part of Lazarus.  Partly for Delphi comparability and I'm guessing that it may be a requirement for non-MSWindows OS's as well.  But RightToLeftLayout needs to be part of Lazarus for MSWindows.  It solves far more problems than it creates and BiDiMode simply is not adequate.  Just an example:  TPageControl can not be mirrored with BiDiMode so you end up with a mix of RightToLeft and LeftToRight controls and that is not acceptable. But RightToLeftLayout works perfectly. ---------------------------------------------------------------------- taazz · 2013-03-02 14:42 Actually tcontrolbar was in delphi long before the TCoolbar component was introduced and I think they were forced in to TCoolBar because the look and feel wasn't as hip and trendy as the latest and greatest from MS at that time when IE5 became the standard in 90% of windows installation some one implemented TCoolBar. In any case LCL has its own little quirks take for instance the resize mess and the endless loops you end up with, the moment you try to re size your own internal components. I still haven't rapt my head around that piece of code. ---------------------------------------------------------------------- Avishai · 2013-03-02 15:08 This has nothing to do with RightToLeft.  I just tried TCoolBar.AutoSize = True with a TEdit in Band 0.  I got the following Error: TControl.ChangeBounds loop detected Edit1:TEdit Left=53, Top=3, Widrh=409, Height=24 NewLeft=53, NewTop=-2, NewWidth=409, NewHeight=24 ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 16:36 Quote from: taazz on March 02, 2013, 03:42:05 pmActually tcontrolbar was in delphi long before the TCoolbar component was introduced and I think they were forced in to TCoolBar because the look and feel wasn't as hip and trendy as the latest and greatest from MS at that time when IE5 became the standard in 90% of windows installation some one implemented TCoolBar. Wow, I didn't know that! CoolBar seems to be even more buggy than ControlBar, based on complaints found by a Google search. But no worries, the LCL versions of those components will be perfect when they are ready (who knows when that is...). QuoteIn any case LCL has its own little quirks take for instance the resize mess and the endless loops you end up with, the moment you try to re size your own internal components. I still haven't rapt my head around that piece of code. Yes, the layout system in LCL is different, but IMO it is better. LCL automatically adjusts sizes until all has settled. VCL does not and thus it does not loop. It is quite well explained here:  http://wiki.lazarus.freepascal.org/Autosize_/_Layout#Difference_to_De lphi I must also wrap my head around alignment and autosize again for the loop Avishai found. I think I must override CalculatePreferredSize, too. Juha ---------------------------------------------------------------------- taazz · 2013-03-02 17:25 Warning what follows is personal opinion so take it with a grain of salt. Actually I disagree. Although delphi does not try to enforce any kind of layout it gives you the tools to do that your self and it is quite simple to use them in your code to do anything you like. What ever tools are given to you they work as advertised eg anchors. Simplistic? Yes a bit over engineered? Probably, non the less it works and it works well. I can't say the same think for the lcl layout. The only think I managed to use with out problems is the alignment (alRight, alClient etc) and the border spacing. Everything else has produced problems for me, anchors where extremely nasty because they did not raise any error they simple did not work when they were set from a constructor. My worst irritation is the fact that the components call the parent's resize method inside their resize method, a practice I find problematic in most cases and I haven't seen any code that uses such concepts that do not creates more problems than it solves yet. If you must call it then do it asynchronously make sure it is called after the current resize has finished its job, that of course would not solve the current looping problem. ---------------------------------------------------------------------- Blaazen · 2013-03-02 18:06 QuoteIn any case LCL has its own little quirks take for instance the resize mess and the endless loops you end up with.I have sometimes endless loops when I set anchors wrongly. Sometimes it shows message window (This will create circular dependency [Ignore] [Cancel]), sometimes it freezes for a while. ---------------------------------------------------------------------- JuhaManninen · 2013-03-02 18:25 Yes, I realize it can cause unnecessary problems when using a Delphi compatible layout. However it is needed for the more advanced layouts that LCL supports as the controls can be anchored to each other in different ways. That is my understanding anyway. Mattias could explain it better. [Edit] I had to learn quite much about those layout algorithms to make CoolBar.AutoSize work. A label used for a Text property always created a ChangeBounds loop error, only because I set its Left and Top properties. I experimented for many hours and finally had to ask Mattias. Only the label's Align must be set to alCustom instead of alNone. Then it started to work. CoolBar was a difficult case because it implements its own layout by overriding AlignControls and CalculatePreferredSize (for AutoSize). I could have saved many hours by asking Mattias at once, but I feel stupid always asking him like a child. Anyway, now I know more. Next component will be easier. Juha ---------------------------------------------------------------------- JuhaManninen · 2013-03-06 15:35 Quote from: Avishai on March 02, 2013, 04:08:05 pmTControl.ChangeBounds loop detected Edit1:TEdit Left=53, Top=3, Widrh=409, Height=24 NewLeft=53, NewTop=-2, NewWidth=409, NewHeight=24 All ChangeBounds loops are now fixed. It was a tough one. BiDiMode works, too. There are some minor layout issues left and the "Break" feature is not implemented at all. Juha ---------------------------------------------------------------------- Blaazen · 2013-03-06 16:56 A little off-topic for Juha. In past, I reported this: http://bugs.freepascal.org/view.php?id=23029 You replied there that the control will be redesigned. I am curious how. Reason is that I designed control (CustomSpinEdit - see image) similar to TEditButton, i.e. basic component is TCustomEdit and buttons (TGraphicControl) are sticked to it. Before, I also tried another design, the basic control was TWinControl (as a non-visual container) and both TCustomEdit and side-buttons was placed on it. It worked but it had a problem with focus. AFAIR if I switched focus (with Tab), the focus was not always given correctly to Edit. Also, TWinControl only as a container is an overhead. Therefore I left that design. Advantage of the previous design was mainly better anchoring and easier usage for a grid cell editor. So I would like to know if it is already decided how the control will be redesigned. Thanks. ---------------------------------------------------------------------- JuhaManninen · 2013-03-06 17:51 Quote from: Blaazen on March 06, 2013, 05:56:28 pmA little off-topic for Juha. In past, I reported this: http://bugs.freepascal.org/view.php?id=23029 You replied there that the control will be redesigned. I am curious how. Reason is that I designed control (CustomSpinEdit - see image) similar to TEditButton, i.e. basic component is TCustomEdit and buttons (TGraphicControl) are sticked to it. ... It has not been discussed for some time, but the consensus is that it should be changed. In earlier discussions the idea was to tweak the bounds etc. at widgetset level which may be difficult in some cases and requires more maintenance. In the Mantis issue #12155, related to your issue, Mattias however writes he made a proof of concept version by using an edit and a button on a panel. He has put it to examples/groupedcontrols. Please take a look. May I suggest that you make a refined version of that control. First the validity of this design must be confirmed on mailing list. Then I can help with committing the code. First it can be inside {$IFDEF NewEditButton} and becomes default only after it is well tested. It would make its way to Lazarus 1.2 which is not scheduled yet. What do you say? Later you can use the same design for your CustomSpinEdit (which you should rename because LCL already has one). The exact same code may not be reusable for your 2-button design. Juha ---------------------------------------------------------------------- Blaazen · 2013-03-06 18:48 Thanks for reply. @Later you can use the same design for your CustomSpinEdit (which you should rename because LCL already has one). The exact same code may not be reusable for your 2-button design. It already has other name, I used CustomSpinEdit only now to better describe what it is. In fact, it's not 2-button design, it can have 1-9 buttons but it is everything only one TGraphicControl. I saw the old bugreport, I also started the demo. Some things has to be finished, vertical resizing for example. Anyway, it is interesting. Don't you know why Mattias decided to use TCustomPanel (which is TCustomControl) instead of TWinControl (as I did)? I chose the second because it is more lightweight. Only note: if someone else want to test the component, you need to have installed "runtimetypeinfo" package. EDIT: @ May I suggest that you make a refined version of that control. First the validity of this design must be confirmed on mailing list. Then I can help with committing the code. First it can be inside {$IFDEF NewEditButton} and becomes default only after it is well tested. It would make its way to Lazarus 1.2 which is not scheduled yet. What do you say? OK. Since many is already done, I'll try to finish missing pieces and test in Qt4 and GTK2. As a stand-alone component, anchoring and as a grid cell editor. ---------------------------------------------------------------------- JuhaManninen · 2013-03-06 21:33 Quote from: Blaazen on March 06, 2013, 07:48:19 pmAnyway, it is interesting. Don't you know why Mattias decided to use TCustomPanel (which is TCustomControl) instead of TWinControl (as I did)? I guess Panel provides some functionality that TWinControl does not provide. Don't know. QuoteOK. Since many is already done, I'll try to finish missing pieces and test in Qt4 and GTK2. As a stand-alone component, anchoring and as a grid cell editor. Great. Could you also write to mailing list to confirm this plan is OK. Many developers don't follow the forum actively. Juha ---------------------------------------------------------------------- taazz · 2013-04-29 23:41 Stupid question alert. Where can I get the tcoolbar and tcontrolbar components? ---------------------------------------------------------------------- Blaazen · 2013-04-29 23:44 TControlBar is on "Additional" and TCoolBar is on "Common Controls". AFAIK TCoolBar.Bands does not work properly yet (they are not Delphi compatible). Of course, in Lazarus trunk. ---------------------------------------------------------------------- taazz · 2013-04-30 00:34 thank you Blaazen. ---------------------------------------------------------------------- JuhaManninen · 2013-04-30 10:33 Quote from: Blaazen on April 30, 2013, 01:44:56 amTControlBar is on "Additional" and TCoolBar is on "Common Controls". The tabs are the same as in Delphi. It is a historical remain as TCoolBar used to be a COM Windows control. In LCL it is built from other widget primitives. It should be in the same tab with TControlBar. QuoteAFAIK TCoolBar.Bands does not work properly yet (they are not Delphi compatible). Yes, the "Break" property does not work, neither does dragging the bands at run time. CoolBar.Bitmap and CoolBar.Images have no effect. All properties needed for Delphi conversion are there and the implemented features work well. In parts it works better than the Delphi's COM control. VCL communicated with it using messages and it never worked well. You can move the controls out of their bands for example. In LCL's CoolBar you cannot do that.