Author Topic: [Bug][Player] Pre/Postview texts not centered  (Read 252 times)

0 Members and 1 Guest are viewing this topic.

Online IchoTolot

  • Moderator
  • Posts: 2718
    • View Profile
[Bug][Player] Pre/Postview texts not centered
« on: May 12, 2020, 02:16:24 pm »
I don't remember if this topic already exists, if yes, sorry for the double post.

The pre- and postview level texts should be centralized instead of being at the very top. This way there are just much easier to read. It was already this way in the past, but I think in the format switch it got messed up somehow.

As a bonus, if it's possible:

If the text is under a certain number of lines, a little bit more space (maybe half or a quarter of a line) could be automatically put in between lines as this further increases readability.
« Last Edit: May 12, 2020, 09:15:20 pm by namida »

Offline Strato Incendus

  • He who usually only makes it up to rank two
  • Posts: 1214
  • #Team SliderFor20thNeoLemmixSkill
    • View Profile
Re: [Suggestion][Player] Centralize Pre/Postview texts
« Reply #1 on: May 12, 2020, 02:53:09 pm »
Thanks, I always tried to emulate this by inserting empty lines - but it would indeed be helpful if the text were centralised by default.
My packs so far:
Lemmings World Tour (New & Old Formats), my music-themed flagship pack, 320 levels - Let's Played by Colorful Arty
Paralems (Old Formats), a more flavour-driven one, 150 levels
Pit Lems (Old Formats), a more puzzly one, 100 levels - Let's Played by nin10doadict
Lemmicks, a pack for (very old) NeoLemmix 1.43 full of gimmicks, 170 levels

Offline namida

  • Administrator
  • Posts: 10704
    • View Profile
    • NeoLemmix Website
Re: [Suggestion][Player] Centralize Pre/Postview texts
« Reply #2 on: May 12, 2020, 09:15:02 pm »
It should be. And I'm sure this has been fixed once already, only to later break again. This is a bug.

Offline namida

  • Administrator
  • Posts: 10704
    • View Profile
    • NeoLemmix Website
Re: [Bug][Player] Pre/Postview texts not centered
« Reply #3 on: October 13, 2020, 09:21:02 pm »
Alright so - it turned out this was due to an uninitialized variable, which explains why the bug would go away and come back inexplicibly.

It's fixed somewhere along the lines of the various menu overhaul code I'm working on at the moment.