UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
I like the new multi-screen set-up – much better! I’m a long-time user and my experience is that the software works very reliably and predictably.
But I do have a couple of useability suggestions.
The first relates to readability of the fonts used on control buttons and tabs. Generally, you have very thin fonts in a very light gray against a half-strength white background. Such low contrast makes reading tricky for me. This might be an aging astrophotographer’s problem, but it is a real one for me. I would appreciate a choice of 2-3 colour schemes for the program. For example, standard (the existing one), plus medium and high contrast ones.
The second relates to the placement of the “execute” button for various tools. Generally, it is at the bottom of a long list of options fields, which always requires a page scroll to reach it. Would you please consider putting it near the top of the lsit to obviate the page scroll need?
The last one concerns the image displayed after a file SAVE. I keep getting tripped up by my logical expectation that the image I just saved is the one in the viewer. However, it remains the originally loaded one. I usually discover this when I complete the next tool step (eg CBG to CSC) to find that the file name about to be saved is the one before the prior save. This requires me to reload the first saved file, reprocess the tool step againa nd save again.
Can we have an “autoload option which, when selected, will automatically reload the just saved image into the viewer?
+1 for these suggestions particularly the last one. I have been using APP for about 18 months and have the impression that earlier releases did do an automatic reload of the just saved image.No?Yes?
Thanks for the suggestions, I passed them on.
