After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323438 - Reproducible: Text rendered too small
Reproducible: Text rendered too small
Status: RESOLVED DUPLICATE of bug 153609
Product: dia
Classification: Other
Component: general
0.94
Other Windows
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-07 07:57 UTC by Anders Musikka
Modified: 2005-12-07 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This is the file mentioned in the bug report. (2.29 KB, application/octet-stream)
2005-12-07 07:58 UTC, Anders Musikka
Details

Description Anders Musikka 2005-12-07 07:57:35 UTC
Distribution/Version: XP, SP2

1: Start Dia.
2: Open file LinearP4 (I will try to attach it to this report)
3: Press ctrl-E, for 'show all'.
4: Click mouse on the text '2', on the lower left part of the screen. The text 
now changes apparent size, reducing to approximately 1/5 of the correct size 
(becoming difficult to read).

Expected behaviour: Text should never change size, except if explicitly 
modified by right-clicking, bringing up the properties dialog, and making the 
change.

Further details: If the document is closed, and then reopened, the sizes of 
other texts are also rendered wrong. If Dia is exited, and restarted, and the 
file is opened again, it shows correctly this time. The size is also sometimes 
fixable by adding a trailing space to the text in question. 

Also, when I inspect the LinearP4 file manually, I can see that the text-sizes 
are in fact correct in the file.

The 4 steps at the top of this description are reproducible every time.
Comment 1 Anders Musikka 2005-12-07 07:58:48 UTC
Created attachment 55736 [details]
This is the file mentioned in the bug report.

Open this file, then follow the steps detailed in the bug report to reproduce
the problem.
Comment 2 Lars Clausen 2005-12-07 10:54:14 UTC
Thank you for your report.  This particular bug has already been reported and
fixed in CVS.


*** This bug has been marked as a duplicate of 153609 ***