MegaGlest Forum

MegaGlest => Bug reports => Closed bug reports => Topic started by: filux on 26 June 2013, 13:16:04

Title: [fixed] r4514 Too short "next hint" button & button doesn't uses text from transifex
Post by: filux on 26 June 2013, 13:16:04

1. Since r4511 button is little too small. You always should remember that translations usually takes up more space than english string.
My proposition (taking into account the possibility of even longer string than my translation) is:

Code: [Select]

--- logger.cpp 2013-06-26 15:05:51.857138372 +0200
+++ Nowy katalog/logger.cpp 2013-06-26 15:03:37.813800797 +0200
@@ -296,7 +296,7 @@
  }
  //Show next Hint
  if(buttonNextHint.getEnabled() == false) {
- buttonNextHint.init((metrics.getVirtualW() / 2) - (300 / 2), 90 * metrics.getVirtualH() / 100 + 20,100);
+ buttonNextHint.init((metrics.getVirtualW() / 2) - (300 / 2), 90 * metrics.getVirtualH() / 100 + 20,175);
  buttonNextHint.setText(lang.get("ShowNextHint","",true));
  buttonNextHint.setEnabled(true);
  buttonNextHint.setVisible(true);

2 String on the button doesn't use Transifex's test string which is stored in $ UserData location (~/.megaglest/data/lang/...).

Title: Re: r4514 Too short "next hint" button & button doesn't uses text from transifex
Post by: GunChleoc on 11 July 2013, 16:45:10

I can confirm this, I need an additional width of at least 2 more em-spaces for my translation ("An t-ath ghliocas").

Title: Re: r4514 Too short "next hint" button & button doesn't uses text from transifex
Post by: tomreyn on 12 July 2013, 10:31:35

The patch for the first issue discussed here is applied in r4518.
The second issue Filux reported needs yet to be handled.