32 replies to this topic

[Bas]

Hi,

I have created an inspector with 3 TNxToolbarItems. Each TNxToolbarItem has a child, a TNxComboboxItem.

For the example lets say the Lines property of these comboboxes if filled with 1, 2, 3, a number for each line. Also, the style property is set to cbDropDownList.

Itemindex for the first box is set to 0, second box is set to 1, third box is set to 2. So they would list 1, 2 and 3 respectively.

Run the project.

Click, but do not select a different value, on the first comboxbox.
Repeat this for the second and third comboboxes.

You are left with 1, 1 and 1 in each combobox. Upon leaving the second and third combox, the selected item is reset to itemindex = 0.

Please please please fix this as soon as possible!

I make extensive use of TNxCombobox, and the way it is working now I can not present it.

Thanks!

[Bas]

Hi,

I have created an inspector with 3 TNxToolbarItems. Each TNxToolbarItem has a child, a TNxComboboxItem.

For the example lets say the Lines property of these comboboxes if filled with 1, 2, 3, a number for each line. Also, the style property is set to cbDropDownList.

Itemindex for the first box is set to 0, second box is set to 1, third box is set to 2. So they would list 1, 2 and 3 respectively.

Run the project.

Click, but do not select a different value, on the first comboxbox.
Repeat this for the second and third comboboxes.

You are left with 1, 1 and 1 in each combobox. Upon leaving the second and third combox, the selected item is reset to itemindex = 0.

Please please please fix this as soon as possible!

I make extensive use of TNxCombobox, and the way it is working now I can not present it.

Thanks!

Also, try assigning the OnEdit event of the inspector. For my example I've put a ShowMessage('I am being edited!'); in there. When the program is run and a TNxComboboxItem is clicked (but not changed) I get the following:

First combobox:
1 Popup

Second combobox:
2 Popups

Third combobox:
3 Popups

If after the third combobox another (like the 1st, or 2nd) is clicked, the OnEdit event is not fired anymore when the component is clicked, which is the way it should be in the first place.

[Boki (Berg)]

Hello,

Thank you for your report. I will review it and fix a problems.

regards

[Bas]

Hello,

Thank you for your report. I will review it and fix a problems.

regards

Nice, thanks Boki.

[Bas]

Hi, were you able to reproduce or maybe fix this?

[lesnes]

Hello,

I am having the same problem and it is causing me to delay a new release of my dbPortal product. Please fix this and release it ASAP.

Thanks.

[Bas]

I am now forced to delay my project as well until this is fixed. Could this issue be moved up in the list of priorities?

If this is not fixed in a couple of days I will be forced to use another control, and I dont want to do that. NextInspector is a way better solution if it would function normally.

Is it advisable to use NextInspector 4.0 instead, eventhough it is still beta?

Please let us now what the status is on this.

[Boki (Berg)]

Hello,

We have fix it. Please visit tomorow users area (about 20h CET) for update.

best regards

[Bas]

Hi Boki,

I see in the users area that the nextsuite.exe file has not been updated in 3 days. Is the fixed NextInspector not uploaded yet?

Do you know when we can download it?

Many thanks.

[Boki (Berg)]

Hello Bas,

Yes it is. Use this file.

regards

[Bas]

I downloaded the new file, but the build of NxColumns fails on line 1223:

CODE

 FEditor.Margin := 1;

with undeclared indentifier: Margin. Actually there is only a property Margins, which is read only.

The build also fails in NxDBInspector on line 106:

CODE

UpdateFields(FProperties.Categories);

with undeclared identifier Categories.

After this there are more, so I stopped the build. Can this be corrected?

[Boki (Berg)]

Hello,

Change Margin with Margins.Left and

UpdateItems to:

CODE

procedure TItemDataLink.UpdateItems;

var

 i: Integer;

