BaRatin-tools / BaRatinAGE

BaRatin Advanced Graphical Environment
https://baratin-tools.github.io/en/
GNU General Public License v3.0
4 stars 0 forks source link

Remember properties of exports to Bareme #37

Open benRenard opened 1 year ago

benRenard commented 1 year ago

and more generally, of any kind of export requiring some user input.

Original request:

Actuellement, lorsqu'on exporte une courbe au format bareme, on doit renseigner le code Hydro, le nom de la courbe, et les dates de validité. Le problème, c'est que si on souhaite refaire cet export, il faut tout re-rentrer, rien n'est gardé en mémoire. Ce serait bien qu'au moins le code Hydro et les dates de validité, une fois rentrés une fois, soient conservés.

IvanHeriver commented 1 year ago

Maybe each project should be associated with a bunch of arbitrary items managed in single class ProjectSettings which could contains things such as:

More generally, BaRatinAGE should have Global Settings and Project Settings, the latter overwriting the former when specified.

IvanHeriver commented 10 months ago

Could you tell me how to export a rating curve using the Bareme format? I don't seem to be able to do that in BaRatinAGE v2.

Also note that this is not implemented in BaRatinAGE v3.

benRenard commented 10 months ago

In v2, you can do it by right-clicking on a RC, then "export values", then select "Bareme" in Filter dropdown.

Example: exemple_bareme.txt

The v2 code is here

I reckon it's a feature some users might miss if it's not in v3, and I don't think it's terribly complicated to implement, so I'd say it's worth the effort

IvanHeriver commented 8 months ago

export to Barem format is now supported in BaRatinAGE v3.

However, export config/properties are still not remembered at the project level.

This issue points to the need for a clear way to handle different settings with different scopes as already mentioned earlier. Here are 3 scopes I can think of right now: