Mantis - Croquet
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3973 Tools minor always 06-30-06 20:47 06-30-06 23:10
Reporter: espin Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0003973: illegible labels in ArchiveViewer
Description: When I open a zip from a FileList2 I get an ArchiveViewer
where the labels of the buttons use a textstyle
       WindowFont
See attached gif.
In order to fix it, I changed
       ArchiveViewer>>createButtonBar
          ...
          TextStyle knownTextStylesWithoutDefault do:
          ...
with
       ArchiveViewer>>createButtonBar
          ...
          TextStyle defaultFamilyNames do:
          ...
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:  ArchiveViewerUglyButtons.gif [^] (6,921 bytes) 06-30-06 20:47

Notes
(0005457)
KenCausey   
06-30-06 21:00   
It would help if you could provide more information about the environment in which you see this. It looks fine to me in 3.9b-7033 on Linux. Have you loaded anything into this image? If so have you checked it in a clean image?
(0005459)
espin   
06-30-06 21:20   
I run the above on WinXP (it was also occurring on WinNT)
using a clean Croquet(Hedgehog) SDK 1.0. image.
I re-tested on WinXP with Squeak 3.9a-7005 and
3.8-6665full and it does not happen: the text style used here
is BitStreamVersSans because Window Font is not loaded (I guess).
Unfortunatelly I do not know when/how WindowFont is loaded into the system.

Hedgehog seems to start from http://isqueak.impara.de/webdav/iSqueak-3.8-6665.zip [^]
(you can see it if you load .../deployment/Homebase.image + other hacks)
(0005464)
KenCausey   
06-30-06 23:10   
If I understand correctly you are seeing this in a Croquet image, not a Squeak image. Since Croquet is a derivative over which we have no direct control I don't think this is a valid Squeak bug report but instead needs to be reported to the Croquet development team. Would you agree?

For the moment I'm going to assume you do and move this issue to the Croquet project on this Mantis server. In the future when you find an issue in Croquet you probably want to start by checking the most recent released Squeak image and see if the issue occurs there as well. If so then do as you did here and report the bug under the Squeak project. If not then report it under the Croquet project. (In case you aren't aware of it note that at the top right of all Mantis pages there is a drop-down list labelled 'Project:' where you can change projects.)