Custom Query (418 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 418)

Ticket Resolution Summary Owner Reporter
#421 wontfix Changing name of the Clock demo Samir Hawamdeh
Description

Problem

By accident the Clock demo in "Demos" folder of MUI share the same name of the Clock utility of the Enancher Package of AmigaOS4

Analysis

In case you have, atleast once lanched the Clock demo of MUI, then anytime you strat the Updater program of the Enancher Package, the name version of this MUI demo will conflct with the Clock utility of the Enancher … this prevent you to check and download correctly the Clock utility using Updater When you open the Updater

Enhancement recommendation

Well, perhaps changing the name of this demo from "Clock" to "MUI Clock" or something similar could help

#156 fixed Changing screenmodes while MUI prefs running Thore Böckelmann Mikhail Malyshev
Description

With older MUI 3.9 it is possible to start MUI prefs, iconify it, change WB screenmode and reopen it.

With MUI 4 under OS3 or OS4 it prevents the system from changing screenmode while it is running.

Under OS4 it causes an infinite loop of automatic attempts to change screenmode.

#123 fixed Check stack size to be large enough Thore Böckelmann Thore Böckelmann
Description

Problem

MUI 3.8 already demanded more stack than the default 8K provided by the system. With MUI 3.9 this requirement has increased even more. Without enough (free) stack certain applications will just crash.

Analysis

Ticket #116 has proven that a stack size of 16K or 20K might be enough, but 32K is definitely a better choice and should be used as an absolute minimum requirement.

Enhancement recommendation

To avoid future crashes the application's stack size should be checked to be at least 32K when creating an instance of Application.mui as this the absolute basic for an MUI application. If the current stack size is found to be lower a warning should be shown to the user with the ability to abort the application early to avoid possible crashes due to the too low stack size.

AmigaOS4 does lots harder to provide a bigger stack even if an application's icon requests loo little stack when started from Workbench. AmigaOS3 would require lots of patches for this to archive. In general it does not harm to have such a check for all systems.

Note: See TracQuery for help on using queries.