On 2019-04-15 23:38, Erwin Burema wrote:
On Mon, 15 Apr 2019 at 20:30, Sebastian Wick
wrote:
On 2019-04-14 12:57, Erwin Burema wrote:
> Without a way to calibrate/profile screens an color management
> protocol looses a lot of its value. So to add this missing feature I
> wrote the following pr
Simon Ser wrote:
I guess most people don't have a colorimeter at home.
Most people who are doing color critical work will have access to
a color measurement instrument, or will have some other method of
ensuring the consistency and availability of accurate display
characterization information (
On Mon, 15 Apr 2019 at 21:11, Simon Ser wrote:
>
> On Sunday, April 14, 2019 1:57 PM, Erwin Burema wrote:
> Thanks for your patch! Here are a few comments, mostly from a protocol
> perspective since I don't know about color management.
>
> > ---
> > .../cm_wayland_calibration.xml
On Mon, 15 Apr 2019 at 21:46, Simon Ser wrote:
>
> On Monday, April 15, 2019 10:42 PM, Sebastian Wick
> wrote:
> > > How would the client "measure"?
> >
> > With a colorimeter. Write some values that you expect to have a certain
> > color, read the actual colors, calculate the error.
> > I'm not
On Mon, 15 Apr 2019 at 20:30, Sebastian Wick
wrote:
>
> On 2019-04-14 12:57, Erwin Burema wrote:
> > Without a way to calibrate/profile screens an color management
> > protocol looses a lot of its value. So to add this missing feature I
> > wrote the following protocol.
> >
> > The idea is that th
Hi guys,
I got some very weird result while using transient window in weston.
Let's start from a simplest qt program:
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
MainWindow w;
w.show();
QDialog d1(&w)
d1.setWindowTitle("transient& non toplevel dialog d1");
On Monday, April 15, 2019 10:42 PM, Sebastian Wick
wrote:
> > How would the client "measure"?
>
> With a colorimeter. Write some values that you expect to have a certain
> color, read the actual colors, calculate the error.
> I'm not sure if that answers your question.
Sorry, I'm not familiar wi
On 2019-04-15 21:01, Simon Ser wrote:
On Monday, April 15, 2019 9:30 PM, Sebastian Wick
wrote:
On 2019-04-14 12:57, Erwin Burema wrote:
> Without a way to calibrate/profile screens an color management
> protocol looses a lot of its value. So to add this missing feature I
> wrote the following p
On Wednesday, April 3, 2019 4:00 PM, Samuel Thibault
wrote:
> Olivier Fourdan, le mer. 03 avril 2019 14:39:29 +0200, a ecrit:
>
> > > What we currently have in Wayland is support for AccessX, directly
> > > implemented in mutter. The rest of accessibility features are currently
> > > mostly broke
On Sunday, April 14, 2019 1:57 PM, Erwin Burema wrote:
Thanks for your patch! Here are a few comments, mostly from a protocol
perspective since I don't know about color management.
> ---
> .../cm_wayland_calibration.xml| 106 ++
> 1 file changed, 106 insertions(+)
On Monday, April 15, 2019 9:30 PM, Sebastian Wick
wrote:
> On 2019-04-14 12:57, Erwin Burema wrote:
> > Without a way to calibrate/profile screens an color management
> > protocol looses a lot of its value. So to add this missing feature I
> > wrote the following protocol.
> >
> > The idea is tha
On 2019-04-14 12:57, Erwin Burema wrote:
Without a way to calibrate/profile screens an color management
protocol looses a lot of its value. So to add this missing feature I
wrote the following protocol.
The idea is that the calibration/profiling SW only sets the RGB
triplet and then the composit
12 matches
Mail list logo
