matejcik

if you didn't understand our explanations,, this part of the builder tutorial should help :e) http://www.Wherigo.com/tutorial/index.aspx#Obj2-2 if you did that and still have problems, perhaps it would be best if you put the cartridge source (the .lua file) into a zip file and uploaded it to the forum. then we can tell you what's wrong

did you create the cartridge? if yes, please read again carefully what i and cantuland posted above. if not, contact the cartridge creator and tell them to fix the cartridge

i'm lost. what were you talking about again?

my guess is never. that, or sometime during this fall or winter i'll do a desktop version of openwig (it's pretty tough to connect to a GPS on a desktop, you know? there is no standardized API, unlike on phones or PPCs)

you're using OnClick. don't do that. instead, define a command on the item and do whatever action you wanted when that command is clicked

alright, how about this. every one of you has played the tutorial, right? the tutorial uses a dynamically generated zone called "LandingZone", which has an OnExit and OnEnter events. when you picked up the energy crystal and returned to landing zone, did you have to "zero in" on some specific point?

eh, why do i bother. well of course you have to zero in on the zone. the event can't fire when you're not in the zone yet. point is, you shouldn't have to run around back and forth to find the zone's entry point. look. colorado's (and any commercially available gpsr's) accuracy, under the best conditions, is around 20 feet. when conditions are worse, it can easily be 40. that basically means that if you're unlucky at the time of playing, you have to walk as far as 40 feet inside the zone shape you drew on the map. which is over half the size of your 75ft zone. this, as opposed to "zeroing in", has a consequence, though: the whole zone shape appears to be shifted by that inaccuracy. you can easily test that, by approaching the zone from different directions. if the zone shape is working, you can enter the zone on many different physical places. or you can walk through the zone. if you really needed to zero in on a point, in all likelihood you wouldn't be able to stay inside the zone. the gps noises would throw you in and out randomly. the fact that you can stay safely inside, and that you can deliberately exit the zone on its other side, means that the zone shape is there and it is recognized. so. if you are really seeing the symptoms of geocaching-like need to locate a jumpy "zero point" and staying motionless on that very spot, please do me a favor - send me a gwc and a gwl log of that cartridge. i want to see it too.

well, since the only discussions are on this forum, google wouldn't help you that much anyway. you might try "site:forums.Groundspeak.com" though. the closest we have to documentation is the wiki at wherigobuilder.wikispaces.com. sadly, no official api docs are available. pretty much the best you can do is read the source of something generated by builder, you can infer a lot of useful information that way.

thanks. as you can see, the zones in the Clarence cartridge are so tiny that they don't even look meaningful in google maps' maximum zoom (all but the first are deformed, because the points are too close for google to differentiate - or maybe because there is some bug, i can't tell now, but the coordinates are right) - from a standpoint of basically any GPSr available, they are points. if you want, you can send me a gwc or sourcecode of your cartridge, i can do a similar map for you. (if you don't want to upload it publicly, send it to my mail - my username at gmail.com)

put it in a zip. that should work

okay, i want to see it. would you be so kind and upload a gwl logfile from some cartridge you tried?

goes ahead all the way ;e) it's like this: whenever you call a function that is supposed to show a message or input on the screen, it shows it immediately. if there was something displayed before, it is cancelled. that means that if you are in the middle of viewing a dialog, and e.g. a timer event fires, the timer might cancel your dialog if it shows a dialog of its own. you can detect that your messagebox or getinput is cancelled, by writing a button script and testing for button "cancel" pressed one way of achieving what you want to do is using messagebox with a button script, and only setting correct=true in that script. (if your dialog is longer than one line, i suggest using my author script that allows you to "accumulate" messages instead of displaying them over themselves). another way is doing something like if (task.correct) then (show your messagebox) else (set task.correct = true and rely on the OnSetCorrect event to show the messagebox). also, did you know that the OnSetCorrect/OnSetComplete/OnSetWhatever run before the value is set? it is set immediately after the OnSet script finishes, but if you set task.correct = true, in the OnSetCorrect you still see it as false

ah, right. builder copies the old file with the extension .bkup, right? by "make a backup", we usually mean "copy the lua file to a different name and don't rely on what builder makes"... i don't think that anyone will be fixing builder bugs anytime soon - even if Groundspeak suddenly decided to start working on Wherigo full-time, there are more severe problems to deal with (broken downloads from Wherigo.com spring to mind)

get yourself a diff program and compare the backup and the new version. this one looks good. then you might find out what went wrong. also, maybe close and reopen the whole builder before loading the backup?

not really interesting ;e) that's how messages work. that's also the reason you can't use messagebox, dialog or getinput multiple times in one script, they would just cancel each other.

this sounds interesting - care to send me a gwl file to check it?

100 chars shouldn't be a problem. is there something interesting you do in the zone's OnEnter event? showing some screen, running a special command (are you setting the status text? that might be it - it's known to work only on PPC, it might just as well crash your nuvi)

no limit was ever measured precisely (you can do it if you want ;e) ), but some people were talking about 500 or 1000 characters, i think... general consensus is that you should not put more than a screenful of text into one messagebox or dialog line. screen size is pretty good guideline - if you have to scroll for more than half screen, it's time to split the message into more dialog lines. i don't know of any limit for number of lines in a dialog

i think that it works even if you don't leave out the leading and trailing braces, i remember doing something along the lines of [[Welcome ]]..Player.Name..[[ and have a good day]] and it did work. i thought that the builder was being smart and when it saw the opening braces, it switched to explicit mode

and one gotcha: in all players (including the emulator), when an input is on screen and a message box is displayed from timer, it crashes the cartridge

THE HELL! THIS IS NOT TRUE! i've discussed this with many people and now i'm reasonably sure that this is a myth. now it might've been the case with older player releases, but with the newest player version 2.11, which has been out for more than a year now, zones work just fine. (not sure about horseshapes, because the shape recognition is a teensy bit flaky, but wall-types and convex shapes work reasonably well). i dare you to prove me wrong

don't use OnClick events at all! they're evil (no, they don't work on characters either. or zones or items, for that matter)

try this: http://Wherigo.geoteam.info/zone_creator.aspx user's guide: 1. create zones with dummy locations ("create from address" or something) 2. save and close builder, make a backup of source, open source in text editor 3. for each zone: 3.1. locate the snippet mentioned on the page ( zoneMyzone.Points = { ... } ) 3.2. use the page to draw zone shape. (click the map and you'll see how it works) 3.3. to locate your address, use the search box above the map labeled "vyhledávání", then click "ukaž na mapě" 3.4. to delete last point (aka undo), click "smaž poslední ťuklý bod" 3.5. to delete the shape and start over, click "smaž vše" 3.6. when done, copy the points list from the textbox below the map into your source, replacing the original Points snippet. 3.6.1. don't forget to use the name of your zone! if your zone's lua name is zoneMyZone, copy the points list and then change "zone.Points" to read "zoneMyZone.Points" 3.7. then click "smaž vše" and continue with the next zone 4. save the modified source 5. open it in the builder 6. if you did everything right, you should now have your zones

or just set them to visible by default

simple. first, create the items second, click Cartridge, switch to Events tab (or whatever it's called), edit script for When the cartridge is started, and insert commands to move all your items into the zone where you want them to show.