I can't find where I can report stuff about this MUI class so I talk here
A few days ago I updated Newstring.mcc on my OS4 machine. Now I am very surprised to see it appearing in Exchange. I don't see how it can be considered a commodity as I cannot remove it from the system nor that I can disable it. I thought this was the meaning of a commodity in the first place.
I don't see how it can be considered a commodity as I cannot remove it from the system nor that I can disable it. I thought this was the meaning of a commodity in the first place.
Newstring.mcc adds itself as a commodity broker only to be able to catch certain events from the input stream for its handling of i.e. RAmiga+C or RAmiga+V. Being a commodity makes this stuff really easy. But it does not react on the usual stuff like being killed or switched inactive, because there is only one single broker for all instances of Newstring.mcc no matter which application uses it.
Anyway, the devs could add an information text that displays when clicked on in Exchange, explaining that this is an interactive, system-used, non-user changable program.
It will appear only if it was used by at least one application before, i.e. IBrowse.
Quote:
Anyway, the devs could add an information text that displays when clicked on in Exchange, explaining that this is an interactive, system-used, non-user changable program.
I just commited the necessary change for the next MUI4 release. But this won't help for the old 68k version. That one must be patched on a binary level.
So it means one can't expunge it from memory, right?
Not unless all applications dispose all instances of Newstring.mcc. There is absolutely no need to do this yourself. The commodity broker will be removed automatically upon expunging Newstring.mcc from memory.
If newstring.mcc as a commodity can't be (user) accessed (and the user can't do anything with it either), wouldn't it be possible to "hide" it from view (Exchange) et al?
or
It'd be still running in the background and Exchange knowing about it i.e. it could be "greyed out" in the Exchange list
If newstring.mcc as a commodity can't be (user) accessed (and the user can't do anything with it either), wouldn't it be possible to "hide" it from view (Exchange) et al?
What is so wrong about letting the user see that there is something which hooked into the input stream, although it cannot be controlled by the user?
Quote:
It'd be still running in the background and Exchange knowing about it i.e. it could be "greyed out" in the Exchange list
My latest change will give you something similar. Although you still cannot control the Newstring.mcc commodity, you will now get some visual feedback: analog to the disabled Show and Hide buttons the Kill button will be disabled to indicate that this commodity cannot be removed manually.
My latest change will give you something similar. Although you still cannot control the Newstring.mcc commodity, you will now get some visual feedback: analog to the disabled Show and Hide buttons the Kill button will be disabled to indicate that this commodity cannot be removed manually.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
