by Battlegrounds Games, LLC
@David, Confirmed that the map canvas isn't always resizing to the user's specifications, under Windows. Will fix for v1.0.5.
@David, It should automatically be increasing the canvas size. I'll look into it, especially under Windows.
Sorry for the slow reply, I wanted to try something.
To answer your question, no, the errors have all been on newly created maps. After reading your reply I tried loading some old maps and they wouldn't even open. What I was trying is as follows: Although I didn't notice this at first, MapForge defaulted to the 8k canvas for me, so when I started making a new map I changed the map dimensions to 42x42, and hit apply. It turns out that this didn't actually change anything, the map was still 40x40, but I didn't notice that until I exported it. I thought perhaps because I put in a value above the canvas size that might have been causing some error. On trying a new map at the 10k size I still have the same error, so that is not it. BTW, I think if you try to put in a map size above what your canvas supports it should either tell you that is too large, and to increase the canvas, or else just automatically step up to the next larger size.
Good to know the refresh thing isn't a bug. If it is a choice between having to manually refresh and the app overall being faster, I'll choose faster.
Did the errors you experienced all happen with a map that you started creating in an earlier version of MapForge? I ask because I completely forgot to mention (my bad!) that there has been a change to the save file format, and it's possible that old-format files will open but experience errors during use due to some missing variables.
One of the optimizations I made to get better performance has resulted in the need to use the "manual refresh" function more often, but at least the redraw delay now happens when YOU want it to and not in the midst of your editing operations.
I'm testing it out on a map now, and while it does seem faster I am getting a bunch of errors.
First, the map does not seem to update well as I am putting tiles down; sometimes they are disappearing, or not changing stacking order (visually). This goes away if I use the refresh, but will quickly reappear as I add more tiles.
Second I am getting "Saving the map failed." errors all the time now. I'm glad you've implemented a backup system, but I fear if I (and everyone else) have to email you files all the time you will be overwhelmed. Is there going to be some way the end user can make use of the backups? I used to get map save errors (in 1.0.3) often enough, but usually after I had started placing items, especially from Jade Halls, or importing my own. Now I am getting this error just stamping down tiles (from Dungeon Blanks IV) and nothing else. Despite the error message it does in fact appear to be saving the map though, since I can load it back up.
Third, after exporting a map I am consistently getting a MapForge is out of memory error, forcing me to restart.
I am definitely getting the item rotation error as well.
Overall some good stuff, some bad stuff. I'll keep messing around with it to see if I can figure anything more out.
Drat! Looks like a quick patch will be needed to address a few things. The most serious new bug I've discovered distorts rotated Items that aren't square.
David Hemenway's page on DeviantArt: http://hero339.deviantart.com/
Doh! You're right.
Sorry, Gabriel and David!
Fairly certain GABRIEL PICKARD is Madcowchef on Roll20, at least I have been buying stuff from him as it matches the previews Madcowchef shows on DeviantArt
Indeed sounds more like a major release.
Didn't think of a cross hair grid before, but that is a great addition.