@Filippo,
Danke für den Test, es ist doch komisch, wie Du es schon mal in einem anderen Test gesehen hattest, dass der Text im Portrait Modus nicht so sauber aussieht als im Landscape Modus.
Das Problem in Deinem 3ten Bild werde Ich natürlich verbessern. Hatte leider nicht mit allen Sprachen getestet.
Thank you for the tests, it is starnge, as you already had seen it in a previous test, that the texts in portrait mode are not as sharp as in the landscape mode.
The porblem in your 3rd image will for shure be improved. Unfortunately I didn't test it with all languages.
@digitaldon37,
I forgot this one, if you don't mind, I will no more draw the messages on the bottom of the screen, but on a Panel in the middle. Before, when drawing onto the foreground it was easy to refresh a part of the screen without changing the background image. In drawing now directly onto the background image, it would need two whole screen updates for a message, the first time for displaying the message, and the second time to delete it. With the Panel the message display would be independant.
Best regards.
Thanks! I noticed on the pda that there is a delay during screen paints. I don't think this is an issue but I thought I would mention it to see if anyone else noticed it. For example, when going from the main screen to detail screen, you can see the screen being erased (a blank screen shows) and then you see the new screen.
But again this is a minor point. I think getting rid of the fuzzy fonts (though I never could see them on my pda) is a big win.
I read the posts at xda, and I agree with davehutch about the image sizes. They should be the same for both, image and control.
- The condition images are 52*52 pixels but in the program 50*50.
- The detail images are OK 40*40 both
- The button images back,save etc are 48*48 but in the program 50*50
- The + / - button images 16*16 and in the program 20*20
For the +/- buttons there is also a difference in the display on the desktop and the device. I suspect that, as the image files are PNG files they use the 4th byte for tranparency which seems to be used on the desktop but not on my device (WM2003).
In the attached image you see the difference, left device right desktop. Just for test the upper + button is 16*16 pixels. This should remain 20*20 but 20*20 images.
There is also an image with the new Message display.
As I am updating the program, do you want me to also update these sizes.
I read the posts at xda, and I agree with davehutch about the image sizes. They should be the same for both, image and control.
- The condition images are 52*52 pixels but in the program 50*50.
- The detail images are OK 40*40 both
- The button images back,save etc are 48*48 but in the program 50*50
- The + / - button images 16*16 and in the program 20*20
For the +/- buttons there is also a difference in the display on the desktop and the device. I suspect that, as the image files are PNG files they use the 4th byte for tranparency which seems to be used on the desktop but not on my device (WM2003).
In the attached image you see the difference, left device right desktop. Just for test the upper + button is 16*16 pixels. This should remain 20*20 but 20*20 images.
There is also an image with the new Message display.
As I am updating the program, do you want me to also update these sizes.
Best regards.
I think we should change it to the sizes that are standards - ie 48x48 for the condition, 36x36 for details - this would let people drop icons that are already available and use them without much effort.
The button sizes should probably be something standard also - 48x48?
I forgot what I used for the add/delete sizes, but those probably should match the control containers on the form.
I noticed something in the new version. When adding a new location by touching the green +, for the United States certain states lose pull-down menu to change the first lettor of the city. This happens for connecticut, delaware, Hawaii, Nevada, Rhode Island, Vermont, Washington DC, and wyoming.
Is descriptor name on the main page on the todo list?
my reply
Quote:
Interestingly, those states don't list their cities in perfect alphabetical order on the weather.yahoo.com site. For example, Delaware lists the city of Arden as the very last city - this breaks our code.
I will have to write some type of work-around...
Looks like I need to see how arrays can be sorted in B4PPC...
Looks like I need to see how arrays can be sorted in B4PPC...
Updated with sorted cities (thanks to agraham's collection library) but I still have the same problem. It looks like Yahoo doesn't provide an alpha list for some states.
Last edited by digitaldon37 : 01-10-2009 at 10:42 PM.
The fact that for certain states there is no alphabetic list is due to the fact that there is no alphabetic list available in Yahoo, this depends on the total number of cities. Look at the two images below. The same behaviour also exists for other countries where you don't even have a states list.
Unfortunately, the last version does not solve the problem. I tried with the state of Nevada and the city of Zephyr Cove, you get the city of Coyot Springs. Will have a look at it.
Version 0.41.2 with cities sorted alphabeticaly and the right city code.
Added also new text files with 2 new texts in, only English, French and German have the text in the right language in the other files the text is in English..
Linear Mode
