With the tomtom 7 on the diamond the poi's are to small.
How can i make the poi's bigger...
J.P. said:
With the tomtom 7 on the diamond the poi's are to small.
How can i make the poi's bigger...
Click to expand...
Click to collapse
Look in the map folder. There are .bmp files for each custom POI. Just replace them with bigger ones.
I am not sure if this can be done with the build in POIs.
I have the same problem with the pocketgps.com speed camera icons, have changed then to 44x44 icons from 24x24 and hasn't seem to change the size at all, they are still way to small. You need a magnifying glass to see them when they flash on the map
got the same problem really is small considering its a point of interest not a bloody tree! Only way i see the Speed camera poi is having the sound warning on which usually pops up the top left corner what is coming up.
MarcLandis said:
Look in the map folder. There are .bmp files for each custom POI. Just replace them with bigger ones.
I am not sure if this can be done with the build in POIs.
Click to expand...
Click to collapse
I think your correct about the size of the images in the map folder and that you can change the size but its a lot of effort?? If anyone gives it the time maybe they could post the lager bmp images in a zip file??
I have the same problem - especially with speed cameras I think that its mainly because the maps were not designed originally for use on our new VGA screens - the maps are scaled automatically but the bmp images are not - maybe when we see dedicated ver 7 maps for VGA PDA's we'll see an improvement?
I have also button menu and font too small on diamond (vga screen)...
Tomtom icons
I have tried to reduce the size to 20X20, 40X40 and 44X44 but the BMP. are far to small.
(with the wrong size the pictures are red in TT)
Is there anybody who have ONE icon in TT with the right size?
Did you try 48*48?
Blob8me said:
I think your correct about the size of the images in the map folder and that you can change the size but its a lot of effort?? If anyone gives it the time maybe they could post the lager bmp images in a zip file??
I have the same problem - especially with speed cameras I think that its mainly because the maps were not designed originally for use on our new VGA screens - the maps are scaled automatically but the bmp images are not - maybe when we see dedicated ver 7 maps for VGA PDA's we'll see an improvement?
Click to expand...
Click to collapse
Same here.
i don't thing we can do anything for this:
1) maps are not scaled in VGA screen. Infact, a greater area of the map is shown, compared to a QVGA screen (tried on both with two different phones). That is why, the POI icons are small, cos they follow always the 32x32 size. In fact, you will see an area 4 times greater than QVGA screens. Therefore, POI icons look 4 times smaller.
2) If you resize the icons to 48x48 or whatever, TomTom will scale them down to 22x22 automatically (auto-fit) if intelligent enough, becasue that is the size TomTom was designed to display. But it will probably simply not understand the bigger size and just display some rubbish with default resolution of 22x22, i.e., all red square.
Sorry. I see no solution. Maybe by using some overlay third party programs to show POIs and disabling TomTom internal ones. What was it called, "POI warner" I think?
Sorry, but also with 48x48 the icon is to small and only red.
What is de original size?
I must say when I first got my Diamond it was TomTom that I was looking forward to putting on there for the real VGA 'experience' and at first glance I was very impressed... but then I started using it for navigation and, not least given I use it in 2D mode, soon found that everything was a tad too small! I wasn't so fussed about the POIs but it was the map scale overall - at arms length I could hardly see the map detail and really didn't need to see for 10 miles around - it wouldn't be so bad if it didn't zoom out so much.
So, here's how I sort of fixed it.... a kind of workaround which disables TomTom's awareness of it being VGA. The upshot of this is that everything becomes a reasonable scale however the drawback is that it's a waste of VGA and at first glance you might think 'oh my God that's awful - so blocky!' but I soon found that when actually using it in my car I really don't now notice. The blockiness is down to running at a non-native resolution - like all fixed-pixel screens you end up with unclean lines.
Grab yourself a copy of the freeware resource PC tool Resource Hacker, make a copy of the TomTom Navigator.exe file on the PPC, and open it up with the tool.
Now find the resource CEUX\HI_RES_AWARE\2057, right-click it and delete it. It will likely take the whole branch with it if it is the only entry in there. Now save the resulting file (I got an error at this point - dunno if it's Vista or what but it still seemed to work) and copy the file back to the PPC (note it makes a backup so make sure you get the right one!) - you might want to call it something different so you can then have a choice of VGA or non-VGA TomTom's to run.
And that's it... I'm sure when you first see it in action you'll think it's horrible... but in use I think it is fine and indeed for me makes it at least usable once more.
Mathew
Wow nice trick man
POI's are now bigger but OMG this is very ugly lol !
Need anti-aliasing
Its nice but there are some bug for the text display
I actually find it okay when at arms length!
What were the text bugs you mentioned? (I must confess I've only used it a few times since doing this so could well have missed some major showstopper!)
Mathew
MJNewton said:
I must say when I first got my Diamond it was TomTom that I was looking forward to putting on there for the real VGA 'experience' and at first glance I was very impressed... but then I started using it for navigation and, not least given I use it in 2D mode, soon found that everything was a tad too small! I wasn't so fussed about the POIs but it was the map scale overall - at arms length I could hardly see the map detail and really didn't need to see for 10 miles around - it wouldn't be so bad if it didn't zoom out so much.
So, here's how I sort of fixed it.... a kind of workaround which disables TomTom's awareness of it being VGA. The upshot of this is that everything becomes a reasonable scale however the drawback is that it's a waste of VGA and at first glance you might think 'oh my God that's awful - so blocky!' but I soon found that when actually using it in my car I really don't now notice. The blockiness is down to running at a non-native resolution - like all fixed-pixel screens you end up with unclean lines.
Grab yourself a copy of the freeware resource PC tool Resource Hacker, make a copy of the TomTom Navigator.exe file on the PPC, and open it up with the tool.
Now find the resource CEUX\HI_RES_AWARE\2057, right-click it and delete it. It will likely take the whole branch with it if it is the only entry in there. Now save the resulting file (I got an error at this point - dunno if it's Vista or what but it still seemed to work) and copy the file back to the PPC (note it makes a backup so make sure you get the right one!) - you might want to call it something different so you can then have a choice of VGA or non-VGA TomTom's to run.
And that's it... I'm sure when you first see it in action you'll think it's horrible... but in use I think it is fine and indeed for me makes it at least usable once more.
Mathew
Click to expand...
Click to collapse
Anything similar for iGO 8?
I didn't think iGO8 had any issues re size/legibility on the VGA screens?
It works fine, the black popup right above in the screen with the text (for example "no GPS") is to large. But thats not a big problem because it's not mention when you navigate.
MJNewton said:
I actually find it okay when at arms length!
What were the text bugs you mentioned? (I must confess I've only used it a few times since doing this so could well have missed some major showstopper!)
Mathew
Click to expand...
Click to collapse
Well, when you check how much satellites your GPS found, the numbers are displayed bigger.
And on the main screen, the speed indicator number is smaller than "km/h" .
But still nice
Great solution! Thanks.
It seems that TomTom 7 isn't really VGA-ready. Any news on an update?
Think it's very bad for business to offer such a bad solution for VGA screens, which are coming more and more.
Related
I searched through all of the free traffic cam data bases and found a few FREEWARE TXT files with 2455 different Traffic Camera POI's. I edited the files as a .CSV in Excel and then used TomTom's Official unsupported TXT -> OV2 software to convert them to OV2 (TomTom's format). Then copied the files to the directory containing my maps of the USA, then went into TomTom and enabled SPEEDCAM as a POI. Then I went into the Preferences and edited the POI for SPEEDCAM to warn me when ever I get within 300yards of one.... NICE!
Attached is the Traffic Cam POI's, TomTom's own conversion software, and a few more POI's I found as freeware.
Ron
The USA has speed cams?
yup, usa does have them.
Very nice man. Much thanks.
nice
thank you
grizzley said:
The USA has speed cams?
Click to expand...
Click to collapse
In my area, they have Red Light Cameras... They are a BIOTCHS! You cannot fight it in court, numerous pictures, and a high quality video of the entire act. The police come in with computer video presentations and show everything... and they will do 10+ people in a row... very lucrative for the city.
Ron
wow. I didn't know these were out there! Are they in cities or on the Interstates or both????
Just installed and ran TomTom on my latest trip. What a nice surprise to find that the red light cameras in Germantown (near Memphis) are included! I'd guess the same could be said for other red light cams as well.
Thanks!!!
cool find and work. Gonna try it out.
I know of some that aren't showing up. Let me know what to send you to get them added.
Traffic Light Cameras in L.A. - Yup!
Installed and intentionally drove by a red light camera in Los Angeles (Melrose & La Cienega for those who care). It absolutely showed up!
I believe, based on when the alert actually went off, that I will reset to advise more in advance than that suggested in the first post.
chop249 said:
I know of some that aren't showing up. Let me know what to send you to get them added.
Click to expand...
Click to collapse
You can add them to your TomTom under Change Preferences > Manage POIs > Add POI. If you want to post the Red Light coordinates I could add them to the database.
Post coordinates to new POIs like this:
Red Light Camera 21.37861, -158.14242
Thanks,
Ron
lokmeup said:
You can add them to your TomTom under Change Preferences > Manage POIs > Add POI. If you want to post the Red Light coordinates I could add them to the database.
Post coordinates to new POIs like this:
Red Light Camera 21.37861, -158.14242
Thanks,
Ron
Click to expand...
Click to collapse
Great I'll get the new ones posted here in the next few days.
lokmeup said:
I searched through all of the free traffic cam data bases and found a few FREEWARE TXT files with 2455 different Traffic Camera POI's. I edited the files as a .CSV in Excel and then used TomTom's Official unsupported TXT -> OV2 software to convert them to OV2 (TomTom's format). Then copied the files to the directory containing my maps of the USA, then went into TomTom and enabled SPEEDCAM as a POI. Then I went into the Preferences and edited the POI for SPEEDCAM to warn me when ever I get within 300yards of one.... NICE!
Attached is the Traffic Cam POI's, TomTom's own conversion software, and a few more POI's I found as freeware.
Ron
Click to expand...
Click to collapse
Great work ! the thing that doesnt work is USA Speedcam TomTom.zip picture it shows a red square ! other than that awsome
little help on enabling cameras as POI
I go to settings but the enable/disable poi is grayed out, how do fix this?
jrdejavux said:
Great work ! the thing that doesnt work is USA Speedcam TomTom.zip picture it shows a red square ! other than that awsome
Click to expand...
Click to collapse
Yeah... that bugged me for a while. I even found a cool BMP for the icon, but TomTom wont use it. So, the red warning square is good enough for now. The BMP icon is included with the USA Speedcam TomTom.zip file. So, if someone gets it to show up properly in TomTom, Let us know.
Ron
lokmeup said:
Yeah... that bugged me for a while. I even found a cool BMP for the icon, but TomTom wont use it. So, the red warning square is good enough for now. The BMP icon is included with the USA Speedcam TomTom.zip file. So, if someone gets it to show up properly in TomTom, Let us know.
Ron
Click to expand...
Click to collapse
Resize it to 22 X 22 instead of the 32 X 32 you have it at. I did it but as a crop I couldn't get it sized down maybe you have a better program than I do.
tag for later
Here is an update with 5 new cameras in the DFW area that I know of. I think there might be a few more, I'll keep my eyes peeled! When I added them I just left them named as the intersection where they are located.
Bob
chop249 said:
Resize it to 22 X 22 instead of the 32 X 32 you have it at. I did it but as a crop I couldn't get it sized down maybe you have a better program than I do.
Click to expand...
Click to collapse
Nice job! 22x22 BMP attached. Just copy it to your map folder.
Ron
Hello all,
I don't see that good anymore and I wonder if anyone know how to increase the size of text font of the anotations (places and road names) in google maps.
Thanks.
I have been searching for the same answer. It seems VGA support is very lacking when it comes to GPS software. I use both Google maps and Windows live search maps and now that I have my Touch pro the font and icons are too dang small to see at a glance.
same problems with HTC diamond
I have the same problem with google mobile maps on my htc diamond - got the car holder et al and then realized the font size is way too small. Its impossible to read anything from the driver's position.
If font size can't be increased, maybe some kind of a screen zoom software might help??
Google Maps / Live Search font size too small on Fuze
Here here! I too just upgraded to the Fuze. I love the high-resolution screen, but now the font size for street names and such in both Google Maps Mobile and Live Search Mobile is just a joke! It's way too small. Impossible to read while driving. I know there's a " preferences.xml " file for LSM in its folder in Program Files, but I don't know what tags (if any) apply to the font used. Need a fix!
Welcome to getting old. Wish I had good news but my experience is that I keep getting older and more pathetic by the day. At any rate I also have been keeping my ahem eyes open for a fix.
as a temporary fix, you can increase the system font size found under settings>system>screen>text size tab...it will make the fonts larger in google maps after a restart of the program.
Problem is, this method increases the size of text everywhere in your phone, which can be big doo-doo.
Yes, google or a coder from XDA would make a lot of folks happy with a fixeroni for this.
i tried but increasing the font size under system settings does nothing to google maps - it only increases the font size in sms/email/etc
wrong font used in Google Maps Mobile
Earlier versions worked fine on my T-Mobile MDA, but in Google Maps Mobile version 2.3.0.9 and 3.0.0.2, a different font is used for "tooltips". Context menus or main menus are OK. What's worse for me is that it has chosen to use a Greek font that was installed by a Bible program I use. I have attached some screen shots.
Google Maps 3.0.0.x uses very sophisticated algorithm to determine which font should be used.
It gets list of fonts from all folders on device, then sorts them from Z-A and then takes first one.
Cool, isn't it?
So, first thing to try is to copy 'Tahoma.ttf' (usually in Windows folder) to new file, 'zTahoma.ttf'. It fixed problem for me.
Problem also occurs when installing Microsoft Reader. It installs WingDings font on Pocket PC. W is closest to Z, so Wingdings is used as a main font. Looks great.
Hi all,
I have Memory Map with all the UK at a scale of 50k. Problem is that they're devided into 12 regions, each file being between 200-400MB. My Touch Pro won't open any of them, MM gives an error saying 'unable to load' type error. After some research it seems that the files are too big for it to open, even though MM say try to keep the file sizes below 400MB (which they are, give or take). I can send visible screen capture maps from my PC which do work kinda confirming that it is a size issue.
Does anybody have any suggestions in solving this. As I really want all regions on the phone as a resource without having to consider where i'm going before hand and uploading just that portion or route.
Thanks.
No solution I'm afraid, just confirming that it looke like a file size issue... I tried copying via both Activesync and direct to disk in case it was that. 120Mb seems to open OK, which covers all of north Wales... I used MM on my Wizard too but never tried copying a whole tile over due to lack of storage, so I don't know if it's a hardware limit or an application problem...
Ok. thanks for confirming that.
It's a shame MM dosn't allow you to zoom out further as it would be possible get extracts at the limit of the file size possible to load and then build your own tiles of the UK. As it is, this would be far too time consuming at the current zoom extent.
Organic99 said:
Ok. thanks for confirming that.
It's a shame MM dosn't allow you to zoom out further as it would be possible get extracts at the limit of the file size possible to load and then build your own tiles of the UK. As it is, this would be far too time consuming at the current zoom extent.
Click to expand...
Click to collapse
If you can get hold of the 1:600000 road map you can use that to zoom out further. The higher resolution maps you have will appear as green outlines. You can then subdivide your 50k maps and save them as smaller, slightly overlapping sections by drawing a closed route on the low-res version of the map. Then increase the resolution, right-click on a line of the route, go Operations->send enclosed map to mobile device then choose a place to save the map (does not have to be on your PPC so you can transfer quickly later). Of course because of the overlap the total amount of storage for the whole of the UK is greater... it's a bodge but it's better than no maps at all
Cheers,
Tim
I can confirm that the Touch HD has the same problem, maps over about 120MB dont open. Maps 100-120MB sometimes work sometimes dont Interestingly The maps and sizes are exactly the same as I have previously used on both an original Touch and and MWG Atom Life without any problem. They didn't give a problem untill the file size got considerably bigger. Wonder whats different on these newer phones?
Procedure To Edit The Internet Globe Button Manila Files
(No more solid white blank buttons)
7d3f1247_manila - Globe Unselected
3f00cd2f_manila - Globe Selected
What:
With this procedure you will be able to select any graphics or highlight color you want to use for both the selected and non selected states of the Internet globe button.
How:
There are no special tools required other than Manila Editor 0.2 and a graphics program that can work with png files. You will need to know how to use both of these programs though.
Advantages:
The biggest advantage over editing either 27c65cbd_manila or InternetPortal-en-US.xml would have to be speed. When I tried that way on my Fuze it would take well over 5 seconds to load every time I scrolled to the Internet tab. Sometimes almost double that on a fresh boot. Second advantage would be that this *should* work on any device that uses those 2 files, where the xml edits are different files for different devices. Which leads to the third advantage of not needing special install instructions for theme makers. Edit the manilas and drop them in with the rest.
Other Info:
(Just skip this part if you don't care about the why and scroll down to the instructions.)
I have literally scoured these forums and the Internet for days trying to find information on editing not only the Internet globe manila files, but the other 7+ files that just don't work right with Manila Editor. Most theme makers know of these files. Mostly what I found was a lack of information and more questions than answers. The only other procedure I could find at all for converting manila files gives better results than using Manila Editor but it's very complex for the average user requiring command line tools. Even so the author, (Chainfire) has written a damn near fool proof tutorial so if anyone is interested you can find the thread HERE. Unfortunately even that procedure would not handle the problem manila files properly and quits with the following message.
Reading file: 5c01b59c_manila
Error: file is not QTC format
For reference, this is the list of files that I know of at the moment with this problem, and all return the same error except for 7d3f1247_manila. (More on this file to come.)
7d3f1247_manila - Globe_Unselected (512x256) 28.5k
3f00cd2f_manila - Globe_Selected_D (512x256) 64.5k
40ec2415_manila - Small Avatar_D (64x64) 2.5k
2f411611_manila - Exclamation Point_D (256x256) 32.5k
4d97cac6_manila - Add Contact_D (256x256) 32.5k
54e0759d_manila - Contact Avatar_D (256x256) 32.5k
400b663e_manila - You Tube_D (64x64) 2.5k
55cc771a_manila - Selection Highlight Bar (512x256)64.5k
5c01b59c_manila - Contact Avatar2_D (256x256) 32.5k
The first oddity I noticed when using Manila Editor on the Globe file (3f00cd2f_manila) is no mater what size my graphic was before running it through, it always came out to be approximately 125k. Since the stock file was roughly half that size I knew something was really wrong. The other glaring anomly with most of the files is they show up as duplicated (side by side) images when viewed with M.E. so I figured that somehow all of this must be connected.
I am not a programmer by any stretch but I know just enough to get me into trouble most of the time. Anyway I loaded both files into Notepad++ and turned on hex view to see what was so different. The header of both files were similar but not exactly the same so I copied chunks of the problem file from below its header and pasted it into the good manila at the same address location. What it produced was a repeating pattern on the top left corner of the stock green button but every other row was white. I don't know why but the fact that the image repeats in M.E. as well and the file being double the size made me think to cut the image in half and try to see if M.E. would accept it. It did and I was elated to finally see an image on my phone other than than the big white rectangle.
I had an image that was really distorted but it wasn't difficult at this point to see what was going on by the way it was distorted. I was able to get a perfect button on my next try by creating my image on a 256x128 canvas and then scaling it to 512x128. It looks really bad and stretched out at this point but after processing with M.E., the phone will compress back to it's original aspect and it looks just perfect. I use The Gimp as my image editor and just save as a png file with the default settings.
Now that I Finally had a working selected globe image I wanted to change the static globe as well. (7d3f1247_manila) This was a whole new battle but at least I had something to work from this time. There are some significant differences in this file compared to the selected globe. First, it looks perfect when you extract it using M.E. which led me to believe that this would be easy. I couldn't find much info on this particular manila and I think I know the reason why. Either people are replacing both images via the xml workaround, or they are just concerned with getting the highlight the right color on the selected image. Either way, when I tried to do a 1:1 replace in M.E I got to see the wonderful white rectangle again. At this point I had finally gotten all the tools working from the post I mentioned before and decided to try this file using that procedure as it should return better results if it did work. It worked perfectly but I still wanted to get it to work using M.E as most people are not going bother with a long drawn out procedure.
After playing around some I found that if I scaled the 512x256 image to 256x256 it worked perfectly. The up side is the file size is half of the stock image. The down side is the resolution is obviously cut in half. It's really not a show stopper but using the other method does produce perfect results. Not completely satisfied yet I tried some more images at different resolutions to see what happened. The 480x240 image I had from one of the globe mods that are floating around produced a white rectangle. I then decided to try another unscaled image that was almost completely transparent and it worked without a hitch. Now that I was completely confused I went back and tried the original 512x256 that produced the white and it did so again. It wasn't until I switched to another tab and back again that it finally showed up correctly.
So what does it all mean? Hell if I know but at least the scaled 256x256 method seems to work every time without any problems and its fast to boot. The long procedure would be the best method of them all but probably not worth the effort for most. As far as the other problem files go I guess I'll try and work them out too unless someone else more capable picks up the ball and runs with it. The selected globe was the particular image that stuck in my craw and got me started on this.
Instructions for 3f00cd2f_manila - Globe Selected:
1. Create your image at a size of 256 x 128 exactly how you want it to look on your device.
2. Scale it to a size of 512 x 128 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs. This will distort your image badly but do not fret. Yet.
3. Fire up Manila Editor as usual and use your new image. Now you can fret as you wait to see if this works or not.
4. <-- I hope
Instructions for 7d3f1247_manila - Globe Unselected:
1. Create your image at a size of 512 x 256 exactly how you want it to look on your device.
2. Scale it to a size of 256 x 256 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs.
3. Fire up Manila Editor as usual and use your new image.
General Notes:
If you don't want to mess with any of this and like what's in the screen-shots attached, you can install the cab or just unpack the zip into your windows directory on your device. As always, please back up your files before adding new software.
Notes concerning 7d3f1247_manila:
This procedure *should* work if done as stated. If you use the alternate method I linked to in the info section above you don't have to scale the image and will get a higher resolution image. I have successfully used a non scaled image before with Manila Editor but it goes white on first load after a reboot then somehow clears up. With the scaling method I've yet to see the dreaded white rectangle. Read the info section for more information.
More Information:
Manila Editor 0.2.0
Editing Manila
Manila 3D Porting
Pixel Perfect TF3D ***
Manila Fine Details
Cheers,
Eidolen
*Disclaimer*:
Obviously I can't test this on every device but I can't think of any reason why this wouldn't work on any TF3D enabled device. If this doesn't work for you, feel free to post here or contact your congressman. (Where applicable) If this helps anyone please be sure to drop in and say hi.
There is some real development going on about this subject over on the pixel perfect thread. If you are just looking for a quick fix then what I posted above is still relevant but you might want to keep an eye out for a *real* fix as I doubt it will take them long once they sink their teeth into it.
I believe they already figured out that you can patch the header on the problem files to correct the payload size which should work also. If you are not so technically inclined then the method posted here still works flawlessly for me and should for you as well.
I've added a picture that might help if the directions above were confusing at all, so it might help clear it up. You can find the link to the Pixel Perfect thread right above this post.
Cheers,
Eidolen
I'm sure others have come across this...
My carrier's limit on sending MMS is ~300KB. Our 3.2mp pictures are much larger. That and most people I want to send MMS's to don't have a 300 by whatever + resolution screen on their phone.....
So I'm looking for a simple, easy to use, app that will just resize images for me. I know the MMS software in most ROM's will auto-convert them to some sizes, but I'd rather just save the images at that size to begin with... and send that smaller file myself (also good for uploading to ftp servers to share via e-mail to other mobile devices)
I did some browsing, and i saw maybe some versions of HTC Album do resizes... but I'm not really looking to update that yet... most other google searches around 'pocket pc paint' or 'wm6 image resize' end up with themes and the like -- I need an on-phone solution.. I don't want to be tied to a computer to resize an image!
searches:
http://www.google.com/search?q=wm6+...s=org.mozilla:en-US:official&client=firefox-a
http://www.google.com/search?hl=en&...ficial&hs=aGH&q=wm6+resize+photos&btnG=Search
http://www.google.com/search?hl=en&...ficial&hs=7vb&q=ppc+resize+photos&btnG=Search -- came up with some results, but I've never haerd of a lot of these solutions, any feedback?
hmm, did you want the original picture to be 3.2 MP? If not, then just take the picture at a lower resolution?
Other than that, although I have not played around with it, an app called Photogenics may be able to do it. Keep in mind though, it's not freeware.
Resco Photo allows you to downsize photos. You can select what pixel size you want, or type in a percentage. Its does a lot more stuff too, its not free though.
I have AT&T and they limit mms to 600k. Is that your carrier as well?
Motorious said:
hmm, did you want the original picture to be 3.2 MP? If not, then just take the picture at a lower resolution?
Other than that, although I have not played around with it, an app called Photogenics may be able to do it. Keep in mind though, it's not freeware.
Click to expand...
Click to collapse
I like taking high-quality pictures in case I want to share them by e-mail / upload them, or save them for later use as something..
But I also want to resize them for friends when i send it to phones. and at&t requires it to be smaller in size to send via MMS... as another poster mentioned.
Cropping would also be nice... I was mainly looking for a free solution, but If i gotta pay I gotta pay.. I prefer donating to developers here over paying for product from companies though.
The authors of XnView (a freeware ACDSee clone) have recently published a version for PocketPCs and Windows Mobile Smartphones. It works very well on my Touch Pro. Allows retouching, resizing, modifying colorspace, batch conversion to many formats and more.
http://www.xnviewpocket.org/
Photo Resizer
ยป PhotoResizer v1.0 Description
With PhotoResize you can copy and resize JPG images from a folder to another selecting the quality and output size of target image.
This tool is useful when you want to copy your photo from your camera to your PDA and show them at your friends using a PDA as photo album. (As I usally do)
The main problem is that every single image done with your camera (depend wich camera you use) is usually several megabytes and if you simple copy photo from camera in few time you will finish the memory available on your PDA.
With this tool you can reduce the space on each photo resing it to the dimension of your PDA screen (usally 320x240, 320x640, or 640x480). In this manner the dimension of files are drastically reduced and you can show images directly from PDA. During the conversion phase a progress bar will show you the percentage of work, if during conversion will be found an image with dimension less then the output size, that image will be skipped.
Funcionalities:
* Select source folder and destination folder graphically
* Choose target size of images
* Choose quality (default is 75%)
* Choose if you want to see the thumbnail during the process (this option can be time comsuming)
the PhotoResizer v1.0 free for Pocket PC