Revision history [back]
We'll try to replicate and fix this. My guess is the DPI is reported high and the code we're using to display help is doubly compensating for that, probably because Qt isn't consistent in what it's doing). A work-around would be to view the docs on our website for now.One thing that would be useful if you're willing is to see if you also have problems like this with the release from http://wingware.com/wingide/early Thanks for reporting this problem!
We'll try to replicate and fix this. My guess is the DPI is reported high and the code we're using to display help is doubly compensating for that, probably because Qt isn't consistent in what it's doing). A work-around would be to view the docs on our website for now.One thing that would be useful if you're willing is to see if you also have problems like this with the Wing 8 alpha release from http://wingware.com/wingide/early Thanks for reporting this problem!
We'll try to replicate and fix this. My guess is the DPI is reported high and the code we're using to display help is doubly compensating for that, probably because Qt isn't consistent in what it's doing). A work-around would be to view the docs on our website for now.One thing that would be useful if you're willing is to see if you also have problems like this with the Wing 8 7 alpha release from http://wingware.com/wingide/early Thanks http://wingware.com/wingide/earlyThanks for reporting this problem!
Sorry for not answering this earlier. Apparently we didn't get notice of it being posted. We'll try to replicate and fix this. My guess is the DPI is reported high and the code we're using to display help is doubly compensating for that, probably because Qt isn't consistent in what it's doing). A work-around would be to view the docs on our website for now.One thing that would be useful if you're willing is to see if you also have problems like this with the Wing 7 alpha release from http://wingware.com/wingide/earlyThanks for reporting this problem!