ppenguin

Results 63 comments of ppenguin

A very late but heartfelt thanks (I just stumled over this issue through an old reference, and noticed that I used this functionality without remembering any of this a few...

> this is working as well: > > ``` > >     >   const defaultConfig = { >   startOnLoad: true, >   securityLevel: 'loose', >   flowchart: { >   useMaxWidth: 0, >   },...

Using [this](https://stackoverflow.com/a/61983069/12771809) and [this](https://bazaar.launchpad.net/~arcachofo/simulide/1.0.1/files) I could download the most recent source tree with one `curl` command: ``` curl -SLo simulide.tgz "https://bazaar.launchpad.net/~arcachofo/simulide/1.0.1/tarball/1425" ``` I guess it should in theory be possible...

As a test and PoC I made a [`nix flake`](https://github.com/ppenguin/SimulIDE/tree/from-scratch-upstream-trunk-1723) that can build and run _almost directly_ (it needed some minor fixes) from the current upstream trunk, can be tested...

@bodograumann I'm exactly at the same point as you, and concluded indeed that the only "right" way to handle this is that the compositor (`qtile` in this case) reports the...

I started on a quick hack, with the objective to basically be able to define a `scale: int` as a parameter to `Screen()`, but got stuck on where it is...

@bodograumann I *think* the above mentioned `libqtile/backend/wayland/output.py::wlr_output.set_scale` is the equivalent of the `wlr_output_set_scale` used [here](https://github.com/swaywm/sway/blob/ee7668c1f2b5ba31420d972161d6d43fc1c84bb4/sway/config/output.c#L454), which is just the autoconfig value (`1` or `2` depending on "H-resolution" range) `sway` uses...

I have the same issue, I haven't experimented with any different settings for `eDP-1`, but when I execute `wdisplays` (I can still interact normally on the external monitor while `eDP-1`...

(I just noticed that the `bw/entrypoint.sh` suffers from the same issue. I.e. it can end up in an endless loop for an invalid pid file)

... but the "fix" for the BW entrypoint doesn't seem to do the right thing: from the `nginx` main processes POV it is ok, but the problem seems to be...