About a BATCH I/O log header

[Padanges]

Hi,
please, consider writing the header where there would be the process start time and the operation type name in the Batch I/O tab. For example, "Info Edit fields batch tool started at ...date/time". I found it relevant to get that info while working with PDFe. It's possible that others found that missing too.


Thanks in advance.

[RTT]

Done.

[Padanges]

Could you please make it also possible to get back to the previous mode (before BATCH I/O log got automatically visible), for example, to the "PDF view" mode, just by presing ESC key, once the process has finished? The "keyboard-only" users don't like mice, you know


Thanks in advance

[RTT]

Done.

[Padanges]

Great. I would also recommend using a font which represents white spaces in equal length as widest chars in Batch I/O log window (for example, Lucinda Console does that) - this way we could see properly formatted output without the need to save them to a file first. And would also suggest to set the default "save log" name to current date and time (using legal file address symbols, and leading zeros if necessary): "year-month-day,hour-min-sec". That would help to organize logs faster.

P.S. this naming default could also be useful for "Export Grid Fields..." - we usually need to give the name some unique ID counter, and the time format serves this well.


Regards

[RTT]

Done. Now the batch i/o window uses a monospaced font and the default file name of the save batch i/o log and export grid dialogs includes the date in the name.

[Padanges]

Great news
In addition to this, it would be useful to be able to save the log with a hotkey "Ctrl+S" instead of a mouse-click, i.e. using "Ctrl+S" (or at least "Shift+S", if the previous combination can't be used) in I/O Log mode would run the Save File dialog. What do you think?

[RTT]

Done. Ctrl+S, or the shortcut currently assigned to the UpdateInfoAct action, now also triggers the batch i/o logs save as dialog.

[Padanges]

Great. I'm just curious, how do you avoid "hotkey collision" (if it's assigned to UpdateInfoAct and Save File dialog) then - activating a hotkey checks for the current pdfe mode and only then executes the command accordingly?

[RTT]

The hotkey is global, but the function called by the event can make decisions. In this case it's a easy to know what are the user intentions, based on the active mode.