Community
Participate
Working Groups
Hello, This is enhancement suggestion for building faster more accurate documentation. If each click in the interface was registered by a plugin into a database structure AND the user had access to this database through a table interface, providing editing and drag and drop capabilities, the user would be able to: create accurate click by click instructions for each process in the interface users benefit: faster development of tutorials step by step procedures for complex tasks 'road-maps' for complex projects user analysis material for efficiency analysis This information could also be used in helping users develop: macros wizards user functionaiity tests stress tests on plugins If each click was also recorded and saved as a raster/vector image then this would provide a graphical representation of the step for reference for more visual users of the plugin. I welcome your thoughts on this plugin proposal. regards Dennis Daniels
This is a neat idea and requires support from the UI plugin. I will, for now, move this suggestion to the UI component for evaluation. From a documentation point of view, I think a similar result could be obtained by simply pointing a camera to the screen a record a small movie with the entire interaction. Then one could deliver that as a tutorial, or could do some video editting, image snapshots,etc. For all the other reasons you mentioned (creating wizards, etc.) the support you propose makes more sense.
Dorian, this defect was still assigned to you which means that nobody on the UI team has looked at this. You also need to changethe ownerhip of the defect. Please take a look at this defect and if you still think that the UI team needs to address this defect reassign this bug to the component owner.
Kevin, I am moving this back to the UI component. The feature really talks about having UI support for recording events that can be played later.
Marked for consideration post-2.0. There have been other requests to monitor action activation. We may need to make the action framework more open to support user customizable key bindings in the future, and consider logging at the same time.
Reopen for investigation
not a key binding issue. (key bindings are now fully customizable) action/macro recording is now on the 2.2 draft proposal.
