Opened 6 weeks ago

Closed 6 weeks ago

#445 closed bug (fixed)

MUI prefs: Failed to create application (20) - on another MUI preferences run

Reported by: Hubert Maier Owned by: Thore Böckelmann
Priority: normal Milestone: 5.0-2020R2
Component: MUI prefs application Version: 5.0-2020R1
Severity: minor Keywords:
Cc: OS Platform: All
Blocked By: Blocking:
Release Notes:

Description

Summary

If MUI prefs is already running and started a second time, an error message in a console window pops up:
Failed to create application (20).

Steps to reproduce

  1. run MUI prefs
  2. run MUI prefs again

Expected results

  1. No error message, i guess
  2. Adding "uniconify" followed by a "bring to front" would be best probably.

Actual results

See summary

  1. If the prefs window is hidden behind other windows it is brought to front.
  2. If the prefs window is iconified, nothing happens.

Regression

Nope, at least i don't think so, never tried it before.

Notes

Change History (5)

comment:1 Changed 6 weeks ago by Thore Böckelmann

Component: undefinedMUI prefs application
Milestone: future release5.0-2020R2
OS Platform: AmigaOS4All
Owner: set to Thore Böckelmann
Priority: undecidednormal
Status: newassigned

comment:2 Changed 6 weeks ago by Thore Böckelmann

Resolution: fixed
Status: assignedclosed

In 6590:

  • prefs.c: a double start of MUI prefs will now deiconify the first instance and bring it to the front. This closes #445.

comment:3 Changed 6 weeks ago by Samir Hawamdeh

Tried this one, i've iconified MUI prefs, and then double clicked to the MUI icon in order to open MUI again

While the firrst MUI instance will be deiconified as it should, i still getting the "Failed to create application (20)" message requester …

Maybe that error should not be showed in this case ?

comment:4 Changed 6 weeks ago by Thore Böckelmann

Resolution: fixed
Status: closedreopened

comment:5 Changed 6 weeks ago by Thore Böckelmann

Resolution: fixed
Status: reopenedclosed

In 6594:

  • prefs.c: added a check for a double start in case creating the Application object fails. If a first instance is detected then no error message will be generated. This closes #445 again.
Note: See TracTickets for help on using tickets.