begin

 with FOwner do Include(FPropertiesState, psUpdating);

 for i := 0 to FOwner.Items.Count - 1 do

   with Fowner.Items[i] do

   begin

     if DataSet.FieldDefs.IndexOf(FieldName) > -1 then

     begin

       case DataSet.FieldByName(FieldName).DataType of

         ftString, ftMemo, ftWideString: AsString := DataSet.FieldByName(FieldName).AsString;

         ftInteger, ftWord, ftSmallint, ftAutoInc, ftLargeint: AsInteger := DataSet.FieldByName(FieldName).AsInteger;

         ftFloat, ftCurrency: AsFloat := DataSet.FieldByName(FieldName).AsFloat;

         ftBoolean: AsBoolean := DataSet.FieldByName(FieldName).AsBoolean;

         else AsString := DataSet.FieldByName(FieldName).AsString;

       end;

     end;

   end;

 with FOwner do Exclude(FPropertiesState, psUpdating);

end;

regards

[Bas]

I have changed the Margin to Margins.Left, so that is fine.

The code you posted for procedure TItemDataLink.UpdateItems does not compile since most variables are not declared in the unit.

Besides this unit there is also NxInspectorReg on line 206:

CODE

 Result := '(' + TNextInspector(GetComponent(0)).Categories.ClassName +  ')';

with an undeclared identifier for Categories. After remarking out the two errornous methods everything compiles/builds ok.

One thing I have not even mentioned yet is the internal compiler error upon building NxCommonRun.bpl (Delphi 2005):

CODE

[Hint] NxEdit.pas(3174): H2077 Value assigned to 't' never used

[Hint] NxEdit.pas(3173): H2077 Value assigned to 'CanInc' never used

[Hint] NxEdit.pas(3170): H2164 Variable 'Hour' is declared but never used in 'TNxTimeEdit.GetValidText'

[Hint] NxEdit.pas(3170): H2164 Variable 'Min' is declared but never used in 'TNxTimeEdit.GetValidText'

[Hint] NxEdit.pas(3170): H2164 Variable 'Sec' is declared but never used in 'TNxTimeEdit.GetValidText'

[Hint] NxEdit.pas(3443): H2164 Variable 'd' is declared but never used in 'TNxCalcEdit.AddNumber'

[Fatal Error] F2084 Internal Error: LA33

However, it does compile so I left it as that. The 3.5 version did not have this btw.

[Bas]

Hi Boki,

Any progress? I am really getting close to my deadline now, so even if you have temporary fixes or code that I can replace, please let me know.

[Bas]

Any news on this? I am not able to compile the latest version as it is. Or has the file for download been updated with the fix perhaps?

[Boki (Berg)]

Hello,

This is fixed few days ago. Please log in into users area and download new file.

regards

[Bas]

Ok. I installed the new version and the combobox changing values is now fixed hurrah =)

But the OnEdit event is still being fired when I select a combobox though..

[Markus]

This is fixed few days ago. Please log in into users area and download new file.

I don't think it's a good idea to "re-pack" different versions in the same file. Different versions/revisions should be transparent to the customers. Especially for users like me who are using a version control system and run their modified (customized) Berg components.

[Bas]

Boki,

What is up with the OnEdit bug that I initially posted on April 26th?

I have to say I am dissapointed in the support that has been offered so far. I had to wait quite awhile before 1 of these 2 bugs was fixed (TNxCombobox changing itself), then it was fixed but the package put online did not compile, then the package was updated with out any notification and I had to read it from your reply in this thread that a new version was online.

Now, more than 1 month later, the second bug (OnEdit event being fired while it is not supposed to) is still not fixed, nor a workarround provided.

Being a paying customer you can understand that I am not satisfied with this kind of support. As posted by other users, Forum posts should always be replied too, and at least with in a day or two. This is not being demanding, your competitors in the field of custom Delphi components are able to do this.

Please take this post as constructive critisism. And I would still very much like to have a fix.

Maybe it would be a good idea to host a "bug squashing" week at Berg once in awhile. This is not uncommon.. and seeing the number of posts in this forum related to "wierd" things happening not only in TNextInspector but also other components it would be a good idea to do so.

I sincerely hope future releases will be more stable because Berg does have some credibility to win back, at least in my book.

[Markus]

Exactly. Take a look at my (bug report) posts. One out of 10 gets a reply, although I'm providing a fix, stack trace, detailed information, ... for most of my requests.

I'm spending my time to increase the quality of Boki's components that obviously makes him sell more licenses in the long term.

I think every other commercial component developer would love to have such customers as there are in this forum. Therefore I think we, the Berg Soft customers, deserve better support than the current.