Lord Insectord gives suggestions

It happens after acepting the save dialog, instead of the "saving project" i get the access violation. Can't see the cursor in that context.
In the current project I got the access violation like 10 times by now...

I use an intuos3 too, but my left hand is always hooked at the ctrl-z area, and using the drawing hand there in the tablet feels unconfortable, maybe I can get used to it...

[Taron]

Can you send me that project file somehow. Sounds like you had it saved before, but working on it again gives you trouble, is that correct?
If that was the case, I'd really love to see that project file. I'd be happy to be able to recreate that damn crash, for sure!

I'm not sure I understand that last line, though. Your left hand is hooked to undo and using your drawing hand there...you mean your left hand is your drawing hand, but you have to have it over the undo area the whole time?
That sounds horrible!
I've got to get the customizable hotkeys up and running soon, I see.

But first I want to solve your crash problem. It's really weird, because Verve for me is almost perfectly stable, I'm not ever afraid it crashes. So...we gotta figure this out!

I think I cornered it: https://dl.dropboxusercontent.com/u/2294713/21.rar
Go to the goat's layer, use the first brush, smallest size, paint detail/light on the horns, ears, head, chest, legs, then save and... let's see If you get the jack pot... I tried 4 times and crashes every time.
P.S.: I think painting a lot of tiny detail with small brush sizes might be the problem... now no matter where I paint, if I add small detail, I get the crash.

[Taron]

Wow, that is exciting... ...for me, eh...in case I will run into that crash, too, I can fix it right away, I'm sure! I'll have a look!

[Taron]

OMG that is awesome!
(just had to write that real quick!)

[Taron]

YES! I GET THE CRASH! YEHAAHHH... ...uhm, now, that's probably not the expected reaction ... ...but now I can track it down!!!

[Taron]

Uh, Oh, that's a bad one, though!
It has something to do with the memory bank size, somehow going beyond capacity. Wow, that is unexpected and quite evil. But I'm glad you've manage to explode it, hahaha...ouch. I had no idea there was a limit?! So, that'll be interesting.
I'll figure it out! In the meantime, what will certainly help is to collapse some of the layers. I shall solve this somehow...

[Taron]

Oh dear, man... I know where the problem is at and I have a vague idea how I can solve it, and it's a totally logical issue!
This can currently only be a 32bit application, but you've got so many layers with so much (beautiful) data on them, that it bursts the 32bit bubble. Now I am going to change the whole file system because of this, which is rather traumatic to me , but I will still do it. Yet, I can't tell how soon this will be done.
I really hope you can forgive me, but you should try to optimize your use of layers for now. I know this isn't all that easy, since my layer merging is still rather simple and you may have to revisit your painting strategy a little bit.
I will go at it as hard and as fast as I can as soon as I can. Shit. It annoys me, too, so very much, that I have to run into such troubles. We already have 64bit machines, but Blitzmax really wasn't expected to ever scratch those memory boundaries, haha. Shiiiiat.
Anyway, I'll be on it, Zafio, and I'm truly, really, really sorry. The only upside is: It's not my code or the rest of my code, rather. It's purely a memory management issue of the file system. And that is good. Better than having a trouble in the middle of the code somewhere.
I can prevent the crash, but it would prevent the saving of the file, too, hahaha... doh. Or partially only, which is just as stupid.
I wonder how you were able to save it in the first place, actually!? Impressive.

But what you've painted there is just gorgeous! I hope you can find an alternative way to proceed with it, because it would be an unforgivable loss not to have you wrap it up! It's exquisite!

Wow, well, I'm sorry to be the hell bringer!... But I'm glad you know what the problem is finally.

As for me, well, I've lost the count of crashes, but I'll change the strategy as you suggest

[Taron]

Great! I'm still so sorry about this, but that's how it goes with ALPHA developments, I'd imagine. In my case that's quite unusually extreme, considering that this is my first really big programing project and I get to deal with things I've never touched before. So...I can only apologize and thank you to push me & Verve forward like that! It's kind of fantastic, actually. I just hope it's not going to hurt too much with such crash situations. I'm excited you have a good saving habit, though! I'd have gone nuts to think you would've lost such a masterpiece! You manage to use Verve so elegantly, so clever and artistically, I can't tell you how happy and awe-inspired you make me!