Doh … OK MDI goes and back to tabs it is then, may be a squeeze getting it all into the top tabs but i will have a go.
CHeers Pete.
@Bainesbunch
WOW, I am astonished. I come back after few days and I see hugely improved application! 
Now I just need to find if it can be improved anything more 
Thank You Bainesbunch!
Hello Folks,
Lots of progress to report, the UART decoding is now working and here is a screen shot to see it in action. I am still working on the I2C and SPI as will try and get another release to you before the end of the weekend. I have moved the design away from a pseudo MID interface and back to a tabbed format, which makes seeing all the salient information much easier.
Cheers Pete.
This is looking very user friendly now. Can’t wait to try it out. I especially like the Fake It button, I do need that on occasion.
LOL yeah it is there to create some I2C and UART data so i can debug the decoders. but if anyone has any real UART traces to test with it might be good to play with 96008n1 if you have some please and what it is supposed to contain. I might leave the button there for all those PPL who, like me, don’t have a nano to play with.
My quad is on its way according to the ordering system and the postal service claim to have it in their possession …
I am really hoping that someone like Ben will pick it up and run with it to create an export format for it like he did for the nano. The trouble is that the memory is limited and so it will most likely have to be binary and not XML. Either way as long as the schema is decided it can be imported into my client.
Cheers Pete
Hello folks,
Firstly sorry for those waiting for an update this weekend but I have had some issues with the I2C decoding but as you can see from the screen shot this is now working. I am not going to release another version until i have the SPI decoding as well this will be midweek hopefully.
Cheers Pete.
Hello Folks here is version 1.0.0.6
In this version we have UART and I2C decoding seen in the screen shots.
Automatic saving and loading of configurations on open and close of the application. You still have the ability to save configuration to another file if you want to for loading at another time.
Some screen tidying up and moving of controls about moved it back to a tabbed layout away from the MDI format.
I am looking for more feedback now on what you would like to see included in the beta release.
Version 1.0.0.6 attached along with a default configuration file. this should be placed in the same folder as the application.
Cheers Pete.
XMLDataViewer_V1_0_0_6.zip (156 KB)
Have been using v104 and am quite impressed with your overall layout. Here are a few of my constructive suggestions.
You seem to have everything under control except for the mouse pointer data. If you could display the mouse pointer data only while the mouse is on or very near a waveform data point (displays the nearest waveform data point data only), then that would be fantastic. With the current mouse pointer operation, most of the mouse pointer data is meaningless. Those cursor lines add unnecessary confusion.
If you can do the above, then another suggestion would be that when the user clicks on the mouse pointer location (while mouse pointer waveform data is present) then that becomes the reference for other mouse pointer locations that also display waveform data (now display and leave the cursor lines at this reference location). You could display both the current mouse pointer data and the relative mouse pointer data (in parenthesis, also no cursor lines for current mouse location). If you click the mouse again while waveform data is present, then that becomes the new waveform reference location. If you double click while on a waveform location then the mouse reverts back to pointer only and the parenthesis and reference offset data disappear. This would replace the need for a cursor system, and is used by many CAD programs.
The other suggestion would be to have a button to center the trigger location on the screen. I do believe that you have everything else covered. Oh yes, the help button should also display the version number.
The application is looking very good. Sorry it took me so long to review. 
Thanks very much.
I agree, I’ll work this into the next version.
Another feature I’ll work on eventually. This would be used to show time and voltage differentials, as well as mouse-driven zoom.
I’ll work on adding this, as well as some sort of home button that zooms out as far as possible, and some sort of auto button that fits the voltage scale automatically and uses FFT data to adjust the timescale to show perhaps five cycles.
Thanks again. Currently I’m working on integrating FFTW to support a detailed spectral view. Your feedback is appreciated.
In the future I suggest that you post feedback as comments under the project wiki’s “todo” page, or as “Type-Enhancement” issues in the issue tracker. Would you like me to add you as a project contributor?
Yes, please, thanks.
Excellent. You’re now in the project’s member list. I’ll add anyone else on this forum interested in testing the software.
A nit, but I thought you’d want to know. The About box shows v1.0.0.7
Thanks. Great work.
Paul
Well spotted, it is because I have the compiler auto generating the version when I re-compile
I am waiting on someone to create an XML output for the quad before I continue work on this project, but it is nod dead just sleeping
Cheers Pete.