mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #33] Unclickable menu #2904
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#2904
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Shooshka on GitHub (Dec 9, 2020).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/33
Originally assigned to: @VShawn on GitHub.
Click on "+" or use Alt+M --> RMB click on any of connections --> Cannot edit/duplicate/etc, any option unclickable in this menu.
@VShawn commented on GitHub (Dec 9, 2020):
sorry I don't get how to reproduce the bug?
I tried RMB click server card and it did goes into edit page and can edit options of it
@VShawn commented on GitHub (Dec 9, 2020):
did you mean RMB click launcher list item? It's not design for click,after alt+M try press keyboard right key😀
@Shooshka commented on GitHub (Dec 9, 2020):
Yep,
But if I can... I can! ;)
To be clear, I'm about this:
@VShawn commented on GitHub (Dec 9, 2020):
In fact in theverybeginning, i design luancher all actions called only by keyboard.
But it's ok to add some mouse event🤔, i will inform you when i upgrade this
anyway i will add more information in guidance
@VShawn commented on GitHub (Dec 9, 2020):
new release package fix this issue.