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

Ideas for new default config #49

Closed
MasterP-theGu opened this issue Apr 14, 2020 · 1 comment
Closed

Ideas for new default config #49

MasterP-theGu opened this issue Apr 14, 2020 · 1 comment
Assignees
Labels
help wanted Development help required (see `difficulty:*`) skip:changelog Issue/PR should skip CHANGELOG type:enhancement Augmenting an existing feature type:question Question (most likely will convert to Discussion)

Comments

@MasterP-theGu
Copy link

My primary screen is the left one and having the RightPanel in the left margin has made a lot of sense to me for quite a while. So I thought, others whose primary screen is the left one might have similar feelings. And as fvwm3 might want to come with a new/updated standard config, I thought we could have a collection of ideas for this fvwm3-standard-config here. As I can only start this from a user perspective, I shall suggest results rather than ways / codes, but if you have code, I'm sure nobody will be disappointed with it being shared here.

Make standard panel LeftPanel
or have a switch in the config to choose between left or right margin
currently: *RightPanel: Geometry 120x$[vp.height]-0+0 v new *LeftPanel: Geometry 120x$[vp.height]+0+0
On a switch-level I could think of something like set panel = left
or, which could be discussed, have a general switch in a top-section of the config as to which screen is the main one and/or whether we have global or per-monitor configuration and have the position of the panel and possibly all kinds of other things depending on this, so something like
set primary screen = left -> panel=left v set primary screen = right -> panel = right

@ThomasAdam ThomasAdam added this to the post-1.0 milestone Apr 25, 2020
@ThomasAdam ThomasAdam added type:enhancement Augmenting an existing feature help wanted Development help required (see `difficulty:*`) type:question Question (most likely will convert to Discussion) labels Apr 25, 2020
@ThomasAdam ThomasAdam self-assigned this Apr 25, 2020
@ThomasAdam ThomasAdam added the skip:changelog Issue/PR should skip CHANGELOG label Jun 15, 2021
@ThomasAdam ThomasAdam removed this from the post-1.0 milestone Jun 15, 2021
@ThomasAdam
Copy link
Member

Hi,

Closing this as there's nothing else to do that can't be solved through editing the fvwm config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Development help required (see `difficulty:*`) skip:changelog Issue/PR should skip CHANGELOG type:enhancement Augmenting an existing feature type:question Question (most likely will convert to Discussion)
Projects
Status: Done
Development

No branches or pull requests

2 participants