YoWindow Forum

The picture is really beautiful on the ipad3. The program has worked fine until tonight. When looking at the forecast 5 days out the program froze. If I hit the << in the upper left corner, the options screen comes up. I can go through the option screen but when I hit done the screen of the house is still frozen.

Hey, Tom!
Thanks for finding this problem.
If 'the program is still in the locked state, can you try the following?
- Go to options and turn Debug option ON.
This will display debug buttons over the landscape.
- click "Cl" button - this will open a console window.
The console at the moment is very awkward and ugly.
Scroll through the Console with your finger.
- Try to find any messages in the console colored in RED.
If you find them, please take a screen-capture of them and post on the forum or just send to me by email.

To take a screen-shot you need to press Start and ON/OFF buttons at the same time.

PS
I have modified the title of the post to reflect the problem.

Tom, I have an idea why the freezing could have happen.
Do you remember if you were rotating the iPad after you have selected the day?

Try the following experiment.
1. Select a day in the Forecast Panel, make sure white frame displayed around the day.
2. Rotate iPad to make its orientation change from Portrait to Landscape or vice versa.
Will you have the freeze?

I did your suggestion. Picked a forecast day then turned the orientation and the program did freeze again.
I can turn on the debug but it won't show on the screen. The screen is totally frozen.

Hi pasha
The same problem. With ipad2 ios 6.01 Gr
Herman

Good!
I'm glad to read that my guess was right.
I will fix this problem in the new build.
It will be available in the middle of the next week.

Thank you, Tom, thank you, Herman!

tph06784 wrote:I did your suggestion. Picked a forecast day then turned the orientation and the program did freeze again.
I can turn on the debug but it won't show on the screen. The screen is totally frozen.

Same here on iPad2 (5.0.1)...

My iPhone4 (5.0.1) doesn't seem to have this bug...

I have downloaded latest version and can confirm that this error is fixed.