[important] Test client bug - mystery which could help to solve custom font problem
Posted: Wed May 02, 2018 10:45 am
I've sent video with this bug ( https://www.youtube.com/watch?v=5AH61dV3JtQ ) to devs a few weeks ago, but unfortunatelly they said they don't know what could cause this bug, so I wanna share it to community, maybe someone would have ideas how it could happen. Maybe also it's my mistake and I failed to describe to devs the problem with this bug and why it's VERY important too look into it, so I'll try to do it here:
1) When I started to work on my 'tileset' custom font (example: https://www.youtube.com/watch?v=q_QYL8hZPsY ) TomeNET had version 4.7.0. At this version several glyphs didn't work for remapping, for example glyph #2
Also information about problem with #2 font listed in the guide:
https://youtu.be/MDYDr2Ey5nY?t=8m38s
It means that from version 4.7.0 to version 4.7.1a bug with #2 glyph was fixed!
3) Recently I've started to use 'test' client ( https://www.tomenet.eu/downloads/TomeNET-test.7z ) to be able to use new music features which I used in my musicpack... And I've discovered that Glyph #2 DOESN'T work any more, made 'test client bug' video and sent it to devs:
https://www.youtube.com/watch?v=5AH61dV3JtQ
It means that due working at new test client devs did something which broke possibility to map #2 glyph.. So in 4.7.1a #2 glyph WORKS, and in test client - it doesn't! And apparently it's unknown what caused that (or maybe I failed to deliver correct explanation of this issue to devs). If devs would compare source code from test client with source code from 4.7.1a - maybe it would be possible to solve the mistery how #2 glyph was 'blocked'.
It's VERY important issue which could show the reason why it's Not possible to map certain characters!
1) When I started to work on my 'tileset' custom font (example: https://www.youtube.com/watch?v=q_QYL8hZPsY ) TomeNET had version 4.7.0. At this version several glyphs didn't work for remapping, for example glyph #2
Also information about problem with #2 font listed in the guide:
2) but actually glyph #2 WORKS in TomeNET 4.7.1a. Evidence:Problems have been reported for mapping characters 2 and 16 to 27, there is
currently no further information available regarding this issue.
https://youtu.be/MDYDr2Ey5nY?t=8m38s
It means that from version 4.7.0 to version 4.7.1a bug with #2 glyph was fixed!
3) Recently I've started to use 'test' client ( https://www.tomenet.eu/downloads/TomeNET-test.7z ) to be able to use new music features which I used in my musicpack... And I've discovered that Glyph #2 DOESN'T work any more, made 'test client bug' video and sent it to devs:
https://www.youtube.com/watch?v=5AH61dV3JtQ
It means that due working at new test client devs did something which broke possibility to map #2 glyph.. So in 4.7.1a #2 glyph WORKS, and in test client - it doesn't! And apparently it's unknown what caused that (or maybe I failed to deliver correct explanation of this issue to devs). If devs would compare source code from test client with source code from 4.7.1a - maybe it would be possible to solve the mistery how #2 glyph was 'blocked'.
It's VERY important issue which could show the reason why it's Not possible to map certain characters!