You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In eeschema_do.py::wait_eeschema_start(), KI6_LOADING is passed as part of the other argument to wait_eeschema() and from there to wait_for_window(), where it raises ValueError instead of waiting for KiCad to gather its marbles.
I think that is a mistake ?
wait_for_window() has special handling of KI6_LOADING but that looks wrong as well, as it requires other to be a string argument, rather than a list argument ?
I'm not proposing a patch, because I have a hard time figuring out how what the intention/correct operation is in this case.
For me, removing KI6_LOADING from the argument to wait_eeschema() solves the problem.
The text was updated successfully, but these errors were encountered:
In eeschema_do.py::wait_eeschema_start(), KI6_LOADING is passed as part of the other argument to wait_eeschema() and from there to wait_for_window(), where it raises ValueError instead of waiting for KiCad to gather its marbles.
I think that is a mistake ?
It gives another try to KiCad waiting 1 second before trying again. This gives KiCad 3 seconds to load the schematics. I never saw KiCad loading schematics for that long. Now I modified the code to wait upto 60 seconds.
wait_for_window() has special handling of KI6_LOADING but that looks wrong as well, as it requires other to be a string argument, rather than a list argument ?
Nope, it must be a list.
I'm not proposing a patch, because I have a hard time figuring out how what the intention/correct operation is in this case.
For me, removing KI6_LOADING from the argument to wait_eeschema() solves the problem.
I'm working with some really huge multi-page schematics for a retro-computing project (https://datamuseum.dk/wiki/Rational/R1000s400/2022_Project_Status) , and kiauto often fails because KiCad takes too long to load them.
In
eeschema_do.py::wait_eeschema_start()
,KI6_LOADING
is passed as part of theother
argument towait_eeschema()
and from there towait_for_window()
, where it raisesValueError
instead of waiting for KiCad to gather its marbles.I think that is a mistake ?
wait_for_window()
has special handling ofKI6_LOADING
but that looks wrong as well, as it requiresother
to be a string argument, rather than a list argument ?I'm not proposing a patch, because I have a hard time figuring out how what the intention/correct operation is in this case.
For me, removing
KI6_LOADING
from the argument towait_eeschema()
solves the problem.The text was updated successfully, but these errors were encountered: