Am 02.01.2013 um 20:05 schrieb Kevin Gale <[email protected]>: > Hi Christian > > Is there any specific reason why this was changed as I think this is going to > cause problems for us.
well, this is a way to find bugs and correctly handle out of memory situations. > I imagine some (if not all) of the PictureMBS functions return nil for > several reasons with out of memory only being one of the reasons. Currently, > if we get a nil value we know we cannot continue so we clean up and exit (in > quite a lot of cases we don't really care why we got the nil as it makes no > difference). Well, just to show you: RawRow(index as integer) as memoryblock this one raises OutOfBoundsException if index is invalid. it returns nil if image is invalid or the row is nil. In normal case it returns a memoryblock pointing to the row. Row(index as integer) as memoryblock This one returns a copy of the row, so beside of the above it raises now an OutOfMemoryException. RowInFormat(index as integer, ImageFormat as integer) as memoryblock this one goes like the above. If most people here think my idea of adding OutOfMemoryException here is a bad idea, I can of course remove it. But I thought it's a good idea to have the plugin report the issue. Greetings Christian -- Read our blog about news on our plugins: http://www.mbsplugins.de/ _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
