kkotyk

I just wonder if we can write our own method of ascontiguous which can reshuffle an array slice directly onto the gpu by using cudamemcpy on the contiguous sections. Or...

Yes, I've looked at the internal Qtile code and it would be so much easier if the Screen() could take in an EDID to match off. Hell, it would be...

I would maybe start with a simpler, but more tedious way of just manually specifying x,y. I'd be perfectly happy using xrandr to initially figure out my layouts, but then...

```python @dataclass class Monitor: edid: str resolution: str rate: str = "60.00" position: str = "0x0" #widgets: List[widget] is_primary: bool = False output: str = field(init=False) #screen: Screen = field(init=False)...

The reason I did EDID is because I believe any information I should need for monitor management should be easily found from `xrandr --prop`. EDID is kinda gross, but at...

I'm fine with either way, and you are more involved with this project so you know what people need. We will just need to document a standard way of being...

```python class Screen(CommandObject): r""" A physical screen, and its associated paraphernalia. Define a screen with a given set of :class:`Bar`\s of a specific geometry. Also, ``x``, ``y``, ``width``, and ``height``...

> > we could instead loop over qtile screens first and if the new fields are set then we can use your x11 code to manage screens or do a...

I will slowly pick away at it. Thanks.

Can this be prototyped in python first? The python tools I started would make this way easier to start with since they can basically write any python dictionary to dmap.