-
-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening New Transaction window for the first time, does not show date correctly #5807
Comments
Linux issue, likely due to #5668. Probably just need to set a minimum width for the field. |
I am unable to reproduce on Debian Bullseye. |
@FlameHorizon Which distro are you running? I'll spin up a VM and try to reproduce & debug using the same. |
@ovari Do you see this issue in Linux Mint? |
@n-stein Edit: have experienced this bug with Linux Mint 21.2 Cinnamon. |
@n-stein have experienced this bug now.
|
This issue still exists in Flathub version 1.7.0 as of 12th March 2024 (Linux Debian 12.5). |
Could you, please, provide a screenshot? |
The format of the date controls in wxWidgets is locale based. In Windows it's entirely dependent on your system locale, but for Linux you can try changing the locale in the MMEX options (the blank drop-down below currency in your screenshot). |
"try changing the locale in the MMEX options" |
For Linux I you may need to also specify the encoding. Try adding ".UTF-8" as in en_GB.UTF-8 You can type in the locale box directly. |
Tried that and no change sadly. |
Ah, you are using mixed locales. What is the output of In the past Flatpak has had issues when the system locales use multiple languages. See flatpak/flatpak#3712. Maybe try:
|
@ovari is the original issue here (date field too small) still a problem for you in the 1.7.1 beta? |
Since they are available on the OS you should be able to add them to flatpak. Try:
|
Appreciate your help on this issue but I'm curious to know how this might affect things generally since selecting the UK format had no effect on the date field and other Flatpaks seem unconcerned that the locale is not present in the |
Sorry, I don't know enough about Flatpak to be informative here. Perhaps @joshua-stone has some insight? |
Have seen this behavior before; however, have not seen this issue recently. Sorry, don't know how to reproduce.
|
Did that refer to the issue about locale I raised in respect of incorrect date format? |
Where are you installing your Flatpak from:
|
@GrahamLees your screenshot shows version 44, not version 45, of the GNOME platform. Are you using the latest, i.e. beta, version of MMEX? If not, can you please test with the MMEX development version 1.7.1-Beta.1? Instructions to install the latest MMEX development version can be found here: #6246 (comment) Thank you |
The version of GNOME is actually 43.9 MMEX was installed from the standard repo using |
Can you please check with the 1.7.1 development version as it is understood that this issue was present in version 1.7.0 and has been resolved sometime during the 1.7.1 development cycle? If this resolves the issue for you, then perhaps this issue's milestone can be changed to v1.7.1 too. Thank you |
@ovari |
@ovari well I tried following those instructions but couldn't get it to finish. I got as far as step 7 and saved the file to: I'll just reinstall the Flatpak from the repo as before and wait until the development version is committed and update from there. The issue is no big deal to be honest, The date picker calendar confirms the date is correct in the field - just presented wrongly - and the date entered in the transaction field is correct in every respect. |
The location where the mmex.flatpak file was downloaded is a temporary location and does not allow full permissions. Also, once you close the browser, the downloaded files may be deleted. Copy the mmex.flatpak file to your Downloads directory (or Desktop). Somewhere that the file will be available after you close the browser and also have permissions to run the file. |
ah, understood. I wondered if I should change the download directory doh 🙄
The only one that loads is the old version which I removed from from the GNOME software list of installed packages but is seems to remain? I seem unable to run the beta version. EDIT: Thinking about it, I think I may have just re-installed the 1.70 version from Flatpak which is why that version is coming up. If I uninstall it again, how do I manage to run the beta? |
Perhaps https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-run can provide some help?
Does that work to run the master branch (i.e. 1.7.1 Beta 1)? |
No, it stil wants to open the 1.7 version and errors with There are still 2 versions listed in |
https://askubuntu.com/questions/1406523/some-flatpak-apps-do-not-display-the-right-locale-language-on-ubuntu-22-04 Does typing the following in your Terminal help:
or from https://man.archlinux.org/man/flatpak-config.1.en
|
What flatpak version do you have on your computer?
|
@ovari 1.14.4 |
@ovari I just tried creating a new database in a separate directory (so not using the existing data set) and this is the same result: |
@ovari By the way - just for completeness, I did use |
LC_MESSAGES changes the UI language. You want to run |
Ok. I've replicated your situation. I have two locales used in my system (same exact ones as you) I've reconfigured my Flatpak to only see the 'en' language: Note when starting MMEX it shows the Now I simply Now if you check Then you can run MMEX normally with |
MMEX version:
Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of MMEX or on updated development code
(master branch).
Operating System:
Description of the bug
Opening New Transaction window for the first time, does not show date correctly. Closing New Transaction window and opening it again shows date correctly.
Reproduction
Is the bug reproducible?
Reproduction steps:
Expected result:
Date should be displayed.
Actual result:
Control, which displays date is to small to show anything.
The text was updated successfully, but these errors were encountered: