Hacker News new | ask | show | jobs
by towolf 4783 days ago
You forgot to mention that the ARGB Visual type was working well enough for years, ever since xcompmgr was around, all trough compiz and GS.

And the GS → metacity → GS cycle was not crashy here at all. It worked.

And now you’re getting into Wayland territory. All the more reason to make sure that windows with alpha maps work.

You can keep the old code around in the meantime.

Also, making a poll in your 50 people IRC channel is not a very meaningful sample size is it?

2 comments

  | Also, making a poll in your 50 people IRC channel
  | is not a very meaningful sample size is it?
They just polled the IRC channel? Really? That just seems like the definition of a 'circle jerk.' Was the assumption that all or a majority of users technical enough to use the terminal would be in the IRC channel?
> Really?

No idea. That’s what I derive from "we had an informal poll". Since they hang out on IRC that is probably where it happened.

The old code didn't work after the port to GSettings. It crashed in weird places. That's why it was "#if 0"'d around in the GSettings port commit. As I said, the original intention was to fix it, but minds were changed.
> but minds were changed.

So what does it take to make the minds change back again?

When I stare at opaque terminals all day I get severely perceptually understimulated to the point that I fear becoming an automaton.

But with some sliding animations and a bit of flower poking through it soothes my nerves.

Is that not enough reason?

I can’t see how Gsettings has anything to do with opacity and the compositor.

Perhaps separating these things out in different commits would’ve been smarter to begin with.

With hindsight, yes, we'd love to do things differently. Saying "you should have done" doesn't really help the current situation here.

The gsettings port broke stuff and reintroduced problems. It was long overdue. This means that cutting features to get things out of the door might happen.

If I had to guess without debugging, I might guess that the 'changed' signals were firing at different times in comparison to when the slider was being adjusted that means that changing the background wasn't ordered 100% correct. The code stems back to 1996 -- it's possible that assumptions like these are being made.

I can’t see how Gsettings has anything to do with opacity and the compositor.

You are implying that because you don't know about the connection, there must not be one?

Perhaps separating these things out in different commits would’ve been smarter to begin with.

20/20 hindsight criticism from someone watching from the sidelines? Helpful.

Only looking for explanations. Really super grateful that Jasper_ added some, but it’s still not entirely clear.