« Last post by mouser on January 16, 2006, 02:48 AM »
i tried getting winamp to scrollcapture and couldn't, even in sendkeys mode which really *should* work...
the post above describes the idea. here's what might have worked with winamp but doesnt quite:
Winamp PE;20;20;20;50;sendkeys
that says when capturing windows of class "Winamp PE" it should use the margins of 20;20;20;50 (see above) and use the sendkeys method of scrolling.
im not sure why the sendkeys is not causing the window to scrol.. the margins are used to make the capture avoid the scrollbars and skinned window borders.
« Last post by mouser on January 15, 2006, 02:57 PM »
thanks for being understanding. as you know from past work on f+r i tend to work in bursts on different apps, focusing on one for a few weeks or a month and then switching over to another. f+r stuff is still percolating in my mind and it'll get it's turn at bat soon
« Last post by mouser on January 15, 2006, 01:55 PM »
baseman, we really need some new good reviewers.. if you feel like writing a review drop me an email and we can talk about a category that might interest you and others.
« Last post by mouser on January 15, 2006, 11:24 AM »
yep, i've just been holding off releasing this so they can come with version 2, which has just gotten pushed back a little while the other programs are being updated.
« Last post by mouser on January 14, 2006, 02:34 PM »
what happens on those screensavers it doesnt work on? maybe the keypress interrupts the screensaver before it can be captured? in this case you could engage the delayed/timed capture of screenshot captor and then start up screensaver (either with a tool to start the screensaver or by doing preview from screensaver config options).
« Last post by mouser on January 14, 2006, 01:56 PM »
it will be extremely interesting to hear the next episode of the mp3 show. fodder you should listen to it on mp3 - it's clear that his cohost realizes the gravity of what he's accusing microsoft of doing and keeps offering him the opportunity to back down but he never does.. you have to give him some credit for sticking his neck out so far on something that's going to get a lot of push back.
« Last post by mouser on January 14, 2006, 01:28 PM »
i guess there are multiple issues here. 1) watermarking that is just meant to add a VISIBLE extra overlayed image, usually to corner of picture, or covering entire picture, which is not intended to actually hide information but rather brand your image. 2) steganographic watermarking, designed to secretly embed information that you could use to prove ownership etc., which would be invisible and hard to remove.
i was thinking more along the first lines. for the 2nd case configuring an external tool would be your best bet probably since as fodder says it can get a bit involved and probably doesn't belong inside screenshot captor itself.