Hi Hans,
I didn't anticipate long comments - I thought people would just type a few words, but I see what you're saying. I'll convert the comment box into a memo field with scroll bars.
It's possible to default the child comment to the contents of the clipboard (using GetClipText()), but doing so by default could lead to some unpleasant surprises for unsuspecting users, depending on what was last on the clipboard. I see two options for this:
1) Add a button to trigger pasting the clipboard comments into the Child comment (click the button, clipboard contents are added to the child comment), or,
2) Add a checkbox on the settings form to turn this feature "on" (the comment is whatever was in the clipboard when the macro is run) or "off" (functions as it does now, with the comment blank when the macro starts).
I could go either way - what do others think?
I didn't anticipate long comments - I thought people would just type a few words, but I see what you're saying. I'll convert the comment box into a memo field with scroll bars.
It's possible to default the child comment to the contents of the clipboard (using GetClipText()), but doing so by default could lead to some unpleasant surprises for unsuspecting users, depending on what was last on the clipboard. I see two options for this:
1) Add a button to trigger pasting the clipboard comments into the Child comment (click the button, clipboard contents are added to the child comment), or,
2) Add a checkbox on the settings form to turn this feature "on" (the comment is whatever was in the clipboard when the macro is run) or "off" (functions as it does now, with the comment blank when the macro starts).
I could go either way - what do others think?
