First, in response to Nunigaia's query, the skin I am using is simply "BlackShadowSE P", the one which comes with the system. I have tried with the alternative "Default OE-A"", and the same problem occurs.
Second, in response to VHannnibal and Alexwilmac,
1. I think the two of you are discussing an important issue--whether the green button performs the same function as the OK button seemed to do when it had been available until last week. I agree with AlexWilmac, that the scan function is not new, and that is useful in its own right.
2. This discussion between VHannibal and Alexwilmac, important as it is, touches on but does not quite address the critical issue (the one I raised). To reiterate (perhaps more clearly)... the disappearance of the OK button, whether on Manual Scan or on Signal Finder, is a disaster. Here's why:
3. On Signal Finder: the consequences of the loss of the OK is that, on selecting Signal Finder, the graph showing the signal strength and the signal quality NO LONGER APPEARS. Therefore, there is no way to look at a transponder to check whether there is any signal at all, or to fine tune the position of the dish (espcially iif it motorised), and then there is no way to actually initiate a scan on that transponder. In summary, this update has ruined the Signal Finder function altogether! In summary, SIGNAL FINDER NO LONGER CAN FIND SINGALS.
4. The situation is little better with Manual Scan. Until last week, the OK button was used to actually initiate the manual scan. Pressing the green button now does not quite get the same outcome.
After the update last week, I was so dumbfounded that I thought perhaps my update was just a one-off corruption. I couldn't believe that such a basic flaw could have slipped through without anyone noticing. Loss of Signal Finder is not just an inconvenient "cosmetic frill". Signal Function is fundamental to searching for new channels/transponders and for checking the function of existing ones.
I am not interested in sheeting home blame for this monumental error. I am new to this, and don't know whether there is any way to alert the person who did this to go back, find out what went wrong in this revision, and immediately repair it and post a new incremental update.
I do hope that my post will draw this to the attention of others, and would be keen to hear whether others have noticed the same glitch - and, I hope, a post from the person who can fix it very soon.