sharkx

You have to do it in LUA code: myStrings = {"Hello World", "Here comes the sun", "How do you do?", "and so on" } In your Message box you select "User Expression" from the list and enter myStrings[1] for "Hello World" After quite some time, I'm back to my cartridge... For now, writing the strings in Lua code worked fine, but wouldn't this be an interesting feature to have ? I mean, have an editable string table that is transposed when compiled into code by urwigo ? Besides that, I would like to report two user interface annoying things : 1. there is no "close" button for the main tabbed group; when you get a lot of windows open, one needs way to many clicks to right-click the tab, then choose "close", then select another, etc. 2. you need two clicks now to set focus to the right input on the right-side properties panel; for instance, you have a Lua user expression box; you select it, the properties show the Lua editor; but if you click inside the editor, the first click focuses the panel, then the second focuses the editor, and the caret appears. Apparently this happens for any input, not just the code editor. I'm not sure those problems existed before, but I did not notice them until the last update. Otherwise, if it needs to be said again, this is a great tool

This may be a stupid question, as I know little about Wherigo objects and lua right now... Given a text media object, how can one access the content of the associated file ? I have tried with something like : for line in io.lines(mediaStringTable.Resources[1].Filename) do ... But I get a message saying that "file not found"; examining the emulator folders, I see the gwc file and a log; nothing more, so I guess the message is legitimate, and there is another way of accessing that content.

Thanks. I will try to do so. Before I got your reply, I was experimenting with Variables; worked fine, except the fact it may build up quite a list of strings...

And here comes another question... Does anyone know convenient way of creating a string table ? What I want to do is avoid using duplicate texts; I mean define some sort of string table, much like the ones used in Windows resource files for instance. I guess one way of doing it would be by using a text file with all strings, which are loaded at startup, but how to use them in a Message element ? Maybe this is a practical feature for future releases, too.

compile it, rename the filetype of the compiled file to .zip, unzip it and open the .lua file Thanks. It's going to be an interesting study

This is a great builder. While using it I came across the need of peeking at the LUA source code that is generated; is there a way of doing this ? Thanks.

You can find the romanian geocaching community (or most of it anyway) at http://www.geocaching-romania.ro The local forum can be found at http://forum.geocaching-romania.ro

This is one solution indeed, but how much time would one spend to figure out what GC197TE is about, for instance, if it weren't for the English translation ? The geocaching.com site itself is in english, so why not provide an english translation for caches ? I' not saying that it should be only english, but it is a pretty widespread language ...

Indeed, I have tried google services once, but when you're on the road, with just a mobile device at hand, this is not very practical. On the same note, the google services did not work on the 'printer friendly' page, as it requires login.

I'm not sure if this is the right spot to ask this question, but I did not see an appropriate section of the forum. Being is Austria for a holiday I was looking for caches near my accompdation position; there were quite a few, but to my surprise only a couple had english description. As i do not speak german, this was quite a problem. I'm pretty sure this happened to others with other countries and languages. What's the solution to this ? Shouldn't there be a rule to provide an english translation beside the text in the country's language ? Contacting the owner isn't always an option. Looking forward to get your thoughts on this issue.