Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#71 closed bug (fixed)

MUI Palette

Reported by: Mikhail Malyshev Owned by: Thore Böckelmann
Priority: normal Milestone: 3.9-2014R2
Component: muimaster.library Version: 3.9-nightly build
Severity: minor Keywords:
Cc: OS Platform: AmigaOS3
Blocked By: Blocking:
Release Notes:

Description

Not complaining about speed, well, a bit…
But the menu is broken, see picture.
Also, if you have a choice of two fancy triangle & circle gizmo's,
why not add a 3-rd? More traditional and light weigh thing.

Attachments (1)

mui-menu-bugs.png (29.9 KB) - added by Mikhail Malyshev 5 years ago.

Download all attachments as: .zip

Change History (10)

Changed 5 years ago by Mikhail Malyshev

Attachment: mui-menu-bugs.png added

comment:1 Changed 5 years ago by Mikhail Malyshev


comment:2 Changed 5 years ago by Thore Böckelmann

Component: undefinedmuimaster.library
Milestone: MUI 3.9-2014R2
Priority: undecidednormal
Status: newaccepted

comment:3 Changed 5 years ago by Thore Böckelmann

Owner: set to Thore Böckelmann
Resolution: fixed
Status: acceptedclosed

In 3733:

  • mastertext.c: fixed the broken context menu display of Colorring.mui due to some recent merges from the MUI4 trunk which did not handle empty preparse strings correctly. This closes #71.

comment:4 in reply to:  description Changed 5 years ago by Thore Böckelmann

Replying to Michael:

Not complaining about speed, well, a bit…

This point will not be discussed any further. We stated our reasons often enough by now. Please stop complaining. 8bit screens are simply outdated.

But the menu is broken, see picture.

Next time please choose a more appropriate title for the ticket. "MUI palette" has absolutely nothing in common with the wrong text display in the context menu. This is really misleading. Furthermore you once again omitted the basic information to which nightly build exactly you are referring. As the name "nightly build" suggests there are lots of nightly builds, in theory one each day/night. Without these basic information I will close future tickets as "invalid" without looking at them any further. Please don't get me wrong. This is no personal hate against you or any other person. In fact I really appreciate that you are reporting some many bugs and finally use the bugtracker instead of private mail. But there are some rules which are to be obeyed and you are constantly failing in this respect.

Also, if you have a choice of two fancy triangle & circle gizmo's,
why not add a 3-rd? More traditional and light weigh thing.

See above. The Colorring class will stay as it is. Accept this.

comment:5 Changed 5 years ago by Mikhail Malyshev

MUI-3.9-20140721

comment:6 Changed 5 years ago by Mikhail Malyshev

Interruptible rendering process, currently if system is 100% busy and triangle is rendering something internally you can resize the window and gfx will be drawn over the window borders since notification to the rendering process was not passed/updated. Also it should have been interrupted and restarted with new dimensions. Currently it's very heavy cpu loop.

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

This cannot be worked around. MUI's redrawing happens in the normal application context while the window resizing happens in the context of input.device which runs at priority 20. Thus it may happen that a resizing event interrupts an ongoing redraw action and causes it to draw in unwanted regions. As soon as MUI detects the resize event it will redraw the window contents again according to the new dimension.

comment:8 Changed 5 years ago by Mikhail Malyshev

Strange, from my view, the window refresh is fairly fast, but the preparation of the gizmo graphics can take a long time, what is it doing ? It looks like the code is really slow or something else interacts inside it before outputting the data in the window. I am serious, it can not take 10 seconds to do something complex and yet simple like that in a window of around 500x300 pxl.

comment:9 Changed 5 years ago by Thore Böckelmann

Milestone: MUI 3.9-2014R23.9-2014R2

Milestone renamed

Note: See TracTickets for help on using tickets.