> On 5 Feb 2016, at 9:29 PM, Tomaž Vajngerl wrote:
>
> Hi,
>
> On Fri, Feb 5, 2016 at 2:02 AM, Chris Sherlock
> wrote:
>> There were a series of patches that handled hi-DPI displays in 2014 that
>> Keith did for us and that were pushed by Kendy:
>
> Yes, and I continued later on with the pat
Hi,
On Fri, Feb 5, 2016 at 2:02 AM, Chris Sherlock
wrote:
> There were a series of patches that handled hi-DPI displays in 2014 that
> Keith did for us and that were pushed by Kendy:
Yes, and I continued later on with the patches when I got a laptop
with HiDPI screen and running Fedora.
>> I'v
On 5 Feb 2016, at 6:37 AM, Norbert Thiebaud wrote:
>
> On Thu, Feb 4, 2016 at 10:10 AM, Armin Le Grand wrote:
>>
>> Example:
>> You have painted an ellipse (vector data). User chooses 'convert to Bitmap'
>> and saves the file. On Mac you will have a >200 DPI bitmap,
>
> Just as a reminder. the
On Thu, Feb 4, 2016 at 10:10 AM, Armin Le Grand wrote:
>
> Example:
> You have painted an ellipse (vector data). User chooses 'convert to Bitmap'
> and saves the file. On Mac you will have a >200 DPI bitmap,
Just as a reminder. the 'DPI' on mac depend dynamically on the
'Screen' on which you are
Hi SOS,
Am 03.02.2016 um 16:46 schrieb SOS:
It is relevant. If you have a vector graphic and it gets converted to
bitmap, the DPI from the system is used to define the resulting pixel
size. Conversion to bitmap happens more often than it might seem.
Examples:
- user chooses to do so (contex
Hi Chris,
On Wednesday, 2016-02-03 23:27:22 +1100, Chris Sherlock wrote:
> If nobody has any objections, I can add an environment variable that forces
> it to pick up the actual screen resolution.
>
> Something like OSX_FORCEBACKINGCOORDS
Please prefix with LIBO_..., so LIBO_OSX_FORCEBACKINGC
hallo Armin
new comments inline on your remarks
On 3/02/2016 14:10, Armin Le Grand wrote:
Hi,
comments inline
Am 03.02.2016 um 12:35 schrieb SOS:
On 3/02/2016 11:32, Chris Sherlock wrote:
On 3 Feb 2016, at 7:24 PM, SOS wrote:
On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at
Hi,
comments inline
Am 03.02.2016 um 12:35 schrieb SOS:
On 3/02/2016 11:32, Chris Sherlock wrote:
On 3 Feb 2016, at 7:24 PM, SOS wrote:
On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
The other question is: why would we not want to the act
> On 3 Feb 2016, at 11:08 PM, Alexander Thurgood
> wrote:
>
> Le 03/02/2016 00:52, Chris Sherlock a écrit :
>
> Hi Chris,
>
>
>> Hi all,
>>
>> I’ve mentioned this briefly to Tor on IRC, but thought I’d email the mailing
>> list and a general enquiry.
>>
>> I noticed that we don’t actual
On 3/02/2016 13:01, Chris Sherlock wrote:
On 3 Feb 2016, at 10:35 PM, SOS wrote:
On 3/02/2016 11:32, Chris Sherlock wrote:
On 3 Feb 2016, at 7:24 PM, SOS wrote:
On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
The other question is: why wou
Le 03/02/2016 00:52, Chris Sherlock a écrit :
Hi Chris,
> Hi all,
>
> I’ve mentioned this briefly to Tor on IRC, but thought I’d email the mailing
> list and a general enquiry.
>
> I noticed that we don’t actually get the “true” DPI for OS X, nor the actual
> resolution - at least on high
On 3 Feb 2016, at 10:35 PM, SOS wrote:
>
>
> On 3/02/2016 11:32, Chris Sherlock wrote:
>> On 3 Feb 2016, at 7:24 PM, SOS wrote:
>>>
>>> On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
> The other question is: why would we not want to th
On 3/02/2016 11:32, Chris Sherlock wrote:
On 3 Feb 2016, at 7:24 PM, SOS wrote:
On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
The other question is: why would we not want to the actual DPI and
screen resolution?
My understanding is that, h
On 3 Feb 2016, at 7:24 PM, SOS wrote:
>
>
> On 3/02/2016 3:55, Kohei Yoshida wrote:
>> On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
>>> The other question is: why would we not want to the actual DPI and
>>> screen resolution?
>> My understanding is that, historically, the OS provided
On 3/02/2016 3:55, Kohei Yoshida wrote:
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
The other question is: why would we not want to the actual DPI and
screen resolution?
My understanding is that, historically, the OS provided a function to
query DPI but what gets returned from suc
On Wed, 2016-02-03 at 10:52 +1100, Chris Sherlock wrote:
> The other question is: why would we not want to the actual DPI and
> screen resolution?
My understanding is that, historically, the OS provided a function to
query DPI but what gets returned from such function was not always
accurate (or a
size of things obviously
double (or change to whatever scale the screen resolution makes it).
I guess I was wondering what the impact is, or what challenges have we had with
not getting the *actual* DPI and screen resolution on OS X builds? Has anyone
noticed anything odd when they are using a Mac
17 matches
Mail list logo
