Has anyone tried the newest version of SimpleMail?

It requires the newest nlist. I can't get it to run.

The directions suggest bindkeys? I went to MUI setting and selected fonts, but still simplemail asks for the newest nlist.

Any Ideas?

Hello matt3,

You have to download nlist for morphos and install it. Do it by hand because the install script wants to copy the files in sys:classes/mui instead of replacing those e present in mossys:classes/mui. After that flush the old files from memory or reboot your machine otherwise simplemail 0.25 wont start.

Brumiga

I had the exact same problem

Assuming you have the newest nlist installed you need to delete the nlist classes from the mossys:classes/mui directory.

I thought objects in mossys where supposed to be superceded by newer versions in sys:, but there you go.

Anyhoo, simplemail wouldn't work despite the latest nlist being installed until I deleted the older version in mossys:classes/mui.

ya know it would be cool if someone would explain why that is, thanks.

Mark Cheetham

MaSC:

There are two directories for mui classes. The Mossys:classes/mui is specifically for MOS PPC native classes, while the Sys:classes/mui ones are for "3rd party" generic/68k versions.

If the same file is in mossys and sys MOS will always use the mossys version despite the version of either file.

If this nlist is a true ppc version then you can indeed put it in mossys, if its not put it in sys and "backup" the older version in mossys to somewhere safe.

Hope that clears things up for you.

Bifford

I had a lot of trouble myself and making matters worse the mirror I was getting the new nlist from was sending the older version at first. Once I installed by hand I still kept getting th eolder version from mossys taking over. renaming the same files in mossys helped at last and I put the new ones in sys.

I get it now, Thanks for the help :)

It seems to me to be messy, what with various versions and 68k/ppc binaries around in various places. MOS could do with some kind of manager, that'll compare versions and mos, ppc(wos etc) and 68k binaries so you can decide which you want to move into storage and which you want to keep.

[ Edited by MaSC on 2005/2/9 0:03 ]

Quote:I've felt that way for a while - especially this last month when I've been trying to update and check all my MUI and lib files.

thank the ghods for magellan!
still, it gets very confusing especially when you have to hunt down the files.

I agree as well. A manager that will look at MUI classes and libs then
ask to delete ones that are the same would help a lot, something that
shoes all classes and version numbers would be even better.

A little class simplification would also be welcome. I hate it when I
want to change my MUI colors and have to mess with 3 string classes, 3
text input/editor classes, 2 list classes, 4 toolbar classes, etc.

It is not something that could be done from a application point of
view, but could it be possible to have certain classes point to other
classes? For example, maybe it could be decided that Text Input be
made the standard text input class and there could be new
String, Better String, and New String classes that would point
to the Text Input class.

--Aaron