Open frsommer opened 3 weeks ago
BTW Workaround is using version 0.35
Can you tell us an ARC on which we can test it?
yes, try Frederik Sommer
avatarrlpTREE_reforestration
any other will do as well, do you need an invitation?
but now i get a new error:
Hei, `maybe i did something stupid?: i sometimes create a new assay or study from the arcitect, when filling the new isa files i sometimes open the new isa in excel, open an old isa and copy some old sheets to the new one, modify using old swate and saving them
then open in the arcitect and fill the ontologies to have a green check.
that was my workaround for not being able to reuse already written isa files
that worked fine in v35 maybe this is now a problem? (using excel and old swate)
but cannot do anything now since it always throws the error above
Swate in excel is really old, there were a lot of changes. We tried to be as backwards compatible as possible, but it is not recommended to use the swate in excel at the moment. @Etschbeijer is currently working on restoring Swate in Excel (progress can be tracked here: https://github.com/nfdi4plants/Swate/milestone/9).
Swate will receive an update tonight/tomorrow. This might fix some of the issues you encountered
@frsommer i would need an invite (https://git.nfdi4plants.org/frey1)
Okay, i checked the ARC:
but now i get a new error:
This was an issue with the database, resolved by @Zerskk ❤️
Downloading ARC, open Assay, try to modify/change an swate-sheet, shows blank window,
This issue is due to some underlying changes in our core code (ARCtrl). Swate was not yet ready for the change but had to implement it for other features. This issue will be resolved in the next Swate update (tonight, or tomorrow).
Swate cannot display Input/Output [Data]
currently. Again, this will be fixed soon
CPU is extremely busy when opening an ARC
This issue might be related to #215 on MAC and is currently investigated.
Sadly, it is difficult to narrow down, as we are currently not able to reproduce the performance issue:
OS and framework information (please complete the following information):
Describe the bug
] Screenshots