VFB History wishlist: Persistent ID Numbers

[lbpalm]

Instead of numbering the images from top to bottom in ascending order, consider number them from bottom to top in ascending order, i.e., the latest image render is always the highest ID number.

This would make the ID number associated with each image in the image history stack persistent instead of the number getting bumped every time a new image is added to the stack.

The value is that when referring back to previous images, the identifying stack number would always be the same, persistent number.

Persistent numbers would greatly facilitate easy access to image selection in the stack when looking up settings, comparing images, etc.
It also seems to make logical sense.

BTW, I would not advocate for a limit of 9 images in the history stack.

[dlparisi]

See here...http://forums.chaosgroup.com/showthr...indow-Behavior

[vlado]

I have 1269 images in my VFB history; I never delete stuff - instead I let V-Ray delete the oldest images as the history disk limit is reached. How would persistant IDs be helpful if the latest image ID is something like 1269?

Best regards,
Vlado

[lbpalm]

HaHa - I don't delete either!
If I were asked, my suggestion would be to create a unique VFB directory, in the max project folder set, for each project as a matter of rote.
- Maybe the create folder dialog could default to such a location when invoked.
And I would suppose 1269 images could be handy, given there was a way to keep track of and document them, such as you have provided.
I also think it would be cool if there was a way to auto-name single frame images, in version sequence, to the file's project name. Probably another question.

[vlado]

Actually in the VFB settings you can actually choose to store the history in the project folder (there is a "Use Project Path" option).

Best regards,
Vlado