[UNAPI] - Telnet Client

Page 6/7
1 | 2 | 3 | 4 | 5 | | 7

By fr3nd

Expert (89)

fr3nd's picture

29-08-2019, 16:41

True... ducasp, do you want to fix it yourself? Feel free to add any description you like. It's just markdown inside the 'description' field of the yaml.

Feel free to create a pull request with your changes https://github.com/fr3nd/msxhub-packages/blob/master/package...

By karloch

Prophet (2066)

karloch's picture

30-08-2019, 01:35

Thank you ducasp!

I just tested the new version (how nice is HUB UPGRADE TELNET!). Great to see the cursor on the screen and the keys working correctly! However something weird happens: when the BBS loads the editor, the MSX sends an abort request and it is immediately closed. That was not happening in the previous release, so something must have been changed.

You can see what I am talking about here:

By karloch

Prophet (2066)

karloch's picture

30-08-2019, 03:12

By the way, I am curious, how it is possible to the client to work in MSX1? It only has 40 columns and SCREEN 2 is tiled.

By ducasp

Master (154)

ducasp's picture

30-08-2019, 04:28

karloch wrote:

Thank you ducasp!

I just tested the new version (how nice is HUB UPGRADE TELNET!). Great to see the cursor on the screen and the keys working correctly! However something weird happens: when the BBS loads the editor, the MSX sends an abort request and it is immediately closed. That was not happening in the previous release, so something must have been changed.

You can see what I am talking about here:

That's weird, the Client itself has changed just two things, the received buffer size and location so it won't interfere with the larger size of the latest ansi-drv and what it sends when an arrow key is pressed... Obviously something is wrong, just that something that could cause it doesn't come to my mind :P I'll check it this weekend, thanks for testing and reporting it, for me the editor that appeared is not the same you used, probably why it worked on my video.... oO

By ducasp

Master (154)

ducasp's picture

30-08-2019, 04:29

fr3nd wrote:

True... ducasp, do you want to fix it yourself? Feel free to add any description you like. It's just markdown inside the 'description' field of the yaml.

Feel free to create a pull request with your changes https://github.com/fr3nd/msxhub-packages/blob/master/packages/TELNET.yaml

Great fr3nd, I'll make sure to do it, thanks :)

By ducasp

Master (154)

ducasp's picture

30-08-2019, 04:36

karloch wrote:

By the way, I am curious, how it is possible to the client to work in MSX1? It only has 40 columns and SCREEN 2 is tiled.

It will be a dumb terminal, no ANSI escape code rendering, just use screen 0 and msx dos calls to write to screen . If using an 80 column card and setting screen to 80 columns before calling the client, it will work with 80 columns as well (I've tested the routines for screen detection / initialization on OpenMSX using Gradiente 80 Columns card) , otherwise, 40 columns. Not a great experience, but it is usable and a faster and more complete alternative to TCPCON. Smile

By karloch

Prophet (2066)

karloch's picture

30-08-2019, 13:35

ducasp wrote:

It will be a dumb terminal, no ANSI escape code rendering, just use screen 0 and msx dos calls to write to screen . If using an 80 column card and setting screen to 80 columns before calling the client, it will work with 80 columns as well (I've tested the routines for screen detection / initialization on OpenMSX using Gradiente 80 Columns card) , otherwise, 40 columns. Not a great experience, but it is usable and a faster and more complete alternative to TCPCON. Smile

That's way better than a MSX1 had until now Smile

Yesterday I was talking with a friend who managed to also connect his ZX Spectrum to the BBS, I was pretty surprised it was able to display the 80 columns and most of the colors. They must be using the tiles to redefine the ANSI chars and colors, but they avoid attribute clash quite well:

Probably a MSX1 can do better :P (this is NOT a feature request)

By PingPong

Prophet (3449)

PingPong's picture

30-08-2019, 14:33

ZX Spectrum does not have proper tiles like msx1 screen 2
Avoiding colour clash is not possible
64 columns in screen 2 is doable (with colour clash)

By ducasp

Master (154)

ducasp's picture

30-08-2019, 15:36

So, it seems that just where I did not think could change a bug, it did... I was sending a NULL terminator of arrow keys ESCAPE CODES as well as of enter (CR/LF). Minor fix, works fine with SlyEdit now:

https://github.com/ducasp/MSX-Development/blob/master/UNAPI/...

I've also followed fr3nd recommendation and updated the yaml file and pushed, so it hopefully will be available soon in MSX HUB as v1.11 as well.

# CHANGELOG v1.11

- Oops... When changing to send arrows as ESC commands, was sending also
0 (String terminator, not '0') after CR/LF and arrows, and this was causing
SlyEdit to quit even before you could type anything.

Again, Karloch, many thanks for this input. It is always a pleasure to see people using the software and liking it and suggesting.

P.s.: Having an ANSI mode on MSX1 would be cool, but I'm not sure I'm up to this task, if Toby didn't share ANSI-DRV source code I would most likely take an entire year to come up with something similar and probably not as fast lol... I still do not understand quite a bit of V9938/9928 and all their quirks. But if someone have some working example that I could grow on instead of working from the scratch, this could become a reality and it would be really nice!

By karloch

Prophet (2066)

karloch's picture

30-08-2019, 19:27

Thanks to you for the great work you put in the client Smile And about MSX1, I was just being curious, it was not a feature request. I don’t think there are many MSX1 ethernet users out there Smile

Page 6/7
1 | 2 | 3 | 4 | 5 | | 7