22 replies to this topic

[John Taylor]

How do I get rid of the bell when moving from one Inspector item to another with the Tab or Enter key ?

Also, how can the Inspector be forced to focus the next editable item rather than categories that cannot
be changed by the user ?

thanks.
JT

[Boki (Berg)]

Hello Jt,

This is good idea, I will see what I can do about beep sound.

Best regards

[Thore]

Hello,

what happened to this issue? As I can see, the problem with the sound after tab press is still there.
Any suggestions?

Best Regards
Thore

[Boki (Berg)]

Hello Thore,

I will be like to get rid of this sound, but really have no idea why this happen.

I will take another look this weekend to solve this. Any tip is welcome

Best regards

[Gerry]

Dear Bojan,

Sorry to bother you again but attached to this post is sample code for getting rid of the really annoying bell when pressing (shift) tab.

Your humble servant,

Gerry

Attached Files

•  NxInspector_fix.pas   2.26KB   7 downloads

[Boki (Berg)]

Hello Gerry,

I will check it now. Thank you, I hope that we will get rid from this annoyance

Thank you again,

Best regards

[Boki (Berg)]

Hello Gerry,

Your code get rid of bell when using Tab key. Do you maybe know where to we put RemoveMessage to we get rid of bell when pressing Enter?

Thank you again

[Gerry]

Dear Boki,

I have the honor to be your most obedient humble servant
Attached is sample code to remove the bell when pressing VK_RETURN and VK_TAB

Kind regards,

Gerry

Attached Files

•  NxInspector_Fix.pas   3.02KB   10 downloads

[Boki (Berg)]

Hello Gerry,

Thank you Gerry, you have helped me a much! Both keys are not producing beeps no more.

Thank you again!

Best regards

[Gerry]

...and here, by special request of Mr. John Taylor, the patched FindNextItem and FindPrevItem methods for skipping read only items...

Attached Files

•  NxInspector_Fix2.pas   1.04KB   3 downloads

[Boki (Berg)]

Hello Gerry,

I have try to apply a change for FindNextItem/FindPrevItem, but with new code we have a problem that user can not move with keys above Category items.

When it comes to the Category Item it stuck on it.

Best regards

[Gerry]

The patched code works fine for me. Please send me a sample.

[Boki (Berg)]

Hello Gerry,

Just add a few categories and add some items in it. Category is ReadOnly by default and this is why this problem appear.

Just press Arrow Down/Arrow Up and you will notice that you can not "go" over a category item (top-level item).

Best regards

[Gerry]

This is really strange. I have tested it again and here it works fine.
Arrow keys up and down but also (shift) tab.
The read only top level items (TNxDBToolbarItems) are skipped.

Please post (or send me) a sample.

[Boki (Berg)]

Hello Gerry,

I will apply your code once again and send a demo to you.

Best regards

[Boki (Berg)]

Hello Gerry,

Please look in attachment for sample.

Play with arrows keys, and you will notice that you can never select top-level items.

Best regards

Attached Files

•  Project1.zip   257.21KB   1 downloads

[Gerry]

Your example works as expected, gray (top level) items are skipped.

John Taylor asked “how can the Inspector be forced to focus the next editable item rather than categories that cannot be changed by the user ?�. The way I understand it he wants all read only items to be skipped. This makes sense to me.

Why do you want to stop at those read only top level items?
To expand them using the +/- keys?

[Boki (Berg)]

Hello Gerry,

Why do you want to stop at those read only top level items?
To expand them using the +/- keys?

This is a one of reasons. I have check in Delphi, Object Inspector work in same way

Best regards

[Gerry]

Your right, I looked at the Delphi inspector and it stops at expandable items. But what about read only items that are NOT expandable (top level) items. Does it make sense to stop at those items?

[Boki (Berg)]

Hello Gerry,

Unfortunately, other "parent" items need to be processed in same way.

Solution may be to we have a property which will control this feature. But I think that this property will be one property enough.

Best regards