It seems to be the other way around; QDate only accepts dates, while QDateTime accepts both dates and times.
We can't directly use the QDateTime data format because it would then also process the letters between words that match the data formats.
For example, "Session default" would be interpreted as "Se35ion 7efpmulCEST".
That's why I proposed the standard bash format, so the user can explicitly mark with % which patterns (data formats) should be processed.
This means that each data format needs to be validated and converted, and for that, the code need to predefine which ones are accepted and include them.
It could accept them all; there aren't too many... but I decided on the ones that would actually be useful.
Regards
PS: I really think this functionality would be interesting and useful in general... but for that, a UI would be necessary. Not only because of "name-patter", but also because the template function would be strengthened.
1. This would clearly show that the directory in a template functions as the default directory for projects (it took me a while to figure this out).
2. Template properties could be easily edited without having to open a new session, save as, search to overwrite, etc.
3. And it would also have a naming pattern.
I don't think I'm capable of making the UI, and it doesn't make much sense for me to do it alone either.
It seems to be the other way around; QDate only accepts dates, while QDateTime accepts both dates and times.
We can't directly use the QDateTime data format because it would then also process the letters between words that match the data formats.
For example, "Session default" would be interpreted as "Se35ion 7efpmulCEST".
That's why I proposed the standard bash format, so the user can explicitly mark with % which patterns (data formats) should be processed.
This means that each data format needs to be validated and converted, and for that, the code need to predefine which ones are accepted and include them.
It could accept them all; there aren't too many... but I decided on the ones that would actually be useful.
Regards
PS: I really think this functionality would be interesting and useful in general... but for that, a UI would be necessary. Not only because of "name-patter", but also because the template function would be strengthened.
1. This would clearly show that the directory in a template functions as the default directory for projects (it took me a while to figure this out).
2. Template properties could be easily edited without having to open a new session, save as, search to overwrite, etc.
3. And it would also have a naming pattern.
I don't think I'm capable of making the UI, and it doesn't make much sense for me to do it alone either.
But sharing ideas is fun :)