# Is there a way to record full log of actions?

**URL:** <https://discourse.slicer.org/t/is-there-a-way-to-record-full-log-of-actions/6513>\
**Category:** Support\
**Created:** [April 16, 2019, 4:24pm UTC](https://discourse.slicer.org/t/is-there-a-way-to-record-full-log-of-actions/6513 "2019-04-16T16:24:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [April 16, 2019, 4:24pm UTC](https://discourse.slicer.org/t/is-there-a-way-to-record-full-log-of-actions/6513/1 "2019-04-16T16:24:44Z")

</div>

I am using several modules and I want to recreate the procedure used but I cant find a proper way to log everything. Some modules simply dont give any useful information. The only logged information currently are warnings and errors, but I know there is info, it is just not used.

Example: I select the segment Editor module, then I select Pant brush. I expect the info to show Segment Editor: Selected Paint Brush.

Where can I change the info verbosity??

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [April 16, 2019, 5:15pm UTC](https://discourse.slicer.org/t/is-there-a-way-to-record-full-log-of-actions/6513/2 "2019-04-16T17:15:00Z")

</div>

> [@Alex\_Vergara](#):
>
> I cant find a proper way to log everything

It is of course not possible to log “everything”, but I agree that it would be nice to log more user actions. Pull requests are welcome!

From what I understand from your questions above, logging would not be useful for you, because you know what buttons you press, etc. Probably you would need a macro recorder instead.

You can already record and replay most GUI actions using QtTesting. Usually it is a bit too low level for general purpose usage, but you can give it a try. Enable QtTesting in Application settings and use Edit / Record/Play macro.

You can record all state changes of MRML nodes using Sequences extension, but it only records result of actions, so you cannot apply them to a new node.

If you want to automate a segmentation process, then you can find several examples in the [script repository](https://www.slicer.org/wiki/Documentation/Nightly/ScriptRepository#How_to_run_segment_editor_effects_from_a_script).

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [April 17, 2019, 1:38pm UTC](https://discourse.slicer.org/t/is-there-a-way-to-record-full-log-of-actions/6513/3 "2019-04-17T13:38:48Z")

</div>

> [@lassoan](#):
>
> Probably you would need a macro recorder instead.

Yes, this did the trick!!  
Thanks