-
Notifications
You must be signed in to change notification settings - Fork 0
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
Currently getting two slidebars when screen = s #3
Comments
Sorry this was a little inaccurate of a description because my desires have somewhat changed. I managed to hack around it with gears.timer.delayed_call() and setting the bar as a function for only when screen = 1. However this is not so clean, and ultimately I would like it to behave accordingly on all monitors regardless of the screen index. If you have any suggestions i'd be more excited to hear! Awesome work by the way, really digging it! |
I am sorry I think I need some more clarification. Do you only want one slidebar, and it should be on screen 1? If you are setting it up within Glad you like it. I have been working on a more general, flexible animation system which would actually really simplify having a sliding bar. |
Apologies for being unclear! I would ideally like all screens to have their own slidebar available. What ends up happening for me at the moment is that when I by default have them for all, each bar tends to end up on 1 screen somewhere with strange offsets, instead of being at the designated position. I'll attach an image of a comment later in the day as an example of what I'm experiencing, together with a snippit of how i'm instantiating this script, if there's a straightforward solution that'd be awesome, but if not, then I'd be happy to wait for the more flexible animation system which may one day deprecate this :) A separate but potentially shorter request if you don't mind pointing me to a solution: I've been trying to add a connect_signal somewhere in your code, to start the 'show' event on a keybind's emitted_signal, so that when I press mod4 for example, the slidebar comes up, and goes down when mod4 is released. I can't find out where in the code to add this signal, because I can't understand the logic. I was initially thinking it might be at about relating to the connect_signals(o) function, but couldn't figure it out at any rate, I kind of added the signal everywhere and things just wouldn't work (likely that I just didn't understand the logic of the script). Any help in this would be greatly appreciated! |
Sorry for not responding sooner. Could you share the part of your code where you are instantiating the slidebar? That would really help! I I am going to try to replicate this anyhow with a second monitor. The way I wrote the show and hide logic was to cover a bunch of corner cases. Like instantly stopping the slide out if you move your mouse away. So it checks the position of the mouse. If you are OK with losing that 'feature' what you can do is remove lines Then, you can copy the logic for the activator |
I currently have two monitors, where i am trying to only have the slidebar active on one of them. I'm not able to bind the screen to anything besides s or nil, where nil presents only one the main screen (with tags and such that aren't representative of my screen 1), and s presents both slidebars on screen 1, 1 where i expect it, and the other with a slight offset. Is there some other parameter I should pass in to limit only the slidebar on screen 1?
The text was updated successfully, but these errors were encountered: