by brianoh on Fri Aug 20, 2010 9:31 am
It's hard to believe that it's four years since layer support was promised. What's the problem here? An otherwise great program is so badly let down by the absence of layers that I cannot understand why this isn't the number one priority for your developers. I can only surmise that either the underlying software model is such that it would have to be redesigned from the ground up to implement this feature and, for some reason I find hard to fathom, it's taking an extraordinary length of time for you to achieve this, or you don't consider it an important enough feature to give it your attention, which I would find utterly baffling.
As a developer myself, and assuming you do consider it important enough to introduce, I have to ask how hard can this be? Although graphics is not my field, surely layers are just objects? You define them as you would any other object, store the definitions in, say, an XML file, and expose each layer on reloading to the end user as a selectable link, much like Photoshop or - somewhat differently - Xara. After all, you have to create them in the first place already, so surely preserving their properties for independent manipulation after committing them to a project is a relatively simple enough step, no?
This one single and very significant omission makes Axialis a frustrating program to work with. Correcting it would be so advantageous to both the end-user and your sales figures that it has to be a major no-brainer, so why the inexplicable delay? How much longer are your users going to have to wait for this?