by Battlegrounds Games, LLC
@David, I'll do further testing to see if something in the rescaling code is failing and causing this error. That seems like a likely culprit. The fact that the error occurs before the bitmap is exported (and not when it's restoring things back to the normal DPI) tells me where I should look for the problem.
Unfortunately I am going to have to report this on another (large, time consuming) map as well. I created it at 50dpi, and tried to export at 200, but got the 'Four parameters expected' error, and then no export. I had no errors pop up during the creation of the map, so I don't think there is any possibility of it being corrupted. I'd love to be able to actually get this exported because I don't want to have to redo the who thing.
Update: Trying to export at 50dpi worked, so there is an upscaling issue.
Hrm. I was just putting together a map and I must say it was much faster and smoother than in previous versions. I set the resolution to 50dpi, and between that and the improved refresh everything was going great. I also used "select all" which was quite nice.
However when I am trying to export (and scale back to 200dpi) I get the following error: "Four parameters expected", at which point it doesn't export but just sits at the export screen. This is both with and without smart sharpen selected, and either png or jpg format.
If I rescale the map before export I am winding up with the same error actually, so maybe my map is corrupted? I'll have to try on a different one tomorrow.
@David (this is starting to look like a David convention, LOL!), some good suggestions for Preference settings, thanks. I can also add some settings for default grid overlay parameters for new maps. And default resolution (e.g. Roll20 users might prefers to always default to 140 dpi). I imagine most everything in the Map Settings could be autofilled by a user's prefs settings.
Sounds great!! Suggestions for Preferences: default Save path; default Export path; default tile set selected - including default section (tiles, textures, or items).
That sounds good, I'll definitely be testing that out once you start implementing it.
@David Bettsack, drawing tools (including the use of textures) are slated for v1.1, but I will likely start implementing them in v1.0.7. Just don't expect them to be fully functional right away. It'll be an incremental process, I'm sure, and the next couple of releases will probably never make it out of beta. They'll be more of a work-in-progress.
@David Ross, copy or move the contents of your current MapForge installation's "Add-Ons" folder to v1.0.6's "Add-Ons" folder. If you've been using v1.0.4 or later, you might also want to move or copy over the "Cached Thumbnails" folder found in the "Support Files" folder, so that the new version doesn't need to re-create the thumbnails again (the result of doing so is faster launch time).
Looks like a great update! I'm excited to try making maps in low res and exporting them in high res - it seems like such a basic idea I'm thinking "Why didn't I suggest that?"
Any rough/vague ETA for drawing? That seems to me to be the last major feature MapForge is still missing.
Is there anything special I need to do to make sure my add-ons from one version to the next are available? Thanks! Looking forward to this update.
What a great update :)
It's a shame I am on vacation now.
By the way, MapForge now comes with some files in the "Maps" and "Exported Maps" folders, whereas those were always empty before. The additions should be particularly useful to new users evaluating the software.