lrbarber commented on issue #1086: URL: https://github.com/apache/daffodil-vscode/issues/1086#issuecomment-3005720542
Especially with the addition of the Data Editor, things have changed quite a lot since this issue was created. As the debugger is started, there are several possible indicators of action taking place. Some of these may not occur due to user configuration settings. Let's look at them in the order they may appear: Pop-up windows asking for file selection for schema and/or data file. If the launch.json configuration contains file selections, these windows will not appear. Text scrolling in Terminal window shows DAPodil communication between VScode and Daffodil. If compilation & parse are both successful, a Pop-up Window indicating that the infoset has been written. There may also be a pop-up window indicating that data is being logged. A java pop-up command window will indicate the starting of the Omega Edit server. This is very evident on Windows, but on linux systems it is generally hidden. The Data Editor window will be open showing the contents of the data file. Behind the data editor, another tab shows that a temporary infoset file was opened, but has been removed (redlined filename) -- it was copied to the actual infoset output filename. (will add info for compilation and parse error scenarios) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@daffodil.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
