UI feedback

[aurolou]

Some feedback and questions on the UI:

• when I establish a connection to an application, it shows up in my workspace list. the application remains listed there even after it's terminated. If I open and close to many application to which I establish a connection, this gets cluttered very quickly.
• Log: this listed applications in my workspace continue to produce Log output even after they have been terminated. e.g., "connection has been re-established". It feels like it's wrong, or I'm not sure what it's suppose to mean, because the application is not even running anymore. It makes the Log also a bit unreadable because you have to filter out these messages to be able to catch the ones for the current application that is actually running.
• In the workspace list with all applications connected, there is a little icon next to the executable name. it's first white, then red. I think it's red after the application terminated, but I'm not sure. My question is: what does this icon mean?
• In the bottom of the UI, it shows a note when compilation happens. this note stays there even if the application terminated due to some crash that happened during instrumentation. Since I'm not sure what it's compiling, I am confused if it's actually still doing something, or if it stopped compilation because it was application specific.
• I also noticed that while the app is running and connected with GPU Reshape, the Log is constantly outputting that it Lost the Connection and Regained it. I'm not sure what it means at all - is there something wrong and if yes, what and how to fix it?

[miguel-petersen]

Hi Lou,

1. Agreed, will address.
2. There's some odd behaviour there for sure, something I have noted as well. It shouldn't re-establish to anything given the application tokens (GUIDs allocated by the host resolver) are different, but somehow it is.
3. White implies the connection is solid. Red implies the connection is bad. Reshape pools the application for a ping message every now and then, if the application does not respond within three seconds, it is considered lost.
4. Yeah the UI response to crashed applications is lacking. It's an interesting problem, as knowing when an application is gone may not be so trivial. I suppose the right way about this is to not ping the application, but the host resolver on the machine and let it figure out if the process died or not.
5. There's something wrong with the network handling, known issue.

[miguel-petersen]

The above has since been addressed.