Open GoogleCodeExporter opened 8 years ago
which components are you referring to? Resistors, caps, transistors, ICs all
have their labels centered
Original comment by bancika@gmail.com
on 11 Sep 2012 at 2:50
All caps and resistors..
I'll attach a screenshot.
Software acts the same here on my laptop (asus eee) running fedora 14 with java
version "1.6.0_20" as on my desktop machine running LMDE and latest java.
+m
Original comment by miro...@gmail.com
on 11 Sep 2012 at 3:56
Attachments:
that's weird, I've never seen it before. Probably has to do with font
measurements under linux. I'll investigate...
Original comment by bancika@gmail.com
on 11 Sep 2012 at 3:59
First i thought it was a feature or that i had something configured really
wrong.
Now that i replaced my 3.12 with 3.15 on the LMDE installation, it works
correctly. But there is one difference; Here on Fedora 14, the font defaults to
"Abyssinica SIL" which could be the problem. But font cannot be changed on
components, so i can't really test if that's it. Abyssinica SIL is installed by
default on Fedora.
Still it puzzles me why the font offsets only on caps and resistors..
Anyway. It is a problem that manifests itself on unsupported version of Fedora.
Original comment by miro...@gmail.com
on 11 Sep 2012 at 4:19
Nope. It isn't just Fedora 14. Since the original report, i've run Fedora 18
beta on this machine and now i'm running CentOS 6.3. Both had/have Oracle java
from official Oracle packages.
I've attached another screenshot, and the issue is still present.
But i think i know how this happens. This machine is old Asus EEE laptop, with
puny 1024x600 resolution screen. I believe that DIYLC assumes a larger
resolution, and that results in value/name offset.
If i save the project and copy it to my desktop machine over ssh and open it,
the texts are in their rightful places.
I'm not familiar with java, but is there a way to add window size to run.sh
script? If smaller size could be determined there, i think the problem would go
away.
Original comment by miro...@gmail.com
on 2 Dec 2012 at 8:58
Attachments:
Original issue reported on code.google.com by
miro...@gmail.com
on 11 Sep 2012 at 2:49