Fabien Devaux

> I'll when I can, unless there is a way to run it non interactively and still collect what is needed. I didn't use it a lot and not sure...

> > It's never crashing when I run in valgrind... > > That's not unexpected. Is it at least logging some memory access errors? I didn't check, just hitting ^C...

It's so fast to start, with an auto restart I can ignore it... :D I noticed sometimes the crash is helpful: when I start gBar with the session, very often...

OK, I'll look at it. gBar is already started by my compositor... but on the fastest machine I have, bluetooth is "often" (didn't make stats) missing initially.... while this doesn't...

I don't see any difference / improvement.

Actually I'm thinking, this can be useful in some scenarios, to have the mouse / focus locked on the current monitor. Do you think it would make sense to have...

I am using dynamic layouts depending on which other screen I plug. Even if I set positions later with `wlr-randr` the issue is the same. In short I can't use...

For instance: ``` Monitor eDP-1 (ID 0): [email protected] at 0x0 description: BOE 0x0A81 (eDP-1) make: BOE model: 0x0A81 serial: active workspace: 3 (3) special workspace: 0 () reserved: 0 50...

You nailed it, the scaling factor seems to be missing somewhere and with this it behaves as expected. Fun fact: restoring the old values just keeps the correct behavior

> is this stilla thing? I'm pretty sure scaling works as expected in multi monitor now. I recall performing some tests with success.