Unicode Bug in v9.10

[moelski]

Hi Roman,

in D2010 I got a strange view if I use nrHID and nrDeviceBox.

Just place nrHid and nrDeviceBox to a form.
Assign devicebox to nrHid.
Set nrHid to "EnumFullMode".

sometimes I got the result as in the 2 pictures.

And another question about the names in the device box ...
If enumfullmode is off I got (for example):
Logitech HID-compliant G3/MX518 Optical Mouse
If enumfullmode is on I got:
USB-PS/2 Optical Mouse

So in EnumFullmode the information is less than in normal mode  ???

Greetz Dominik

[Roman Novgorodov]

Hello

Thank you for information.

We will check problem with Unicode string and fix it asap.

About EnumFullmode.
When this mode is true, TnrHid component requests string descriptors from HID device directly. "USB-PS/2 Optical Mouse" is returned by device chipset.
When EnumFullmode mode is false, component uses string description that are provided by installed device driver. "Logitech HID-compliant G3/MX518 Optical Mouse" is string description from driver file (.INF).

Roman Novgorodov
DeepSoftware.Com

[moelski]

Hi Roman,

We will check problem with Unicode string and fix it asap.

Could you find the problem?
And is there an estimated release date for 9.12?

Greetz Dominik

[Roman Novgorodov]

Hello Dominik

We tested library on RAD 2010 and RAD XE with all available HID devices.
Unfortunately we can not reproduce trouble with wrong chars.
Please give more information about your HID device and step description how do you get different situations on the pictures.

It is not UNICODE problem because first 5 devices are visible correctly. It is problem in device that returns string descriptors non correctly. Or problem is in device driver.

Roman Novgorodov
DeepSoftware.Com

[moelski]

Hi Roman,

after some advanced searching I found the problem ...

I have a bluetooth mouse. But this mouse is actually not connected to my computer.
In the device box I got two HID devices for this not connected mouse  :o

After deleting the Bluetooth pairing all is fine now.

It seems that the mouse has a really buggy driver or it´s a fault of my bluetooth stack ...

Greetz Dominik

Sorry for the false warning.