example edittools.txt (german) (https://simutrans-germany.com/translator_page/base_text/index.php?obj_id=25007&lang=de&ref_lang=none&trans_lang=de,none,none)
example slopetools.txt (german) (https://simutrans-germany.com/translator_page/base_text/index.php?obj_id=25037&lang=de&ref_lang=none&trans_lang=de,none,none)
Screenshot 2025-06-09 114456.png
To use the buttons in the help, two things would need to be changed.
a) The line height must be determined by the graphics.
- Alternatively, continuous text around the graphics would be required, but this would require more effort.
b) An intermediate implementation list for the graphics.
example
t30=t55
t31=t56
t32=t47
...
t40=-
t41=-
t42=-
t43=-
This list would be necessary to account for differences in graphic definitions between paksets. Alternatively, all sets would have to use the same definition order, which is unlikely to be possible.
This seems like a great idea to me 💡, Does it currently work the same as in the scenario?.
Quote from: Yona-TYT on June 09, 2025, 04:23:49 PMThis seems like a great idea to me 💡, Does it currently work the same as in the scenario?.
Yes. And that's why the same problems exist when using button graphics.
simple scenario for img ids
Screenshot 2025-06-09 225432.png
The toolbar help files need to go to the pak-dependent translations. The toolbar (even the slope toolbar) strongly varies between paksets, some have climates, some vertical slopes etc. There is no standard. If not there, there should be a follbar using no images from the general translations.
Then the different image numbers are no longer a problem.
It is also very hard to have the text centered vertically. So it will stay at the top.