Posts made by hookxs

Hi, this is an old issue, I just want to bring it up again because there doesn't seem to be any progress in fixing it. It is not a critical bug but still rather annoying. Some devices are set to switch to dark mode automatically at night and then windy is inconvenient to use. One would think that all it takes is to hard-code the text colors if you don't want to bother with having two different themes :-)

Previous threads eg:
https://community.windy.com/topic/26848/dark-mode-in-android/14
https://community.windy.com/topic/29102/forecast-data-showed-for-a-specific-location-are-almost-unreadable-with-dark-theme-on-android/5

@Suty Hi, is there any progress in this matter? There are several bug reports in the forum going months back that the color scheme in the dark mode is unreadable and the response is always that "it will be investigated". I appreciate your effort but nonetheless would like to ask - is there anything being done in this? Is it not possible to simply hard-code the colors (ideally two schemes based on light/dark mode) at least as a temporary fix until it's properly investigated? Because really as soon as the device (automatically) switches to dark mode, windy is unreadable and frustrating. It is the only app in my entire collection that has such issue. Thank you.

@Ondřej-Šutera Sure, my device is Xiaomi Redmi 9T, Android 12, MIUI 14.

@Ondřej-Šutera Hi, I want to +1 this issue. Windy android app is hard to use in when dark mode is on (which can happen automatically system-wide), the forecast panel is illegible. I don't think it is an issue of some devices, the problem is that some font colors are hard-coded and not dependent on light/dark mode. Could that be fixed? Many parts of the UI also change colors dynamically but the font color is apparently fixed. Thanks.

I meant the "meteogram" info, what you show is "basic". My meteoblue is grayed out and cannot be selected, which probably is not a bug but led me to believe that it has something to do with why (for me) meteoblue is not displayed correctly on the forecast map (which I believe is a bug).

Ok. If I start windy, click on a map to select location and switch models in the bottom-right, it seems to work. If I then click on the yellow arrow to expand the bottom panel with meteo info, the value on the map disappears like you say, so I cannot compare. But if I start windy, go to the search bar in top-left, choose some previous location, the bottom meteo panel is expanded automatically but the value remains displayed on the map (unlike in the previous case). Now if I switch models using their labels below the meteo panel, the displayed value on the map gets confused - it may seem to work but you quickly discover that the values are wrong, because it is possible to get 2 different values for the same model depending on which model was selected previously. I am not sure I can give any more info to replicate the error. I can make a video of the whole process I guess, if anyone is interested. The same error is apparent which other layers (clouds) where different models often give different numbers so it is easily visible.

yes, I know about model availability, bu I sense that meteoblue is in some ways special - for example it cannot be selected in the "meteogram" panel (instead of "basic")

"As shown of screenshots posted above, values are correctly displayed for ALL models (including MeteoBlue)."

-- you are right. Unfortunately I can post equal sequence of images that shows that meteoblue data is not displayed (I mean the whole map, not the one displayed number). Instead it displays GFS or ECMWF.

"when you click the down arrow available as a control after selecting a point on map, the compared meteogram is displayed on the bottom side and the point marker changes to a pulsing circle (no more values are displayed for it on the map)."

-- I am not quite sure what you mean. I use the latest chrome. I did not click on the map to select location (I can try) bu I chose the location from the search bar in the top-left corner (as one of the previously used locations).

I am pretty sure it has nothing to do with internet connection or model availability - all three demonstrated models are well available at the location (ECMWF, ICON, GFS). Maybe this bug manifests itself only when you switch layers (wind / clouds etc.) or do something else, I don't know, but I noticed it long ago and for me it is annoying but I can imagine that many people do not even notice.

The correct map display and METEOBLUE model also works for you? Try some european location, select eg. wind layer and switch between ECMWF-METEOBLUE-GFS-METEOBLUE-ECMWF-... do you see three different forecasts (colors of the map depending on wind speed)? I see only two, not meteoblue.

Three different values for ECMWF for the same location and time depending on which model was selected previously.

I can quite clearly demonstrate that they do not change correctly. I just cannot do a video at the moment, I'll try later.
Also, try alternating between 3 meteo models and you will see that as you go from model 1->2->3->1->2->... the same model suddenly shows different value that it showed in the previous cycle.

About the meteoblue bug in my original post - it seems that the map cannot show meteoblue info and shows either GFS of ECMWF (in my region) but there is not indication that the displayed map is not meteoblue, which is misleading and should be imho corrected.

When e.g. wind layer is selected (or clouds, ...) and forecast for a particular place is displayed, the value of the selected layer is displayed in the map (e.g. 180dg 2m/s). If I then switch meteo models, the map changes but the displayed value remains the same. After another switch, the displayed value changes but is always one model behind, which is confusing. Also, for some models (meteoblue) the displayed map shows the same as GFS, which is also confusing (there is no indication that the displayed data is actually GFS, therefore it is misleading for the user).

True, I do not care about 10 vs 10.2 m/s. But at low speeds it can make a difference, especially when considering the overall daily trend at different locations. If the model predicts 2.5 all day in one place it might be too low for some sports while 3.4 in another place means I might have a better chance there. Currently, I get 3 and 3, the information loss is obvious.

Also, I do not see the downside. Even if it were useless for majority of users, it could be implemented as optional or displayed in the dedicated "wind" tab like I suggested. We could equally argue that predicting wind direction is inaccurate, therefore NE, SW etc indication is sufficient but still we can turn on display in degrees. And it is not consistent to equally round m/s and km/h to integers, the resolution is different.

Just saying it would be beneficial for some and harmless for others. These past few days I used the mobile app which displayed decimal places while the web app did not and it is really better. After the last app update this option is gone.

The title says all. Please show wind speed as 3.2 m/s instead of 3 (likewise for other units) as it used to be. It provides much better info. At least allow to turn this on in options or show the extra decimal digit in the "wind" tab (if not the "basic").
Thanks!