Messages

I guess the reason are the many new example and test files.

Maybe extract FET-7.8.2 and compress it again. If you think the update of the OS is the reason, then then new compressed FET-7.8.2 should be larger too.
I will try and search myself now.

hmm... I must think about how to do that; but not this weekend. I fear I need to do a second check for each single statistic in FET. It is not as easy as in TiTiTo.
In TiTiTo I use exactly the same source as in FET for a whole day, since in fact in TiTiTo I import half days as full days into TiTiTo; so the data in TiTiTo is already a full day and not a half day like in FET. That trick is not possible in FET. I must keep half days in FET. I must code it different in FET.
If you need the statistics for full days fast now, then you can currently import it into TiTiTo and check the statistics there.

I guess in most situations counting also activities with 2 or more teachers is preferred by the user.

If you timetable is not too difficult, i suggest to just select 2 groups and set the "same staring time" constraint.
Advantage: The physical education teachers might even mix the groups. For example if they want to do different physical educations for boys and girls and since you set an "same staring time" constraint this will be also fine, if you need to generate a new timetable later.
disadvantage: maybe a bit more difficult to solve

I think that is fine. You might add an address or phone number in the next line(s).

It depend on who you do substitution planning in your country. There are a lot of different ways how countries do that.
If the "normal" teachers must do the substitution, then "Must come earlier, Border gap, Must stay much longer, Must come earlier, ..." is very needed and useful information. Removing that information is a bad idea in that case.
If you have "special" teachers, that do only substitutions or if you have external teachers that do the substitution, then that information is maybe too much for you.
hmm...
I think the suggestion should be done max optional.

The only other variant is writing the times in the comments and keep the hour name very short like "1st", "2nd", ... only.
I think it is fine to add the suggested feature. I can't see (big) disadvantages.

I also think this is a bad option for most users.
Also: Even if you need it now, as soon as you do the new timetable 6 or 12 month later, you probably forgot that you set that fixed feed.
So if you ever add the feature, then in my opinion it must be also added:
a) A warning if you try to generate multiple timetables at once. It should disallow it and warn that it is only useful if you disable the settings again.
b) A warning with EACH single generation. Because users will forget after some time that they fixed the seed.

It will help if you post an error report.
So you compiled an executable already?
You started the executable and it crashed?
Post the error log here.

Hi,

the trick is to do a minimum example that FAILS. In that case it is easier to find the bug.
I am busy at the moment, so that is probably not the smallest minimum example file that I attach here. I don't have time to check more detailed. But check the attached file. You need to fix that bug. Maybe some other guys have more spare time.
By the way: It will be useful if you say at least "Thank you!" (or more) if guys helped you in the past with success (I hope you remember that other guy(s)).

PS: Please don't double post your problems. Other guys can't see now if your problem was already solved. You force me to double answer. That is work that I don't want to do. Please mark your duplicated questions.

I fear we can't help, since it look like he uploaded only the FET source to github, but not his "Web" code. I was only able to import data, but I am not able to generate. I can't see the problem/bug without the source.

I didn't tested it in the last days, but some years ago height wasn't supported and it looks like it isn't supported today too:
https://doc.qt.io/qt-6/richtext-html-subset.html
So I guess it is only possible with a workaround like boarder, margin or padding.

This way did not want to work this year, where I have one activity for a block of subjects.

I don't understand that part. Even if there is a single subject per block only, you can do that by StElTo, even in fact that is unneeded, since it is trivial and you can even add such an activity in FET directly after you imported the other blocks from StElTo.
Maybe explain more detailed.

TextEdit->setWordWrapMode(QTextOption::NoWrap);