Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#300 closed bug (invalid)

Dashed line around images

Reported by: Fernando Martín Morillo Owned by:
Priority: normal Milestone: 4.0-2016R2
Component: Area.mui Version: 4.0-2016R1
Severity: minor Keywords:
Cc: OS Platform: AmigaOS3
Blocked By: Blocking:
Release Notes:

Description

Hi: I've just tried the latest version for OS3 and there is something wrong with the images when I run AmiModRadio.

[url=http://hostthenpost.org/uploads/98125c943b609bb5a0f38895877b3f29.png][img]http://hostthenpost.org/uploads/98125c943b609bb5a0f38895877b3f29_thumb.png[/img][/url]

Attachments (3)

amimodradio.png (151.0 KB) - added by Thore Böckelmann 4 years ago.
Screenshot of AmiModRadio
homebank.png (87.7 KB) - added by Thore Böckelmann 4 years ago.
Screenshot of HomeBank
LatestMui4.png (159.3 KB) - added by Fernando Martín Morillo 4 years ago.

Download all attachments as: .zip

Change History (13)

comment:2 Changed 4 years ago by Fernando Martín Morillo

I know it's also my fault as I tried some nightly build before this and I had these same problems but I didn't comment, I just thought they would be fixed.

Last edited 4 years ago by Fernando Martín Morillo (previous) (diff)

comment:3 Changed 4 years ago by Fernando Martín Morillo

Changed 4 years ago by Thore Böckelmann

Attachment: amimodradio.png added

Screenshot of AmiModRadio

Changed 4 years ago by Thore Böckelmann

Attachment: homebank.png added

Screenshot of HomeBank

comment:4 Changed 4 years ago by Thore Böckelmann

Component: undefinedArea.mui
Milestone: future release4.0-2016R2
Priority: undecidednormal
Resolution: invalid
Status: newclosed

First of all, please, please, please don't use external file hosters for simple attachments like screenshots. Such external links are guaranteed to become unavailable more sooner than later, which makes later reference (in a year or two) impssible.

This bugtracker is perfectly able to handle attachements up to 5MB each itself. If this limit is too small for specific attachments we can raise it. But attaching file here directly ensures that the files stay accessable for an arbitrary amount of time.

Now back to this issue. I suppose you are using a colormapped screenmode with 256 colors at most. At least the screenshots look "dithered". Most probably you have some external bitmap frames configured instead of the builtin standard frames. Bitmap frames can be used on truecolor screens only. On colormapped screens you get that SHINE/BACKGROUND dashed frame instead to give you a hint that the intended frame cannot be displayed.

All this happens because of your personal MUI configuration and because of the colormapped screen. The builtin default configuration uses the builtin frame styles on. There is no bug in MUI here.

Changed 4 years ago by Fernando Martín Morillo

Attachment: LatestMui4.png added

comment:5 Changed 4 years ago by Fernando Martín Morillo

Yes, you are right. I see I can get rid of that frame of the image. Thanks.

comment:6 Changed 4 years ago by Fernando Martín Morillo

But then a program like AmiModRadio that includes a frame in the images (radio image square border and buttons borders) the program -not MUI prefs- can't show it like before it could.

comment:7 Changed 4 years ago by Thore Böckelmann

If the frame is part of the image itself the restriction of additional frames added by MUI does not apply. An image is an image, no matter what it is supposed to represent.

comment:8 Changed 4 years ago by Fernando Martín Morillo

Tygre added as you commented as setting a white (SHINE pen) background (sorry I was thinking that he added a frame), and opening AmiModRadio with the default MUI prefs it was showing a border around them and inside that white background. Now with the same default MUI prefs it shows that dashed lines.

So do you say (I understand) that it isn't that MUI has changed the code to show that background but that some preference of MUI has changed with this version as default and then I only have to change the prefs to have it as it was as default before?

If it is a new default pref of MUI then it was better as before I am saying.

Last edited 4 years ago by Fernando Martín Morillo (previous) (diff)

comment:9 Changed 4 years ago by Fernando Martín Morillo

I'm seing that it musn't be the new MUI version but the MUI prefs that I am trying now.

Sorry for the inconveniences.

comment:10 in reply to:  8 Changed 4 years ago by Thore Böckelmann

Replying to Retrofan:

Tygre added as you commented as setting a white (SHINE pen) background (sorry I was thinking that he added a frame), and opening AmiModRadio with the default MUI prefs it was showing a border around them and inside that white background. Now with the same default MUI prefs it shows that dashed lines.

Did you really reset all MUI settings to default values? MUI's internal default settings don't use any bitmap frames. However, your own global default value might use them. This is something that only you can check yourself.

Currently AmiModRadio is always setting MUIV_Frame_ImageButton as frame for each image button. To get rid of this frame one must change AmiModRadio's MUI settings and configure the image button frame as the "none" frame (the 3 dots in the frame selection window).

But there is another approach. If the image file name contains the substring "_frame" then the image itself is considered to contain a frame already. MUI will then switch to the "none" frame automatically to avoid duplicate frames (the outer image button frame plus the inner frame contained in the image).

Note: See TracTickets for help on using tickets.