4 Attachment(s)
New Image Filenaming Feature - #IV
Dear Xara...
...I am underwhelmed by the total lack of response to a serious defect in your Image Filename feature.
I have completed a simple exercise for you to respond to now finding that the creation of Image Filenames is dependent on where the image happens to be.
This is clearly unworkable as no subsequent access and usage of an expected filename can be assured.
I created three identical Grouped items, called Ducks, and placed them all on the X-axis (X=0).
Each was given a different Image Filename.
The Preview/Export/Publish HTML of Attachment 129491 reveals only the first Image Filename is applied to all three Ducks.
I moved the third Duck 0.67px right (X=0.67), Attachment 129492 now reveals the third Image Filename.
Only when I have all three Ducks at non-integer co-ordinates, Attachment 129493, do we see all three images rendered with the right filename.
Sadly, put the Ducks onto integer co-ordinates and the last two go AWOL, Attachment 129494
This, together with the random numbering of images even when they are exact clones, makes a total mockery of this feature's expectations.
Will you please address this immediately.
A response will be welcome but is not expected to acknowledging there are ISSUES.
Perhaps you might add a klaxon warning in the next release should people accidently place thing on integer co-ordinates?
Acorn
Re: New Image Filenaming Feature - #IV
Yes I agree this is very odd behaviour. It appears that Xara see's your first identical image as No1 image and identical images, whether named differently are ignored. I can't understand why moving an image to non-interger positions should break this filename. I can understand that changing the size would create a new image name.
Re: New Image Filenaming Feature - #IV
Quote:
Originally Posted by
Egg Bramhill
Yes I agree this is very odd behaviour. It appears that Xara see's your first identical image as No1 image and identical images, whether named differently are ignored. I can't understand why moving an image to non-interger positions should break this filename. I can understand that changing the size would create a new image name.
Egg, if you examine Xara's code, even a dimension change, rotation or squish/ squash need a different filename either.
Similarly, identical Bullets are also being compromised.
See my prior Threads with the same name.
Acorn
