jwildfire.org

Nearly reached the goal, so this is probably the last BETA
As usual, any feedback is welcome, changes since BETA 6:

- major improvement of the progressive preview (flickering reduced, updates now at each change, updates faster)
- new button to toggle progressive-preview in the main-editor, new option in the Prefs to specify the initial state of this button (tinaEditorProgressivePreview)
- new options tinaEditorProgressivePreviewMaxRenderTime and tinaEditorProgressivePreviewMaxRenderQuality to control the progressive preview
- rearranged some buttons so that it is unlikely to press the MutaGen-button by wanting to press Undo (important because the MutaGen currently can not cancelled)
- moved the gradient-editor-button to the gradient-tab

- new property tinaCustomVariationsPath in the Prefs to specify the path for external custom_variations (used by the Custom_Variation_Loader_GH script by CozyG).
- created a v6 of the Custom_Variation_Loader_GH-script by CozyG, which now used the new Prefs-option for the path and included this version as standard script

Download: http://www.andreas-maschke.de/java/j-wi ... 0BETA7.zip

This is fabulous! Thanks for all your work as well as CozyG.

Maybe for the final release you should include the variations for custom loader script ... A one time deal??

The problem is not to include them, the user can not use them unless he copies them to the path (which is an external path by design). So, it would probalby make more sense to offer them to download as separate file

add a link to this for people to download in the instructions?
viewtopic.php?f=23&t=1957

Yes, for instance, maybe just link to the main thread, but better CozyG will finally decide this

this is a good version
Now it seems it is usable at will, static and progressive view coexistence.
One thing you can add is to prevent image refreshing when there is nothing to do: 1. an editor button is pressed (without altering image) or 2. a triangle (without actual editing) or layer is being selected. Refresh only on execution of a function, it will be less disturbing this way.

It is indeed a release candidate. I hope there is room for future improvement in those "big bang" start up milliseconds, especially to tweak somehow dark image phenomenon (not so many pixels) at the beginning of rendering. But this can be just theoretical and the solution might be only higher cpu power. I guess there is not enough data to show without a very fast CPU. But there is static real time for this, this is not a problem, I am just mentioning it.

Also you could fix the layers overview problem.

Layers overview works ok with static view

Have optimized this now as well (as it was possible with not too much effort, but is a real great improvement)

BETA closed, release this night...