Page 1 of 1

keyboard shortcut customisation and mouse buttons setting

Posted: Thu Aug 24, 2017 3:38 pm
by flaenen
Hello,

I was wandering if there is a way to set custom keyboard shortcuts, to launch some Tools that we may use frequently.
Also, if the mouse could be adapted a bit. For example, if we can choose with which button we do the rotation (left, middle or right), and which button triggers translation...

Thank you

Re: keyboard shortcut customisation and mouse buttons setting

Posted: Thu Aug 24, 2017 3:46 pm
by flaenen
Sorry, to precise a bit my question : when I talk about rotation and translation, I mean rotation and translation of the camera, not the models.

Re: keyboard shortcut customisation and mouse buttons setting

Posted: Thu Aug 24, 2017 8:57 pm
by daniel
1) Nope, it's not possible to define custom shortcuts (and it wouldn't be very easy to implement, so I don't think it will be possible in a near future)

2) It's maybe a little bit easier, however there's not a big emergency for this feature so I'll simply add it to the TODO list (which is already huge: see https://github.com/CloudCompare/CloudCo ... C/TODO.txt)

Re: keyboard shortcut customisation and mouse buttons setting

Posted: Sun May 17, 2020 12:32 pm
by sylloge
I understand custom shortcuts won't happen

the menu item I'd like has a tool tip but I can't find the icon
all my toolbars are on

qCC/ui_templates/mainWindow.ui

<action name="actionExportCloudInfo">
<property name="text">
<string>Export cloud info</string>
</property>
<property name="toolTip">
<string>Export cloud info to a CSV file (name, size, barycenter, scalar fields info, etc.)</string>
</property>
</action>

Or, is it a simple change to edit some config files to add a shortcut and rebuild the windows source for myself
I dabble in python a little

Regards

Re: keyboard shortcut customisation and mouse buttons setting

Posted: Thu May 21, 2020 6:52 am
by daniel
You can indeed use Qt Designer, select the action and assign a shortcut to it (hopefully one that has not been used so far).

And then recompile CC. Or make a PR so that it's integrated in the code base and included in the next release.