New version of SpkToolbar

[wp]

In the attachment I am posting an extended and corrected version of SpkToolbar (v0.2). These are the changes:

* Added TSpkCheckbox and TSpkRadiobutton (unit spkt_Checkboxes.pas). I was missing some checkable buttons in the old version.
* Applied ImageIndex when assigning an action
* Added a property editor for image index
  - use specialized ImageIndexPropertyEditor to link to the imagelist
  - assign default values to ImageIndex properties
  - use types TImageIndex instead of integer
* Make sure that item properties (caption, imageindex etc) are updated when the action changes
* Fixed button state to change immediately after mouse-up from pressed to hover, the old version needed a mouse move to change button color
* Found bug in ComponentEditor form causing "Class not found" error: tabs, panes, and items were added without names. Assigning a name by FDesigner.UniqueName fixed the issue.
* Duplicate components after Cut & Paste because missing destruction of components after deletion from internal list
* Naming issue of components added by designer (counter starting at 2, not 1) fixed
* Changed default color of the SpkToolbar to clSkyBlue
* Added component icon to the package
* Changed {$mode delphi} to {$mode objfpc}

There are also two more demos: the first one shows how the toolbar can be used at runtime only (without installation), the second one demonstrates the usage of actions.

Note that there are still two bugs in design mode:
* Add a SpkToolbar, double-click and add tabs, panes and buttons. Compile and run. Lazaraus will complain about missing units that implement the added controls. Either add these units (spkt_Tab, spkt_Pane, spkt_Buttons, spkt_Checkboxes) manually to the uses clause. Simpler: just add any other component to the form, and delete it again, then the missing units are added automatically to the uses clause
* Delete the SpkToolbar (having tabs, panes, buttons) from the form. The toolbar disappears, but the added controls, however, are left in the form declaration. So far, I could not find how to delete these controls in design mode without crashing Lararus.

It would be nice if somebody with write permission could add these updated units to the CCR. Also, it would be find if someone who speaks polish would translate the polish comments.

[LuizAmérico]

Create a patch and post here

http://wiki.freepascal.org/Creating_A_Patch

[wp]

Here it is

[LuizAmérico]

Thanks. The patch needs some cleanups before being applied since it does a lot of thing in one go. Also is giving an error while applying it.

1) The change to mode objfpc does not bring any code benefit, it just creates pollution, it also will make harder to merge changes from original delphi (if any). Please revert with related changes

2) there are some code formatting, this makes harder to review the actual changes. You can send a patch later with only formatting

3) The component icon should go in register unit, this will make the end user executable smaller. See other components source code in Lazarus svn

4) Please send a patch with the demo project separated

5) Avoid double type check like

+if AItem is TSpkComponent then
+   (AItem as TSpkComponent).FCollection := self;

you can do

+if AItem is TSpkComponent then
+   TSpkComponent(AItem).FCollection := self;

[wp]

Ok, here are two patches modified according to your suggestions, one for the component source, the other one for the demos.

[LuizAmérico]

Thanks. Applied with minor changes.

But there are some problems:

- The new components and new icon are not registered in the ide they should go in RegisterSpkToolbar.pas. The files should be added also to the package.

- The basic demo was not updated. Please update the svn and create a new patch

[Sternas Stefanos]

Try this

procedure Register;
begin
  RegisterComponents('SpkToolbar', [TSpkToolbar]);

  //.....
  RegisterClasses([TSpkLargeButton, TSpkSmallButton]);
  RegisterNoIcon([TSpkLargeButton, TSpkSmallButton]);

  RegisterClasses([TSpkPane]);
  RegisterNoIcon([TSpkPane]);

  RegisterClasses([TSpkTab]);
  RegisterNoIcon([TSpkTab]);

  //.....
  RegisterComponentEditor(TSpkToolbar, TSpkToolbarEditor);
  RegisterPropertyEditor(TypeInfo(TSpkToolbarAppearance), TSpkToolbar,
                         'Appearance', TSpkToolbarAppearanceEditor);

  //todo: register Caption Editor
end;             

[wp]

Here everything is fine, but when I update from the svn the component goes crazy. It looks as if my patch does not update all the necessary files in the repository.

It is strange, but the files missing have a mime-type "plain/text", instead of the usual "text/plain". All other files that I checked in my local repository have "text/plain", as well. Could it be that my TortoiseSVN refuses to consider different mime types for patching or updating? I changed their mime-type to text/plain, but I don't know if that helps.

Anyway, I'll give it another try. Find in the attachment two zip files: the first one contains the component and demo patches, the other one the full source of TSpkComponent - in case something would go wrong with the patches again.

BTW: Since nobody could have used the faulty component so far I took the freedom to change the declaration of the OnTabChanging event (adding an "Allow" parameter) because I need a way to inhibit changing tabs in certain cases.

[LuizAmérico]

Thanks. I'll look tomorrow night.

[LuizAmérico]

Applied with some modifications

[wp]

Tested the version from svn, it is running fine now. Thank you.

[JD]

Tested the version from svn, it is running fine now. Thank you.

Just tried the svn version & I'm sorry but it's not running fine at all! One still has to manually add the necessary pascal files to a project's unit clause before the project can be compiled.

I attach a demo project for your review.

Keep up the good work.

JD

[wp]

Maybe the expression "running fine" was too positive, I was referring to the issues with adding to svn. The issues mentioned in the first posting still exist.

As a workaround, just add a second SpkToolbar to the form (or any other component) and delete it again. You will have the missing units in the uses clause afterwards.

[JD]

As a workaround, just add a second SpkToolbar to the form (or any other component) and delete it again. You will have the missing units in the uses clause afterwards.

You're right. Adding a second SpkToolbar to the form and then deleting it effectively adds the missing unit clauses. Funny! 

[LuizAmérico]

I fixed the problem of the unit clause in svn, the missing references i could not fix