« Last post by hjjggh on June 26, 2026, 03:01:44 pm »
For non-English speakers attempting localization, the lack of a language folder and hard-coded text indicates an issue. Please provide a separate localization file (e.g., XML).
Quote "Vaquero March 18, 2014, 06:56:26 pm
I'm wondering why you didn't go for a full localization file. At the moment all the text is hardcoded, and for some tools, if a user version is present, the text gets replaced. Why not replace all text in the code with keys, which content is then loaded according to the chosen language? Additionally I always used a parsing function to determine if the key contains text or a reference to another key in another section or the default if there is none in the selected language. It's a good thing you've already written a frontend to manipulate XML data. But with the current implementation one can't localize menu items for example. I know at this point it is a huge workload to replace all hardcoded text, which is why I do this stuff early on in a project. I still wish, you would consider it. For some unknown reason I can't copy the helptext from the tool search, but from the tools customization. But the "User Tool Text" just works in the tool search and not in the tool customization..."
« Last post by Noobnvil on June 09, 2026, 09:31:51 pm »
Tnx. I trying to do the car modeling tutorial. Question on drawmesh...if I have 4 lines drawn how do I move them all at once? I can move them one by one...I can select them all...but how to move them all?