2023-06-29, 05:42 PM
(This post was last modified: 2023-06-29, 05:45 PM by baltika_no_9.)
[quote pid="26558" dateline="1688056054"]
That doesn't look quite right, if you have 3 x matching devices then it lets you remember the first one by device ID. Shouldn't it stop you assigning any of them by device ID?
Thinking about it some more, this might be something we can't guard against. There's nothing to stop a user plugging in one device, remembering it by ID, and then plugging in a duplicate...
[/quote]
It makes sense to me, the first device is saved with vendor id = X, product id=Y , serial = 0.
Just because the Serial app can detect the other connected devices, Openplotter doesn't care unless I try to set them up. I might be using them in a different application. When I try to add the second one it says vendor id =X, product id = Y, serial = 0 - can't do that, I already have that one used. That way there will never be a conflict.
That doesn't look quite right, if you have 3 x matching devices then it lets you remember the first one by device ID. Shouldn't it stop you assigning any of them by device ID?
Thinking about it some more, this might be something we can't guard against. There's nothing to stop a user plugging in one device, remembering it by ID, and then plugging in a duplicate...
[/quote]
It makes sense to me, the first device is saved with vendor id = X, product id=Y , serial = 0.
Just because the Serial app can detect the other connected devices, Openplotter doesn't care unless I try to set them up. I might be using them in a different application. When I try to add the second one it says vendor id =X, product id = Y, serial = 0 - can't do that, I already have that one used. That way there will never be a conflict.