Jump to content

SecretSquirrel-BJC

+Premium Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by SecretSquirrel-BJC

  1. The new website layout is much harder to read and understand than the previous layout. You actually get less INFORMATION now in the same space. A step backwards
  2. I really don't like the new page layout. The previous layout was much better and readable. Now, the really important info is crunched up and actually harder to read and digest
  3. How embarrassing. I just went outside and now it doesn't happen. I swear to God it was behaving like this...yesterday evening. Oh well, I will wait and see if it happens again. Perhaps there was something intermittent.
  4. Beta 3.15 I mark a wayoint. Then I go to "Where To?" and it shows that the waypoint is 40 to 60 metres away. Consistently dadgum. I like betas but I shake my head that it seems that Garmin do NO testing what so ever - how can they miss these little things before putting out a beta? Don't programmers test their own code any more?
  5. I would offer but I am heading off for about a week. Don't give up!!
  6. When you put a cartridge up on Wherigo, it edits and replaces the cartridge informational details with the info from the listing. I had a similar problem where the cartridge would compile in the Builder and via the Wherigo.Com compile service, and yet blew up when uploading. The error went away when I changed the text on the listing in one of the description fields but I don't remember what character was the problem...
  7. I have finally published my first Wherigo cache, and I just want to say thanks to all the posts on the forum which have given me lots of tips. So thanks guys!
  8. Garmin advise the problem has been fixed and will be delivered in next release. Woohoo - there really is someone out there listening
  9. Agreed there is no way to make the cartridge completely secure - just enough obfuscation to tip the odds in favour of doing the cartridge in the way it was intended. Getting the unlock code is just way too easy via the back door and there is no way to mitigate it. Well it changed how I am designing the cartridge play I was going to only allow those who actually find the geocache to get a physical code which would then allow them to finally complete the game and get an unlock code. Now this new info means I may as well lower the bar down on the unlock code. I just give it to anyone who plays the game. I have now made it either play anywhere, not get the cache and still get the unlock code or play locally, get the cache (for a find on GC.COM) and get the unlock code The play is identical except for the clues, waypoints and some "proof of being onsite" are slightly different
  10. You can go to some lengths to ensure that an associated geocache can not be found by easily reading the GWC file. However every cartridge can be unlocked on Wherigo by just downloading them and reading the unlock code out of the file. The unlock code should never have been hardcoded into the file by Groundspeak. It should have been allocated by Groundspeak and made known on the Author's page, and then the author could at least have obfuscated the unlock code in the GWC file - if they wanted. So at the moment, Unlocking a cartridge on Wherigo is no indication that it has ever been played. I have just unlocked two very new cartridges like this. Sad! Very poorly thought through - half baked. having said that, I am enjoying a cartridge and hopefully a few people will play it in the field to find the geocache.
  11. I did an experiment and it seems to be playing up when we use the Oregon GPS demo mode but it seems ok in normal GPS mode But that isn't good enough
  12. My crosspost from Wherigo Topics Wherigo changed behaviour under Oregon 2.98 I have been testing my new cartridge on the Garmin Oregon 2.98 Beta version and it has different (worse) behaviour than under 2.97 Beta. In 2.97, when you select an Item in the Inventory, it displays the name, picture and an "actions" button. In 2.98, when you select an Item in the Inventory, it just displays an "actions" button. The name and picture will only appear if you select the actions button and then go back. If you come back down from the inventory again another time, the behaviour remains the same. There was no mention of changes to Wherigo in the beta release notes. I switched back between 2.97 and 2.98 just to make sure I wasn't hallucinating! This even happens on a small vanilla cartridge fully developed in the Builder Is any one else experiencing this issue?
  13. I have been testing my new cartridge on the Garmin Oregon 2.98 Beta version and it has different (worse) behaviour than under 2.97 Beta. In 2.97, when you select an Item in the Inventory, it displays the name, picture and an "actions" button. In 2.98, when you select an Item in the Inventory, it just displays an "actions" button. The name and picture will only appear if you select the actions button and then go back. If you come back down from the inventory again another time, the behaviour remains the same. There was no mention of changes to Wherigo in the beta release notes. Is any one else experiencing this issue? I switched back between 2.97 and 2.98 just to make sure I wasn't hallucinating! This even happens on a small vanilla cartridge fully developed in the Builder
  14. I agree - next time I will go this route for development - less time looking for the typo bugs I just introduced and then put it all in one big file when ready to publish to public.
  15. Thinking out aloud to myself.... Just found out that if I had added the global variable to <cart>.ZVariables then any value changes would have persisted across the save/restore. Doh!! If you don't add it, then on restore, the global variable gets reset to the same value as it had at the start. Very interesting. Stuffing them into another object also worked.
  16. Funnily the emulator wanted the commands listed in reverse order so that they would show up in correct order. Whereas Oregon wants commands listed the other way. Nice that the behaviour is so consistent.(sarcasm)
  17. Thanks - BTW thanks for sharing the source of Whackalackey
  18. Probably another dumb question I read in Whack a Lackey, that arrays and timers are not retained across save-resumes However I have the following issue If I have a variable A defined at the outermost scope of the LUA program, initially set to 1 Then later it gets updated to 2 If the cartridge is saved and resumed, then I would expect it to stay at 2. But it doesn't. Do all variables behave like this? Or is there some special setting/construc that I need to use? PS not using the builder interface except to compile and test PPS My workaround might be to stuff variables inside something that will be retained like an item.name or description etc
  19. Hi Folks using techniques discussed in http://wherigobuilder.wikispaces.com/Reverse+Engineering I discovered that I could use something called CommandsArray to order the item commands how I want itmGB.CommandsArray[4] = itmGB.Commands.zcmdAboutGame -- first on menu itmGB.CommandsArray[3] = itmGB.Commands.zcmdAboutAuthor itmGB.CommandsArray[2] = itmGB.Commands.zcmdAboutBuild itmGB.CommandsArray[1] = itmGB.Commands.zcmdAboutYou -- last on menu
  20. Where can I find out more about Groundspeak open code as referenced below? In Whack-a-lackey LUA, I saw the following -- Another thing from Groundspeak open code -- "hook" the OnStart event for _,v in pairs(_G) do if Wherigo.ZCartridge:made(v) then end end for _,v in ipairs(zcart:GetAllOfType('ZCharacter')) do Besides accidentally stumbling across various methods(? is that the correct word) such as "made" and "GetAllOfType" when they are used in creative commons source code, or stumbling around on the forums, is there some documentation that is available that is fairly comprehensive. I haven't seen these documented at wherigobuilder.wikispaces.com either Thanks
  21. Thanks for the response Expected but disappointing
  22. This is probably a question with an obvious answer but I would appreciate some help When I create 3 commands (say A, B, C) for an item, I cannot guarantee that the commands will be shown in the order of A, B, C It doesn't seem to matter about the name or text of the command or the order in which they are defined. Thanks
  23. I just wrote my first straightforward cartridge and it works perfectly on the emulator. On my Oregon 300, I start the cartridge up, then almost immediately close and save the cartridge. Then I start up the cartridge again, and say that I want to play a saved cartidge. The unit crashes/screen goes black during the restore process. Anyone else having trouble? I tried it with 2.96 and 2.97 oregon software
×
×
  • Create New...