@grokys not sure how to describe this issue if found... heres a screen recording
it looks like if I use a control with opacity < 1
and maximize and restore over and over again
some kind of translation matrix keeps getting added.
in the screen recording the only difference between icons that don't move and the ones that do is opacity.
my screen scaling is at 125% I think this probably doesn't happen with 100% screen scaling, will just check
yes screen scaling 100% and you don't see the issue
you aren't using rdp to connect to a remove machine where you're testing, are you?
haha weird! what backend?
you can repro on control catalog on the button page too
direct2d
and skia seem to be affected
to repro
1) adjust screen scaling to 125%
ok cool - that'll be easier to diagnose if you can do it in ControlCatalog
could you add an issue? it'll get lost here
sure
#1142 :)
@grokys @kekekeks can I ask you guys, what do you think about branches which have lots of "merge master into scenegraph" type commits, is this bad practise because it pollutes the commit history or is this a good thing because the branch is kept upstream?
they're pretty much inevitable for a long-running branch
for some branches you can rebase instead of merging but when a branch is longer running you're going to get merges
there are ways to remove them but i don't see any problem with them personally
this is the dilema I'm facing, basically rebasing is preffered but painful
and then merge is much easier
but pollutes history
good to know your thoughts on it :)
in what way do they pollute history? is it just that when looking at a list of commits you don't like seeing merge commits?
rebasing is preffered but painful
Rebasing destroys some information about the actual history
Since it will apply your diff to different base commit
While this information might like a noise to human
It's vital for tools like
git bisect