[TC 11.00b7] Inconsistency in changing drives (forward and backward) using cm_OpenDriveByIndex

[Fla$her]

We consider random keystrokes. For example, instead of Ctrl+7 (cm_OpenDriveByIndex 7) to press 7 buttons on the drive panel, I accidentally (with an incorrect calculation) press Ctrl+8 (cm_OpenDriveByIndex 8). As a result, a list of wfx plugins (cm_OpenNetwork) opens.

I don't want a random key or button press to change the list in the panel to a non-drive one.

There is no such problem for cm_OpenDriveByIndex with negative parameters -1...-100, since the transition is carried out only for drives.

It is expected that this will not happen with positive 1-100.

For negative ones -101-... is provided for pressing all buttons. It is logical to provide the same for positive 101+.

[Sir_SiLvA]

Yes cm_OpenDriveByIndex -1 not openening the Network Neighborhood is a BUG

I would expect cm_OpenDriveByIndex -1 to open the most left item displayed on the drive button bar/last item of the drive drop down list.

[Fla$her]

Yes cm_OpenDriveByIndex -1 not openening the Network Neighborhood is a BUG

This is not a bug, but a stated behavior:

Numbers below -100 count from the last button, so -101 would be the last button, -102 the second-last etc.
Numbers below -1 but above -100 count from the last drive letter

07.06.23 Added: cm_OpenDriveByIndex can now accept negative numbers below -100, where -101 would be the last button instead of the last drive (-1) (32/64)
06.06.23 Added: cm_OpenDriveByIndex can now accept negative numbers, where -1 would be the last drive (other buttons are ignored) (32/64)

And it does not apply to this topic.

[ghisler(Author)]

I don't consider this a bug, only an inconsistency with negative numbers. I will add it.

[Fla$her]

I will add it.

Thank you!

[Fla$her]

Done!

[white]

Moderator message from: white » 2023-06-21, 18:12 UTC

Moved to Fixed bugs.