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
Contrary to pyaedt where there seems to be value to keep a function handler, using a function handler in pyedb does not seem to add much value (for example, no value to redirect info to UI or to be more fault tolerant). More over, it hides under the hood issues. That's something that we found out last week when working on an example over Materials.
Change proposed: removal of the function handler and direct handling of the raised methods.
The text was updated successfully, but these errors were encountered:
Contrary to
pyaedt
where there seems to be value to keep a function handler, using a function handler inpyedb
does not seem to add much value (for example, no value to redirect info to UI or to be more fault tolerant). More over, it hides under the hood issues. That's something that we found out last week when working on an example over Materials.Change proposed: removal of the function handler and direct handling of the raised methods.
The text was updated successfully, but these errors were encountered: