Product, version and build: 5.2.124
32 or 64 bit version of product: 64
Operating system: win 10
32 or 64 bit OS: 64
The hotkey for Rename (Ctrl+Shift J) doesn't work, nothing happens.
Rename hotkey (shift-ctrl-J) doesn't work
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Re: Rename hotkey (shift-ctrl-J) doesn't work
Turns out it is Ctrl-Alt-J as listed in Keyboard Shortcuts.pdf, the menu is incorrectly listing Ctrl-Shift-J
- juneblender
- Posts: 93
- Last visit: Thu Mar 30, 2017 8:54 am
Re: Rename hotkey (shift-ctrl-J) doesn't work
Thanks! I've filed an internal bug to fix this. Sorry for any inconvenience.
-- juneb
June Blender
Technology Evangelist
SAPIEN Technologies, Inc.
-- juneb
June Blender
Technology Evangelist
SAPIEN Technologies, Inc.
Re: Rename hotkey (shift-ctrl-J) doesn't work
No worries, nice to see that support is very pro-active!
Is there a bug hunter trophy?
Is there a bug hunter trophy?
- juneblender
- Posts: 93
- Last visit: Thu Mar 30, 2017 8:54 am
Re: Rename hotkey (shift-ctrl-J) doesn't work
LOL! If there was a bug hunter trophy, I'd have so many they'd fill my office. Bugs hunt me down.
I have some cool PowerShell Studio stickers/pens if you'd like some. Email me at juneb at SAPIEN.
And, we really do appreciate the bug report. That bug is already fixed and ready for the next service release.
I have some cool PowerShell Studio stickers/pens if you'd like some. Email me at juneb at SAPIEN.
And, we really do appreciate the bug report. That bug is already fixed and ready for the next service release.