TiTiTo 8.8.1 released

[Volker Dirr]

WARNING: The translation is currently not working fine. So maybe wait with an update. I will try to fix that problem soon.

You can download the new version here:

Windows 10 or higher: REMOVED (see note below!)
MacOS 13 or higher: REMOVED
Linux x86 64bit:  <...will come soon...>

Note for Windows users:
If you get errors at startup like missing VCRUNTIME140_1.dll and MSVCP140_1.dll, then you need the latest software from Microsoft.
See:
https://learn.microsoft.com/de-de/cpp/windows/latest-supported-vc-redist?view=msvc-170

You probably need this one:
https://aka.ms/vs/17/release/vc_redist.x64.exe

Change log:
8.7.0: - supports FET 7.1.5 file format
8.7.1: - updated to Qt 6.8
8.7.2: - improved FET export (protecting characters <, >, ', " and &)
8.7.3: - send emails is asynchronous now
8.7.4: - removed macros SIGNALS and SLOTS
8.7.5: - added some languages translated by Google AI
8.7.6: - improved Untis export
8.7.7: - coded a workaround for printing. So hopefully no more printing bugs.
8.7.8: - Untis GPU 014 export can skip missing teachers, if no comment is manually added.
8.7.9: - bug fix: schedule rooms 2 was incorrect for activities with duration > 1 and swapped axis

8.8.0: - activities -> schedule timetables: option to display the day name
8.8.1: - updated to Qt 6.11.2

[Benahmed Abdelkrim]

The Algerian Arabic translation seems to be to be working incorrectly.. See the attached screenshot below...

[Volker Dirr]

Thank you for report. I must check that.

[Volker Dirr]

hmm.... I can't reproduce it under Linux. Maybe it happen only with Windows. I will check that later.
Maybe I am viewing the wrong dialog. I can't read Arabic. Is it the attached screen?
Maybe also try to just select English in the settings. Restart TiTiTo. Select Arabic in the settings. Restart. And check if the bug is still there.

[Benahmed Abdelkrim]

With version 8.7.5v, this problem no longer exists. The problem appeared with this latest update. I tried changing the language to English, then Arabic, but nothing changed; the problem persists...!?

[Liviu Lalescu]

Maybe newer Qt, Volker?

[Volker Dirr]

hmm.... I updated Qt on Windows; that is correct. But I just tested it with my Windows and it is running fine there.

There must be something more different. Are you using Windows 10 or 11?

Is it incorrect in all sub dialogs or only in that single dialog?

So for example what about the dialogs if you press F1, F2, F3, ... are they all wrong?

[Benahmed Abdelkrim]

It's incorrect in all sub dialogs.
Even if I press F1, F2, ... the problem is the same.
I use Windows 10 ...

[Volker Dirr]

hmm... Thank you for feedback. Sadly I have currently no good idea how to fix that, since I can't reproduce it :-( I must search a bit for this problem.

[Volker Dirr]

ahh... Now I can reproduce the problem on a second PC without installed Qt IDE.
I will try to fix that soon. Sadly i must work tomorrow. So I can hopefully fix it on Saturday.

Dear MacOS users: Is this bug also in MacOS? I haven't got a second Mac anymore to test that.

[Volker Dirr]

ok. I think I fixed it.
Please test this file an let me know:
REMOVED

[Benahmed Abdelkrim]

The problem is solved. Thank you for your dedication. 

[Liviu Lalescu]

So, Volker, what was the problem?

[Volker Dirr]

Not 100% sure. Since there was limited time in the night yesterday, I tried 2 fixes at the same time. One of it is the reason why this strange bug occurs.

With the latest Qt version lupdate and lrelease are not recommended anymore. I use now lupdate-pro and lrelease-pro instead.

And also i swapped back to my old workflow. Since I need to add the simple-mail dll and I need to use MSVC for TiTiTo (not for my other tools), my workflow was always a bit complicated. I wanted to change it, so that I also only need to execute a single script. So instead of mixing between QTCreator and command line, I wanted to use the command line only.
Well, the MSVC command lines knows qmake und nmake, but compiling failed, because of unknown "cl.exe". So i added the PATH to "cl.exe" myself. By that I was able to compile from command line. I must check the whole log files and have a log if there is a warning that i didn't saw so far. I switched back yesterday to my old "complicated" workflow (compiling TiTiTo and simple mail with QtCreator, but update translation and deploy by command line).