-
Notifications
You must be signed in to change notification settings - Fork 24
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
Visual Mode #24
Comments
Great Idea. |
Any word on this @neo1691? |
You also have the option of decreasing the brightness of the whole screen and only brighten the windows of those that are (being) selected, although I guess it's easier to change the border, and it actually makes more sense. |
@HarveyHunt I started working on this long back, implemented it partially, and then I got off completely. I don't even know how much is changed in the code base. I was telling you how to I was going to implement it.
Let me know what you think about it. You can implement it in less than 30 minutes I believe. Let me know if the above make sense or not. I don't think I will be able to implement it in time. So yo go ahead and finish it off. |
@vimeitor I think that brightness is an issue for a compositor to deal with. @neo1691 Thanks for the big write up- you've reminded me of everything we have talked about. I am happy to finish visual mode. I am not sure if I will be able to use your branch though - it is one release behind (soon to be two once IPC is released) and many commits behind develop. I had a few more ideas:
Then pressing alt + q will kill the select items (workspace or client). Leaving visual mode will clear the selection. I think it should be easy to change the code in the op_* functions, I can imagine a macro such as SELECTED(x) where:
|
Sure, don't use my branch. It's too messed up. You will be faster if you Cheers. |
It might be a nice idea to have a mode whereby windows can be selected that an operation will then be performed upon.
The selected windows could have a different border colour to the unselected ones?
The text was updated successfully, but these errors were encountered: