Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify setting to close GE #35

Open
mast-eu opened this issue Sep 18, 2019 · 9 comments
Open

Modify setting to close GE #35

mast-eu opened this issue Sep 18, 2019 · 9 comments
Labels
area: plugin type: feature New feature or request
Milestone

Comments

@mast-eu
Copy link
Member

mast-eu commented Sep 18, 2019

There's a setting to close GE as soon as PM is started:
image

IMHO, it is valid to have an option to avoid this popup when a user installs a plugin:
image

However, the current implementation seems a bit "exaggerated". It always shuts down GE straight away when PM is started, even if the user doesn't install any plugin. Maybe I just clicked the plugin by accident....

I propose to change this into something like "Automatically close Git Extensions when installing plugins (don't ask for confirmation)". The default value should remain false.

@mast-eu mast-eu added type: feature New feature or request area: plugin labels Sep 18, 2019
@mast-eu mast-eu added this to the Backlog milestone Sep 18, 2019
@RussKie
Copy link
Member

RussKie commented Sep 19, 2019

I propose to reword to: Automatically close Git Extensions when installing plugins.
I would also suggest to make the setting or the value visible on the UI somehow (e.g. as a status message). Or confirm with a user whether the user wishes to close all GE instances once plugins are installed/updated.

A really cool thing to do - would to restart all GE instances as they were.
We could enumerate available processes and relaunch GE with the same settings. This of course isn't 100% reliable, if a user opened GE with one repo and then switched to another, the start parameters will have the first repo info.

Slightly OT - the setting looks ugly. Its placement looks somewhat random, the text is misaligned with the checkbox.
And the checkbox is to the right of the text, contrary to all other checkbox settings:
image

@ghost
Copy link

ghost commented Oct 23, 2020

How do I find these settings?

image

@RussKie
Copy link
Member

RussKie commented Oct 23, 2020

How do I find these settings?

Which one, sorry?

@ghost
Copy link

ghost commented Oct 23, 2020

image

@RussKie
Copy link
Member

RussKie commented Oct 23, 2020

The list on the left is build dynamically from the PluginRegistry (I think).
The one of the right - no idea :) I don't have access to the source right now.

@ghost
Copy link

ghost commented Oct 23, 2020

Plugin manager is installed. But there are no settings.

@maraf
Copy link
Member

maraf commented Oct 23, 2020

I can confirm the settings disappeared for Plugin Manager.

@maraf
Copy link
Member

maraf commented Oct 23, 2020

Now I remenber, in Git Extensions v3.3.1 added protected ctor with bool hasSettings. We are not using it in Plugin Manager yet.

@ghost ghost mentioned this issue Oct 24, 2020
@mast-eu
Copy link
Member Author

mast-eu commented Oct 29, 2020

in Git Extensions v3.3.1 added protected ctor with bool hasSettings. We are not using it in Plugin Manager yet.

For future reference: This has been added in #43. The PR is merged into master, but not yet included in a release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: plugin type: feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants