Btw I'm working now for a week non-stop on this damn templating of everything. That's why I'm maybe not so reactive with replies and reviews at the moment. It's kind of exhausting. But there is light at the end of the tunnel.
Sounds nice! 😄 Friend of me visited me on the weekend when travelling from Nordsee to Bayern. He was in Sweden with his van and girlfriend for a few days. He enjoyed it but on the photos it looked quite cold I have to say. At least a lot colder in comparison to how it is now in Berlin.
The last commit is still wip, but the other ones are ok.
Tom Englund: I was wondering if you're currently still working on rules stuff. You were looking into some fixes for that just recently, right? Because I may want to do kwinft/kwinft#241 now, which may create conflicts.
Roman Gilg: well i got that draft laying around waiting for some kind of virtual_desktop_manager integration struct or similiar but then got looped into debug_console thought of using it and appending a few useful things to actually debug or test things properly
Roman Gilg: so proceed on, il rebase with any conflicts 👍️
idea was to add one more tab for space properties aswell and fill in bunch of useful things heh but yeah noticed quite a lot was a bit off on it
il probably get more things going anyhow in ~1 week when the vacation days run out and the regular boring work, sleep, eat shedule begins again xD, so yeah dont worry. anything you work on that conflicts. il rebase! dont let me hold you up
Roman Gilg: i have a uh question tho, seeing you use enum_index in this MR aswell, 395518 in coverity has an odd error about it, ive tried various things in godbolt and locally and cant really tell why its complaining
either its false positive or its catching some oddball case :p
I see hmm. It's weird but I don't think it's a real issue. It somehow assumes that lay could be layer::count, which would be an issue as local layers variable only has 15 entries. Maybe accessing it with at would silence the warning.