Deleted user

Results 141983 comments of Deleted user

the point of the issue was to allow size persistence between application launches via disabling the maximize hint, just because you don't want to have all windows remembering their floating...

And this is where I'll take my leave, if you want to contribute towards your opinion then submit a merge request

well your "approach" is wrong, this video demonstrates size hints being disabled while both dolphin and firefox don't remember their size https://github.com/user-attachments/assets/aca3984b-2909-4428-9b10-24888c24536e

meanwhile my approach, firefox scales correctly, and size persistence works on both firefox and dolphin https://github.com/user-attachments/assets/19f84aa2-ea7a-4f93-bcc4-a9f5b3468a6a

all I did was remove the part where the maximization event was sent, nothing more, nothing less. anyways both of the videos show that not sending the hint is not...

windows spawn tiled for a reason, this is a "tiling window manager (wayland compositor)", also if the window is spawned floating it doesn't work either (probably)

PPS: It seems like remarkable uses some sort of smoothing on the strokes. A moving average (window size=5) on the stroke points comes close to their result.

PPPS: I'm using the lastest main of `rmscene` here

Hi sanasz91mdev! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use...

@david-freistrom After reading through your issue, one possible cause is that GCP Artifact Registry is not fully OCI 1.1 compliant.