Taking photos; duplicates and size + a few bugs in .496

[m1m3r]

Yet again I'm sorry if this has been discussed elsewhere but since I'm not that fluent in German it's hard to make a decent forum search.

I've started taking a photo at every cache and love the way they are being saved with the cache name and GPS position embedded. However, the photos are so very small and there are always two photos saved, one with position data and one without.

I would like to be able to set the photo resolution and that a photo without position data should only be saved when there's no GPS fix.

Also, in .496 I've encountered a couple of bugs.

The cache focus no longer automatically changes when getting closer to a new cache, the red frame stays put on the last one you manually selected.

If you want to delete a photo that you've just taken a nasty error message (sometimes) appears. Looks like it's from WinMo and not from Cachebox - however I can't replicate the error right now so I can't tell what it says...

 

[ersthelfer]

However, the photos are so very small and there are always two photos saved, one with position data and one without.

I would like to be able to set the photo resolution and that a photo without position data should only be saved when there's no GPS fix.

Right, there was two pictures taken, because sometime you need a picture without GPS-data, like for a final photo of a multicache. Therfor a GPS picture was a spoiler.

The photo resolution was readed out of the registry. At the moment ther is a bug. But it was corrected at the next version.

 

[GeoSilverio]

...
The cache focus no longer automatically changes when getting closer to a new cache, the red frame stays put on the last one you manually selected.
...

Actually I don't know exactly how it works. But I think to set the fous automatically always to the nearest cache is also uncomfortable.
For example: If you're doing a multicache, walking around from one stage to the next and suddenly cachebox focuses the next, nearest cache (let's say a traditional). That's annoying.

I think the behaviour is, that cachebox resorts the cachelist if you have no cache manually selected and the "Auto Resort" option is set. If you select a cache manually, no further resort is done...
Perhaps one of the developers can explain it better?

 

[Inder]

The cache focus no longer automatically changes when getting closer to a new cache, the red frame stays put on the last one you manually selected.

If you want the focus autmatically set on the closest cache, please activate "DB"->"AutoResort"
The function is disabled once you select one cache manually. You have to enable ist again after manual selection.
This setting will not be remembered after restarting cachebox. You have to start it manually every time, you use cachebox. We are just discussing this "memory leak" in a german thread.

 

[GeoSilverio]

"memory leak" sounds like a major bug....

 

[m1m3r]

The cache focus no longer automatically changes when getting closer to a new cache, the red frame stays put on the last one you manually selected.

If you want the focus autmatically set on the closest cache, please activate "DB"->"AutoResort"
The function is disabled once you select one cache manually. You have to enable ist again after manual selection.
This setting will not be remembered after restarting cachebox. You have to start it manually every time, you use cachebox. We are just discussing this "memory leak" in a german thread.

Thanks, I already knew this and it worked perfectly in the last build.

 

[m1m3r]

But I think to set the fous automatically always to the nearest cache is also uncomfortable.

Yeah, that would be useless. The way it worked before 496 was perfect, once you manually selected a cache the focus was locked on that one until you activated "auto resort".

 

[m1m3r]

Right, there was two pictures taken, because sometime you need a picture without GPS-data, like for a final photo of a multicache. Therfor a GPS picture was a spoiler.

Never thought of it that way, makes kind of sense. Removing embedded data from a image file is on the other hand an easy thing to do. Best of all would be if there was a setting for this as well.

The photo resolution was readed out of the registry.

I've searched the registry on my phone but could not find any related registry items - where would this key be?

 

[rstweb]

The photo resolution was readed out of the registry.

I've searched the registry on my phone but could not find any related registry items - where would this key be?

The resolution is stored at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Pictures\Camera\OEM\PictureResolution

But it would be better to wait for the new version. There the detection of the highest possible resolution is added and it works perfectly

 

[Inder]

"memory leak" sounds like a major bug....

It is ...

 

[m1m3r]

The resolution is stored at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Pictures\Camera\OEM\PictureResolution

Not on my phone (HTC TD2 with WM6.5), this is the only key present;

[HKEY_LOCAL_MACHINE\Software\Microsoft\Pictures\Camera\OEM]
"SupportedVideoFormat"="*.wma;*.wmv;*.mp4;*.avi;*.3gp;*.3g2;"

But it would be better to wait for the new version.

I will. Any idea when it'll be released?

 

[rstweb]

You have a PM.