8 replies to this topic

[array81]

I use a NextInspector, on this I have a item added on design-time called "customers".

On run-time I add subitems to this "customers" item with this code:

 

      for i := 1 to 10 do

        begin

          itemCustomers.AddChild(TNxCheckBoxItem, 'Customer' + IntToStr(i));

        end;

 

Now I need understand how the user change check status of itemCustomers childs.

 

I have try with this code:

 

  if itemCustomers.Items.IndexOf(Item) > 0 then

    begin

      // my code

    end;

 

both on Edit and Change event of NextInspector but it doen't work.

 

Any idea?

 

Thanks

 

[Boki (Berg)]

Hi,

 

OnChange event should work fine. If you can send me mini-demo I can see where it stops (and why it won't trigger in your case).

 

You can also use OnToolButtonClick event of Item too.

[array81]

If I use the code inside OnChange I have 2 problems:

1. The code is call for all item and not only for itemCustomers childs.

2 The code is call also on form creation when I put default value to NextInspector items.

[array81]

A have create a small demo.

As you can see when the form is create you show message about "client changed" besides you can see the same message if you edit any items of NextInspector.

 

I have add also 3 button to report another problem, this time with TNxButton, as you can see if I sett ShowArrow the caption (and the image) is not centered. I think in this case you must move caption and image on leftto try to avoid the arrow.

Attached Files

•  bergexample.zip   2.75KB   4 downloads

[array81]

I have attached the demo application! See preview message.

[Boki (Berg)]

Hi, 

 

Sorry for delay,

 

I will work on it today.

[Boki (Berg)]

Hi,

 

Sorry again for delay,

 

I have altered your sample bellow.

 

CheckBox item include event from ToolbarItem. I didn't liked this for v6 so I added OnCheck event for CheckBox item only.

 

unit Unit1;
 
interface
 
uses
  Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
  Vcl.Controls, Vcl.Forms, Vcl.Dialogs, NxPropertyItemClasses, NxPropertyItems,
  NxScrollControl, NxInspector, NxCollection;
 
type
  TForm1 = class(TForm)
    insExample: TNextInspector;
    insMainItemGeneral: TNxToolbarItem;
    insItemGeneralTitle: TNxTextItem;
    insItemGeneralType: TNxComboBoxItem;
    insItemGeneralDate: TNxDateItem;
    insMainItemClients: TNxToolbarItem;
    btnPoligoni: TNxButton;
    NxButton1: TNxButton;
    NxButton2: TNxButton;
    procedure FormCreate(Sender: TObject);
    procedure insExampleChange(Sender: TObject; Item: TNxPropertyItem;
      Value: WideString);
    procedure DoToolButtonClick(Sender: TNxPropertyItem; ButtonIndex: Integer);
 
  private
    { Private declarations }
  public
    { Public declarations }
  end;
 
var
  Form1: TForm1;
 
implementation
 
{$R *.dfm}
 
procedure TForm1.DoToolButtonClick(Sender: TNxPropertyItem; ButtonIndex: Integer);
begin
  ShowMessage('checkbox click');
end;
 
procedure TForm1.FormCreate(Sender: TObject);
var
  i: Integer;
  Child: TNxPropertyItem;
begin
  for i := 1 to 5 do
    begin
      Child := insMainItemClients.AddChild(TNxCheckBoxItem, 'Client' + IntToStr(i));
      TNxToolbarItem(Child).OnToolButtonClick := DoToolButtonClick;
    end;
end;
 
procedure TForm1.insExampleChange(Sender: TObject; Item: TNxPropertyItem;
  Value: WideString);
begin
  if insMainItemClients.Items.IndexOf(Item) > 0 then
    begin
      ShowMessage('Client item changed!');
    end;
end;
 
end.

[array81]

Thanks, It's work.

Please fix also image button bug (see my demo) in next version.

 

I'd like know your position about v5 version of your components.

V5 will still be developed or your will devote only to v6?

In this second case (which it is understandable) you think to add all component of v5 to v6 and release a tool to help migration from v5 to v6?

[Boki (Berg)]

Hi,

I am continuing to support v5 as long there are users. This include bug fixes and smaller features that can be easily moved into v5 from v6.

But I hope that more and more there will be v6 users since the code is much more easier to maintain and expand. I think that things are moving slowly into right direction. Soon I will publish new Users Area so downloading different versions will be easier.