Giter VIP home page Giter VIP logo

katriawm's Introduction

katriawm's People

Contributors

vain avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

katriawm's Issues

Fullscreen in flashplugin broken on multihead setups

Just for the record, this is a known issue. Won't fix since Adobe Flash is non-free software and I rarely use it. When/if other software shows the same problems, I'll investigate further.

Here's what happens:

  • Suppose you watch a YouTube video using the Flash plugin in Firefox. Now you hit the plugin's "fullscreen" button.
  • Firefox creates a new window for the plugin.
  • The new window issues a ConfigureRequest before mapping the window. At that stage, we don't manage the window yet. Thus, we blindly acknowledge the request.
  • Next, the new window issues a MapRequest. We now evaluate EWMH hints and make the window fullscreen.
  • However, Flash ignores all changes to its window size. There's no way to resize the darn thing. It only uses those values of the reply to the very first ConfigureRequest.
  • If you have more than one screen, then the initial ConfigureRequest will use the geometry of the very first screen. Thus, your "fullscreen" Flash window will always have that size -- which might be too small or too large if the window is shown on another monitor.

By the way, this is broken in dwm, too.

Window moving and resizing really ugly with sxhkd >= 0.5.6

sxhkd 0.5.6 removed the ! prefix (baskerville/sxhkd@0759508). It is no longer possible to spawn processes on motion events. Instead, these events are always written to a UNIX socket.

This works fine with bspwm (sxhkd is developed by the same person who develops bspwm) because it listens on a UNIX socket to receive commands. katriawm does not do this. We expect IPC commands in X11 ClientMessages.

The only way to make katriawm work with sxhkd 0.5.6 is to use some kind of daemon that listens on a UNIX socket and translates those events into something katriawm understands. This is precisely NOT what I want to do.

I do understand the rationale behind sxhkd's change. But for us, it's very bad news.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.