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

EdgeResistance command not working? #285

Closed
JakeMoe opened this issue Nov 3, 2020 · 9 comments
Closed

EdgeResistance command not working? #285

JakeMoe opened this issue Nov 3, 2020 · 9 comments
Labels
type:bug Something's broken!

Comments

@JakeMoe
Copy link

JakeMoe commented Nov 3, 2020

Using my config from FVWM 2, I have a line "EdgeResistance 0" that doesn't seem to be working on FVWM 3; I can't move the mouse off the edge to the next page. FvwmPager and keyboard shortcuts using GotoPage let me move to them fine.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.87. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the type:bug Something's broken! label Nov 3, 2020
@ThomasAdam
Copy link
Member

Hi @JakeMoe

Works for me, I think. Can you attach your config to this issue, please?

@JakeMoe
Copy link
Author

JakeMoe commented Nov 4, 2020

Sure thing; it's attached. I was mainly checking that the option was still valid. I can do some further testing with a minimal config to see if anything else is interfering.

It's worth noting, I suppose, that I have 3 monitors; one on a laptop, one monitor connected via HDMI, and one via HDMI througha USB-C dock. Not sure if that would affect anything, but figured I'd mention it.

fvwmconfig.tar.gz

@JakeMoe
Copy link
Author

JakeMoe commented Nov 4, 2020

I went with a minimum config, and still had the issue.

DesktopSize     3x3
EdgeResistance  0
EdgeScroll      100

DestroyFunc StartFunction
AddToFunc StartFunction
+ I Module FvwmPager

*FvwmPager: Geometry 75x50-0-0

FvwmPager also only appears some of the time. Haven't opened a seperate ticket yet, figuring I'd tackle one issue at a time. But is there any chance I haven't selected a needed configure/compile option, and the binaries aren't quite right? I downloaded the code and just ran ./configure and make over it with no options, figuring I'd see if I needed more features later.

@JakeMoe
Copy link
Author

JakeMoe commented Nov 8, 2020

Just ran into something odd; I was dragging a window, and I accidentally went off the bottom of the page on to the next page with no resistance. Not sure if that's helpful or useful, but thought I'd add it here.

ThomasAdam added a commit that referenced this issue Nov 22, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Currently a WIP.

Helps with #285
@ThomasAdam
Copy link
Member

Hi @JakeMoe,

I haven't yet looked at why FvwmPager might not be opening all of the time (perhaps you should generate a separate issue for this?).

But in terms of EdgeResistance/EdgeScroll -- I think you're missing some values. I'm using this:

DesktopConfiguration per-monitor
DesktopSize     3x3
EdgeResistance  500 500
EdgeScroll      100 100

DestroyModuleConfig FvwmPager:*
*FvwmPager: Monitor $$[monitor.current]
FvwmPager

... and have been playing with getting EdgeScrolling to work across independent monitors. It's not perfect, but you can compile the code on ta/gh-285 if you wish to give it a go. This goes some way to addressing the observation you had about when moving windows around, you'd end up flipping pages. Please note that the code on ta/gh-285 is still buggy -- but keep your observations here about it, and I'll incorporate this in to my code.

@JakeMoe
Copy link
Author

JakeMoe commented Nov 25, 2020

Thanks for all your help, but unfortunately I no longer have access to the computer I was working on. I suppose I'll have to close this ticket at this time; when I get a new computer built and FVWM 3 working again, I'll reopen if I still have an issue.

@JakeMoe JakeMoe closed this as completed Nov 25, 2020
@ThomasAdam ThomasAdam reopened this Nov 25, 2020
ThomasAdam added a commit that referenced this issue Nov 28, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Currently a WIP.

Helps with #285
ThomasAdam added a commit that referenced this issue Nov 28, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Currently a WIP.

Helps with #285
ThomasAdam added a commit that referenced this issue Nov 28, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Currently a WIP.

Helps with #285
ThomasAdam added a commit that referenced this issue Nov 28, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Fixes #285
@ThomasAdam
Copy link
Member

Hi @JakeMoe

Fair enough. I'm leaving this here for a little bit, but I'm expecting this bug to be fixed via the ta/gh-285 branch.

ThomasAdam added a commit that referenced this issue Nov 29, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Fixes #285, #82
ThomasAdam added a commit that referenced this issue Nov 29, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Fixes #285, #82, #34
ThomasAdam added a commit that referenced this issue Nov 30, 2020
When `DesktopConfiguration per-monitor` is used, panframes need to be
enabled at monitor boundaries as well as outer edges.

Fixes #285, fixes #82, fixed #34
@JakeMoe
Copy link
Author

JakeMoe commented Oct 10, 2021

@ThomasAdam I've finally had a chance to look at this further on a new system (Arch now instead of Gentoo, with fvwm3 pulled in from AUR), and found I was having the same problem with the same config, even with the new patch you put in. Reading the man page a bit more, I wound up putting these three in to make it work:

EdgeResistance 0 0
EdgeScroll 100 100
EdgeThickness 1

It seems to need all three to work; do both EdgeScroll and EdgeThickness default to 0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something's broken!
Projects
None yet
Development

No branches or pull requests

2 participants