Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#51 closed bug (wontfix)

TextView -> MUIPrefs hits

Reported by: Mikhail Malyshev Owned by:
Priority: normal Milestone: 3.9-2014R2
Component: foreign class Version: 3.9-2014R1
Severity: minor Keywords:
Cc: OS Platform: AmigaOS3
Blocked By: Blocking:
Release Notes:

Description (last modified by Thore Böckelmann)

Enter MUIprefs/external - TextView

Play with the text editor by entering some text, and selecting it with mouse

now select any other MUIprefs/external *.mcp and we get hits.

if we return to TextView and play some more, we will get endless single hits
on every prefs change we do.

Also TextView prefs setting - background button
behaves oddly, brings up image requester, not pattern requester
how ever dropping a setting from defaults button works ok and set the background to patter or colour, but the setting is not remembered / or not displayed correct on loading MUIPrefs

Works in early MUI 3.9 versions

Attachments (1)

textview_hits.txt (5.6 KB) - added by Thore Böckelmann 6 years ago.
Enforcer hits of TextView.mcc

Download all attachments as: .zip

Change History (5)

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

First of all please do not post such logs inline but attach them as files.

The hit definitely happens in TextView.mcc, so why should MUI be at fault here? It is not MUI's task to repair broken classes.

And finally you are again mixing different bugs in one ticket. The first bug are the Enforcer hits and the second is the wrong image selection, but there is absolutely nothing common here. Is it really so hard to open separate tickets?

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

Description: modified (diff)

Changed 6 years ago by Thore Böckelmann

Attachment: textview_hits.txt added

Enforcer hits of TextView.mcc

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

Component: undefinedforeign class
Milestone: MUI 3.9-2014R2
Priority: undecidednormal
Resolution: wontfix
Status: newclosed

The more often I look at the log the more I get the impression that TextView.mcc is utterly broken. Although this did become obvious with MUI 3.8 the hits happen quite randomly in completely unrelated classes. The invalid access within TextView.mcc is always the same, but the stack trace makes absolutely no sense. As long as we don't have access to TextView.mcc's source code it is impossible to tell what is going wrong there.

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

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

Milestone renamed

Note: See TracTickets for help on using tickets.