Re: Call for help - understanding how to debug sw module

No probs, good pointer I think I can work with that :-) Chris On Friday, January 29, 2016, Tomaž Vajngerl wrote: > Hi, > > On Thu, Jan 28, 2016 at 9:52 AM, Chris Sherlock > > wrote: > > I did a calculation from http://www.sven.de/dpi

Re: Call for help - understanding how to debug sw module

Well, I just read the AquaSalGraphics code and there is a sanity check that limits it to 200DPI! I’m just testing now what happens if I set the max to 300. Chris > On 29 Jan 2016, at 9:39 PM, Tomaž Vajngerl wrote: > > Hi, > > On Thu, Jan 28, 2016 at 9:52 AM, Chris

Re: Call for help - understanding how to debug sw module

Oops, my calculation is out by quite a lot! My resolution is actually 202.57 PPI, still just over that 200PPI hard limit. Chris > On 31 Jan 2016, at 12:00 PM, Chris Sherlock > wrote: > > Well, I just read the AquaSalGraphics code and there is a sanity check that

Re: Call for help - understanding how to debug sw module

OK, I didn’t read the comment above it correctly - 200 should be more than enough our AquaSalGraphics class doesn’t give DPI in terms of actual screen resolution but the logical screen resolution. I’ve pushed a gerrit patch for review to get the *actual* screen DPI if anyone wanted to review

Re: Call for help - understanding how to debug sw module

Hi, On Thu, Jan 28, 2016 at 9:52 AM, Chris Sherlock wrote: > I did a calculation from http://www.sven.de/dpi and apparently I have a pixel > density of 267.02 PPI. > > Wondering if this is skewing the calculations. OS usually doesn't tell the correct monitor DPI to

Re: Call for help - understanding how to debug sw module

I did a calculation from http://www.sven.de/dpi and apparently I have a pixel density of 267.02 PPI. Wondering if this is skewing the calculations. Chris > On 28 Jan 2016, at 12:13 PM, Chris Sherlock > wrote: > > Hey guys, > > I know a few people have built on

Re: Call for help - understanding how to debug sw module

If it is at all helpful, these are the hardware specs (this machine is seriously overkill, I got it with redundancy money a year ago): Hardware Overview: Model Name: iMac Model Identifier: iMac15,1 Processor Name: Intel Core i5 Processor Speed: 3.5 GHz Number of

Re: Call for help - understanding how to debug sw module

Hey guys, I know a few people have built on a Retina based Mac and haven’t had this issue… Any ideas why this might be occurring? Chris > On 22 Jan 2016, at 11:07 AM, Chris Sherlock > wrote: > > Hi all, > > I’m getting an error that never appears to any of the

Call for help - understanding how to debug sw module

Hi all, I’m getting an error that never appears to any of the OS X buildbots or tinderboxes. I suspect that it has something to do with the fact that I have a Retina iMac. Basically, the unit test that is failing is in CppunitTest_sw_ooxmlimport: Test name: