When I wanted to see the teacher tables, everything would look normal except for the R1 teacher I got an error message. I attach below his screenshot;
Note: no mistake in the table of R1, except this worrying message. Must I neglect it?
That error message shouldn't be there if the dataset is fine.
It looks like your dataset constaints 2 bugs:
bug 1:
teacher R1has got at least 2 activities at the same time at day 0 (your first day) and hour 2 (your third hour).
bug 2:
teacher R1has got at least 2 activities at the same time at day 2 (your third day) and hour 2 (your third hour).
TiTiTo displayes only the first activitiy and warns you that there is at least a second one (not displayed, since i display max 1 activity per slot in that view)
Can you please check:
TiTiTo -> Activities -> Plan Activities 2
click on "Hour" first (so all activities are sorted by hour), then click on "Teachers" (so all activities are sorted by the teacher name)
now check the table: search teacher R1 and check if he has got 2 activities at the same time.
I wonder a bit why that happen, it shouldn't happen normally. Do you remember why that happen?
If that is not the bug:
Please sent me your FET file (if you didn't modified the activities) or sent me you TiTiTo database per E-Mail please.
I sent you an email
Ah. ok.
As soon as you import that file, you will notice that there is already a warning about constraint teacher R1 is not available. That constraint is inactive, but TiTiTo imports it as active. The warning tells you to modify that and import again. It is difficult to automatically fix that, i will maybe check later again if i can code that (it is difficult, since i read the "not available"-flag too late, the order of the FET file isn't perfect for my import, since i need to convert the xml file into a SQL-Database).
So TiTiTo sees activities at that 2 times and also (active, even in fact it is inactive) not available time. That can't be true and it warns you.
So please open your solution with FET, delete that 3 inactive not available constraints and save the file again (maybe with a different name). Import the file again and all warnings are fixed.
Ah ok! now I understand why?. Thank you very much for the detailed explanation.
But it would be nice if you think about this little problem. At least you put it in your TODO. Although it may not be so necessary.
ok. I coded it. i will upload a new version in a few minutes. thank you for report.