sethuster / purple Goto Github PK

The Test button only looks for the element by purplepath that is hard coded.

This needs to be configurable or removed.

We need to add either Clear or Clear All (or both) buttons into the Purple. After adding 6-7 elements, the Purple path box (underneath the Add Element button) is pretty full and busy looking. Clear button will help to keep clean and simple for the Purple path display box

When users click on the refresh button while attached to an application it would be nice if the treeview was opened back up to the particular spot in which the refresh button was clicked.

Right now users have to re-explore the application to get back to the point in the tree view in which they left.

The tree view arrows do not work properly.
When the arrow is clicked to expand the tree view the items are not calculated because the arrow click event doesn't know which item it's expanding.

Users can double click the item to expand the tree view and it works properly.

When attaching PurpleUI to a different application using the application window text box and the refresh button, PurpleUI should start to browse the application tree of the selected application.

However this does not work. It looks like the app still thinks the configured app from the app.config is not running. Which it is not.

Might need to reset this flag when the refresh button is clicked and the application name is not null?

Need to be able to refresh the tree view when the application under test changes.

Would be nice to be able to toggle on the tree highlight, and have the highlighted element change based on the tree view item selected.

This button doesn't do anything.

When users change the application they want to browse at Runtime, the test button no longer works.

This is because the Testbutton is looking for the app.config for the default app name. Need to change this to look for the Application Textbox name.

If users try and attach purpleUI to applications without correct capitalization of the application name, the UI won't attach. Closing the application that PurpleUI was attached to when trying to find elements will crash the application.

Would be nice to add some checking or a friendly error message to the app so users can recover better during these circumstances.

When large areas are highlighted in the Application Under Test, the PurpleUI is covered by the highlight. The user can't click through the highlight back into the purpleUI.

This is because the highlight is actually a transparent window overlayed on the bounding box of the element found with the PurpleUI.

We should add a process to the highlight algorithm to make sure that the PurpleUi is always placed ontop of the Highlight window.

When I tried to get the Metric and the Imperial radio buttons (from Program Options) accessible name using the Purple, it displayed the label names instead of accessible names with a blank value. Looks like the Purple couldn't find some of parent paths and the accessible element names in the tree view.

Expected: /LifeQuest™ Pipeline/Program Options/ProgramOptions_BorderPanel/ProgramOptions_TabPanel/!BLANK!/GeneralTab_UnitSystemPanel/GeneralTab_MetricRadioButton

Actual: /LifeQuest™ Pipeline/Program Options/ProgramOptions_BorderPanel/ProgramOptions_TabPanel/!BLANK!/!BLANK!/Metric (SI)

When trying to automate the calculator app, the menu items can be seen, but their child elements can't be selected from the PurpleUI. This is strange since we can expand menu items in LQP and see all the way down.

Not sure what the problem is here.

When starting the purple UI and not have the application under test running, the Purple UI throws a null reference exception.

The shade of Purple in the Element Info section makes labels difficult to read.

We should change the Element Info bounding box to a lighter shade of Purple to make Labels easier to read.

It would be nice to have a button to clear the purple path textbox.

Right now users have to highlight all the things and delete it.

When users try and explore a application tree, from a previously cached version of the application attached, PurpleUI will crash unexpectedly. This might go well with a fix for issue #19.

Steps to Reproduce:

1. Start PurpleUI and attach it to an application (LQP for example)
2. Browse through the application tree and get info on an element
3. In the attached application, make a change. Open a panel or do something significant
4. Attempt to browse the application tree in PurpleUI
5. Observe the crash, ZE CRASH!

Purple sucks right now!

Would be nice to be able to not have to refresh the entire application view and only refresh certain sections.

Maybe add a context menu choice to refresh at that level?

Users's can't use the Get Element button when the app is changed from the default application at run time.

The Application crashes.

For some reason when we're clicking on the program options tree view items such as 'general' on the program options screen in LQP, the purple path is showing as a blank.

Expected: /LifeQuest™ Pipeline/Program Options/ProgramOptions_ConfigGroupTree/General

Actual: /LifeQuest™ Pipeline/Program Options/!BLANK!{1}/General

When I added a element by clicking the Add Element button, it brought back all elements paths that I deleted all previously in the Purple path box (underneath the Add Element button). It should NOT bring back all deleted elements paths values to the Purple path box.

Want to be able to build element cache files in different formats so that we can use them to directly discover if application builds have changed.

Supported formats to Add:
-XML
-CSV
-JSON?