Re: Nick's Learning Mapper

From http://www.gammon.com.au/forum/?id=14607

I downloaded the 4 files. Two in the lua folder, 2 in the plugins folder.

I activated the plugin and the map window shows up, but the learning window does not.

I have tried mapper learn and it does not result in any thing that I can see.

Is there a GMCP version of this?

There are two windows it draws (apart from the map).

The "learning dialog" window with buttons to press to teach it line types.

The "learning info" window which shows the deduced line type next to each line from the MUD. This window has thin gray lines at each side of it. They can be a bit hard to spot.

Do you see either of those? If so, which?

Possibly you have the wrap column set to a very large number (output configuration). The learning windows are drawn to the right of the wrap column.

GMCP does not really apply - this mapper is intended to deduce the map information from non-GMCP MUDs.

As I said, the map window shows up, but the learning window does not.

I definitely have my column set really high to avoid wrapping, since it's broken right now. I've temporarily reduced it to test out the mapper some more. I do see the learning window now.

Thanks for your help.

Things that break wrapping: variable width fonts and fonts that use different width for bold characters if the show bold setting is active.

MUSHclient wraps naively using an average character width, so if any characters on a line are a different width, the calculation will be wrong.

My issue with wrapping isn't how it's wrapping, it's that it's wrapping at all when I tell it not to. :)

See https://github.com/nickgammon/mushclient/issues/63

The client always wraps, the misleadingly-named “Wrap output at column number” checkbox only affects whether it wraps at a space or not.

It pre-allocates room for the number of characters in the line (when the line is started) for speed reasons. Thus it must always wrap when that limit is reached.

It is more than misleading in the checkbox, you have a menu item under game that says "Wrap Output" that suggests this is togglable.

I read your comments on the git issue and if wrapping is unavoidable then I'll have to keep my 500 column to reduce opportunities for the client to wrap.

Out of curiosity, why don't you want the output to wrap? If it doesn't wrap, and a very long line arrives, then part of it disappears off the RH side of the screen and is unreadable.

The client has been around since 1995 and you are the first person to complain that you don't want output to wrap.

The decision on whether to wrap or not should be first by the server and then by the player, facilitated by the client. A client could provide for wrapping, but not enforce it (or if wrapping, maybe at the viewport's edge by default, with option to shape it more if desired by the player).

Wrapping that goes off the screen could be by design (because the server wants the player to decide how to wrap and when).

Or wrapping is done at the server level with a backup wrapping as optional by the player via his client settings.

And I'm not complaining. I have options and none of them are arduous. :) I'm merely expressing an opinion.