Robertspark wrote:Think you've all missed the question
Perhaps I did...
Robertspark wrote:At no point did I suggest re-writing all of the existing default UCCNC screensets.
So, what was it exactly you want to do? Create a part which is language independent? What would be the point if not all the screens are similar and use the same language?
But yes, perhaps I don't really understand what you wanted to do...
Robertspark wrote:At no point did I suggest that it would be beneficial to have a screenset in russian more than any other language.
No, you did not suggest, but it was an example language you mentioned. You said "
I'm working with a screenset that is orffered in Russian" so I took that as example. I mentioned Hungarian as well, not just Russian, because CNC Drive is a Hungarian company with a lot of Hungarian knowledge. Who would be interested in doing it unless it was beneficial for them?
Robertspark wrote:the question was, do you think it would be possible to use a textfield object to display text which appeared like a label and was obtained from a slow looping macroloop which provided the translation for various bits of text?
...and the answer is almost exactly the same.
Yes, it is probably possible, but it is a huge job (which I am 100% sure about). ...and yes, I am pretty sure you need to rewrite the existing screenset to make it work if you want to use new, language independent buttons.
...but if I'd do it it would not be through a macro loop. Why would you need to have a macro loop involved at all for a simple (technically speaking) language set-up? Such things normally done in off-line configuration and not on a running software, so there is no need for macro loop. ...but resizing may create an issue, so the problem is probably quite complex.
Robertspark wrote:I am presently doing a screenset for something specific and I know that it IS also used by Russian speakers (I've seen the button images with the text on them), hence I was wondering if there may be an easier way than having a whole load of different buttons with different text on them or to just overlay the text you want on them with a label or textfield object).
Personally I'd just create separate bitmap files with the languages I'd provide. Depending on the work flow used for generating the button images this can be very simple. In my case for my Probe screen buttons, I used Adobe Photoshop CS5.1 and the text is just a separate layer, so changing the text to anything I want to is easy in the original file. Of course, once the file is saved as a png changing anything is not so easy any more.