Routing Back Errors from Runtime to IDE #2138
Replies: 5 comments
|
Today i had again a Customer who this Feature would have saved a Fortune of Time. |
|
It would make debugging a lot easier if this is the case |
|
If I read your initial message: "after a Deploy it could write out possible Errors and such here." I have some more questions. After the deploy 4diac IDE is not connected to 4diac FORTE anymore. How and when should 4diac IDE know that it needs to connect to the 4diac FORTE instance to fetch some information? Therefore could you describe more explicitly and detailed what you would expect, what kind of errors should be reported back, how and when should this be reported back, where in 4diac IDE would you search for that. |
yes, you are right. we must make a own Logger like the SDM from B&R: |
|
I could also imagine a monitoring command to retrieve recent log messages from a log buffer in FORTE, similar to the Linux kernel ring buffer. We could then periodically query and show the log messages in a console in 4diac IDE while a monitoring session is active. Is this something that would work for your use case? |
Uh oh!
There was an error while loading. Please reload this page.
currently the Runtime can only log to the "local" console.
would it be nice if the Runtime could also write to the IDE Console ?
after a Deploy it could write out possible Errors and such here.
All reactions