mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #144] Bulk connect window options #2039
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#2039
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 @BrommD on GitHub (Jul 14, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/144
Originally assigned to: @VShawn on GitHub.
Is your feature request related to a problem? Please describe.
in #107 the option was removed to open connection grouped in own window automatically. Now with "tags" I can open all connection belonging to a tag , but they all are placed in same existing windows (where the handling of such overloaded "tab" windows is quite cumbersome). This is not very comfortable to former version. Rather having 10 windows open with 3-4 grouped connection, than one window with 30-40 tabbed connection.
Describe the solution you'd like
Have the possibility to open tagged connection "grouped" into own window (again), in case there are more tags assigned per connection, this option is disabled (as it does not make sense for application to guess to which window to place the new connection), so this will also work using implementation #107.
Describe alternatives you've considered
detaching and moving opened connection (from same group/ag) from main window to separate one, so having multiple windows with their own dedicated connections (i.e. "systems" or "mandator")
Additional context
Add any other context or screenshots about the feature request here.
@majkinetor commented on GitHub (Jul 15, 2021):
Since you can use multiple tags, nothing stops you from creating N groups of connections and multi connect to specific group using its tag.
Regarding new/existing window, that is a feature request that is as I see it only possible if you have another option. Now we have button Connect, and we could have button Connect using single window, Connect using multiple windows.
@BrommD commented on GitHub (Jul 15, 2021):
Right, the upper part (tagging, whatever required) is just fine, only the removed option "open in new windows" is missing here.... I would prefer to have sth default for connection profiles, like this was able in "grouped" feature in old version, but I can also live with "tag/open in new window" processing
thx, Dejan
@majkinetor commented on GitHub (Jul 15, 2021):
OK, so we could have something like this:
[Connect v] button with submenu. Connect itself triggers default action and both actions are available via drop down menu.:
Default action for top level Connect is set in the configuration
So default would be as it is now (single window) and if you check that option in global configuration it would become multiple windows by default, but one would still have an option to ad hoc choose both options (as it seems to me this use case is situational).
This is trivial to implement, looks useful, and resolves all the problems you have.
@BrommD commented on GitHub (Jul 15, 2021):
SOLD! :)
@VShawn commented on GitHub (Jul 17, 2021):
What about an option
Connect to new windowto let user choose where the new connection should be placed.By this option, a new tab window will created and the new connection (sigle connection by click single session / all connections open by a tag) will be placed in this new window.
We don't need a configuration to setup the
Default action for top level Connect is set in the configuration@majkinetor commented on GitHub (Jul 17, 2021):
Sounds good
@BrommD commented on GitHub (Jul 19, 2021):
Hi, if it does not create much effort, a configuration possibility would be great. Thx, Dejan
@majkinetor commented on GitHub (Jul 19, 2021):
I initially proposed that because with only 2 explicit options, you need to always choose, so each bulk connect is extra mind step. So if you connect to same window 90% of the time, it is more efficient to set default to 'same window' and then override that default when you need it in ad hoc manner.
@BrommD commented on GitHub (Dec 22, 2021):
Hi
just want to add here, that the possibility to open a windows quickly in same or in new windows without using the mouse (press hotkey, type/search, chose profile, cursor-right, chose "new windows" or not) is simply great.
thanks for making this possible.
Dejan
@VShawn commented on GitHub (Dec 23, 2021):
@BrommD
session open from Alt + M will be opened in same window or new window, did this not work for you?
@BrommD commented on GitHub (Dec 23, 2021):
hi, sry, I was not accurate enough. I want to say thx for exactly having implemented such an option. This works great.
Regards, Dejan
Von: VShawn @.>
Gesendet: Donnerstag, 23. Dezember 2021 01:48
An: VShawn/PRemoteM @.>
Cc: Bromm, Dejan @.>; Mention @.>
Betreff: Re: [VShawn/PRemoteM] Bulk connect window options (#144)
that the possibility to open a windows quickly in same or in new windows without using the mouse
@BrommDhttps://protection.retarus.com/v1?u=https%3A%2F%2Fgithub.com%2FBrommD&c=3ilYjgr&r=5In0snLjkrlk42h66QEkX3&k=7s1&s=rcuUjx54e2mvHJlgIYGvZvsqTsadGWaYH88RTX6D9kF
session open from Alt + M will be opened in same window or new window, did this not work for you?
[image]https://protection.retarus.com/v1?u=https%3A%2F%2Fuser-images.githubusercontent.com%2F10143738%2F147171040-f53b6d93-6ec7-4bd1-b177-816abbfe5079.png&c=3ilYjgr&r=2sPlC8RAjVHX1XRpemFzRN&k=7s1&s=gTVMWckbrMGVrIiMKweTogKpshcYvhClBmxzXrmWcZm
—
Reply to this email directly, view it on GitHubhttps://protection.retarus.com/v1?u=https%3A%2F%2Fgithub.com%2FVShawn%2FPRemoteM%2Fissues%2F144%23issuecomment-999964699&c=3ilYjgr&r=2mkwkxS3HFhXVX4QGEUJJh&k=7s1&s=XdnsYty1pAhIdSAxTSPwCeNowCro9BqNv8TIxcEko6H, or unsubscribehttps://protection.retarus.com/v1?u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH672M7ER32W4CZJ36DQAWTUSJWTZANCNFSM5ALS3D2Q&c=3ilYjgr&r=2XaTMdQym4Eoms1maln68Y&k=7s1&s=2RoJhh5jVfUin54gDQxs5VcHIsxnRE4DB8ZQuUdwj6S.
You are receiving this because you were mentioned.Message ID: @.@.>>