[Implemented] send the DebugOutput to the ClipBoard
- netmaestro
- PureBasic Bullfrog
- Posts: 8451
- Joined: Wed Jul 06, 2005 5:42 am
- Location: Fort Nelson, BC, Canada
Re: Programmatically send the DebugOutput to the ClipBoard
Updated my code to allow for multiple calls over some time. Original code would only work once and fail if you called it again later.
BERESHEIT
Re: Programmatically send the DebugOutput to the ClipBoard
Darn, NetMaestro, how could you forget 'lastSize' ?
I knew there was something wrong with your code, i just knew it.
Thanks for correcting it... and please, please, do better next time.

I knew there was something wrong with your code, i just knew it.
Thanks for correcting it... and please, please, do better next time.

PB Forums : Proof positive that 2 heads (or more...) are better than one 

Re: Programmatically send the DebugOutput to the ClipBoard
Hello Dude,
in case you still follow this thread, know that I now feel double sorry for you. You'll surely deserve a big apology for having been told off for disregaring the topics intention and even dared to evoke thinking about a possibly helpful workaround.
I too had the joy to develope a 'solution' the other day but didn't post it because:
a - it wouldn't have suited the topic and wasn't its aim/need. (that was before your 1. posting)
b - there are always others who can do it smarter and they love to let you know. (still before your 1. posting)
c - I realized it would have been a huge shame, if I had done. (after your postings and muting)
Not only because a workaround in and of itself is a no-go (in sense of disrespect) but even more, because it can only be of so low value as everybody is already doing it ever since. (it still gives me the shivers)
But mind you, my solution looked nearly exactly like what Danilo had come up with, even regarding the needed delay ... and I'm sure it would have been dismissed just the same, only for being by me.
The respect and fun on board is to the others.
greets ~ Vera
in case you still follow this thread, know that I now feel double sorry for you. You'll surely deserve a big apology for having been told off for disregaring the topics intention and even dared to evoke thinking about a possibly helpful workaround.
I too had the joy to develope a 'solution' the other day but didn't post it because:
a - it wouldn't have suited the topic and wasn't its aim/need. (that was before your 1. posting)
b - there are always others who can do it smarter and they love to let you know. (still before your 1. posting)
c - I realized it would have been a huge shame, if I had done. (after your postings and muting)
Not only because a workaround in and of itself is a no-go (in sense of disrespect) but even more, because it can only be of so low value as everybody is already doing it ever since. (it still gives me the shivers)
But mind you, my solution looked nearly exactly like what Danilo had come up with, even regarding the needed delay ... and I'm sure it would have been dismissed just the same, only for being by me.
The respect and fun on board is to the others.
greets ~ Vera
Two growing code-collections: WinApi-Lib by RSBasic ~ LinuxAPI-Lib by Omi
Missing a download-file on the forums? ~ check out this backup page.
Missing a download-file on the forums? ~ check out this backup page.