(old)Puppy Linux Discussion Forum

Hi

Flash wrote:In that shot, if you had chosen "Window", which window would Screeny choose?

01micko wrote:I'm glad you asked that Flash.

The cursor turns into a cross hair looking cursor and you just hover over the window you want and click.

Just make sure that the window to be captured IS NOT obscured (behind) any others,
otherwise this will happen: (see pics)

CatDude
.

Mmhm, including the pointer in a cap (even with a fancy full-service-cap+ wine-app like FSCap) can be tricky in Puppy .. it's all about the difference in how the pointer is drawn and by what, how it relates to the rest of the draw and so on.

Ridiculously easy (and the pointer image shows as expected without any special consideration for mask, etc) with fscap in native win32..

Hi Mick,

I have installed Screeny-0.4 on my Wary desktop, and although it works very well as is, I would like to have your app work with my PrtScr key --like I have been able to do with mtpaintsnapshot. While I am able to configure Screeny to run when using the PrtScr key, it does not capture and save a screenshot, despite appearing to go through the motions of doing so... --and I have no idea why.

It seems to me that once I have set the key binding properly in JWM, it should just work, and therefore no additional lines of code for your scripts are necessary... --any ideas, suggestions?

Thanks in advance,
Monsie

Monsie, have you installed xwd?

Aragon

aragon,

Thanks, indeed I did install xwd. When I indicated that Screeny

works very well as is

I meant that it runs fine from the desktop menu when I use the mouse.

Further, the fact that I am unable to get Screeny to work with my keyboard at the moment is not a deal breaker for me... rather, it's a preference and also a curious puzzle that I would like help with solving, and in the process I am sure that I will learn some things along the way...

Monsie

Hello Monsie

Sorry for the delay, your post just caught my attention.

I will have a look at your issue and see if it can be resolved in the next version.

Cheers

EDIT: hmmmm... it works fine here. Are you putting this command in /root/.jwm/jwmrc-personal? It certainly seems strange if you actually get the screeny gui showing yet it fails to work . Maybe a conflict? Any errors in /tmp/xerrs.log?

Hi Mick,

Thanks for getting back to me.

Yes, I did indeed have the key binding set in jwmrc-personal just the way you indicated... so tonight, just for kicks I tried it again, and this time Screeny did "save" the snapshot, but the file showed up in text format... So, then I tried to re-boot Wary but was not able to... I kept getting a kernel panic, and no amount of re-booting with the various troubleshooting options would help...

To make a long story short, it appears that my Wary Puppy CD is corrupted. I have been having intermittent problems with booting it since the summer at least... I thought it was because I was running pupmode 13 but as it turns out, now I cannot boot up Wary 5.3 from the CD alone, whereas Puppy 4.3.1 and Wary 5.2.2 work just fine in my latest test, and in fact, I am running Wary 5.2.2 in live mode as I post this...

So, I will have to burn a new copy of Wary 5.3 and once I get Puppy set up again the way I like it, will try this again. If I do happen to have further glitches with setting up Screeny, I'll let you know... but as I suspect, I think the problem (all along) is due to a messed-up CD.

Monsie

Hi Monsie, thanks for letting me know. Hope you get your installation fixed.

Meanwhile, I have released 0.5. Has some new "features" (erm, which I promised it wouldn't get ). Sorry, no cursor feature, too hard basket in the context of the program.

EDIT- 0.6 is out, fixed potential bug with setting an insane delay (not a positive integer), use hard coded 1-10 instead in a combobox

Just an update for the record...

I burned a new copy of Wary 5.3 and so far, so good Luckily, my save file on my usb flash drive seems to be intact, so it did not take long to get up and running again.

Screeny 0.4 is working just fine when configured to run with the keyboard through JWM so I will have to try the newest version next...

Monsie

01micko wrote:...
0.5 posted
...
-windowed shots get the forum compat treatment if chosen too, be aware that small windows get enlarged, but if you don't want that turn off forum compatibility
...

my hacked /usr/local/screeny/screenfunc wrote:#!/bin/sh
#functions for "screeny"
#set work dir
#121006 L18L do scale only if width is greater than 600 px

APPDIR=$(pwd)
export APPDIR

case $1 in
snap_func1)
{
WINDOWID="$(xwininfo -frame|grep "Window id"|tr ' ' '\n'|grep "[0-7a-f][0-7a-f]")"

xwd -id "$WINDOWID" | xwdtopnm | pnmtopng > "$CAPTURE"
}
;;

snap_func2)
{
WINDOWID="-root"

xwd $WINDOWID | xwdtopnm | pnmtopng > "$CAPTURE"
}
;;
forum_func1)
{
WINDOWID="$(xwininfo -frame|grep "Window id"|tr ' ' '\n'|grep "[0-7a-f][0-7a-f]")"
#121006
WINDOWWIDTH="$(xwininfo -frame|grep Width:|cut -d':' -f2|tr -d ' ')"
[ $WINDOWWIDTH -gt 600 ] \
&& xwd -id $WINDOWID | xwdtopnm | pnmscale -w 600 | pnmtojpeg > "$CAPTURE" \
|| xwd -id $WINDOWID | xwdtopnm | pnmtojpeg > "$CAPTURE" #121006
}
;;
forum_func2)
{
WINDOWID="-root"
#121006
WINDOWWIDTH="$(xwininfo -frame|grep Width:|cut -d':' -f2|tr -d ' ')"
[ $WINDOWWIDTH -gt 600 ] \
&& xwd $WINDOWID | xwdtopnm | pnmscale -w 600 | pnmtojpeg > "$CAPTURE" \
|| xwd $WINDOWID | xwdtopnm | pnmtojpeg > "$CAPTURE" #121006
}
;;
esac

Have fun

Nice idea L18L

One problem, 2 calls to xwininfo means 2 clicks..

I simplified the original var and separated it, While the code is technically slower I don't think it matters.

Attached is an experimental version with the above, but I didn't add the fullscreen code. If your res is less than 600 then something is wrong or your eyesight is poor! Plus all of Puppy's icons would be squashed up. I guess if you ran in vertical mode then it would be warranted, but I just think that the case for not out weighs the case for.

Oh yes, I tried to add gettext to the experiment, doesn't quite work with the menu tooltips and the help/about.

Cheers!

Hello Mick,
yes my eye sight is poor but my screen is 1920 px wide
and I did not think about small screens < 640*480

Anyway attached is v 0.6.5.1exp
It does NOT contain screeny.pot because using Barry´s momanager you do not need it.
German translation in MoManager-de-screeny...

# (c) Mick Amadio, 01micko@gmail.com LGPL 2012(see /usr/share/doc/legal)
#L18L HELP in tmp/screenyHELP, help &
# splitted in smaller chunks
# added: File, Help, delay, preferences, splash messages
# message about smaller than 600 px trashed
. gettext.sh # enable multiple variables in message (see eval_gettext)
# version 0.6.5.1

Have fun and keep the faith
---------------------------------
LO-downloader extended

Hi L18L

Works well . I switched to de_DE.UTF-8 to try it out.

So.. what's the best way to package an NLS file for version 0.7? (considering mo-manager so others can translate).

Once a couple more translations are in I think it's ready to be a replacement for mtpaintsnapshot at the woof level.

Ha.. for a proggy I started touted to have NO features it sure has evolved

Hi 01micko,

you wrote:...best way to package an NLS file for version 0.7? (considering mo-manager so others can translate)....

For getting more translations I suggest you post in Localization Project
with a link to post 1 of this thread where version 7 will be available.
And the hint use momanager should be sufficient.
But also pointing to MoManager translation manager in
[url=file:///usr/share/doc/HOWTO-internationalization.htm]HOWTO internationalize applications[/url] (klick file /usr/share/doc/HOWTO-internationalization.htm)

Packaging a *NLS.pet is merging the different /usr/share/locale .... only
and not the /usr/share/applications

Thus the translator can post just the MoManager...screeny...tar.gz produced by momanager. Nothing else than
- version 0.7
- the momanager and devx
is needed to make the localization of version 0.7.

OK, thanks L18L

I have posted 0.7.

NLS only includes /usr/share/locale/de/LC_MESSAGES/screeny.mo (I think that's right ) at this stage.

For those who have L18L's 0.6.5.1 version there is no functional difference at all with 0.7 so no need to download it. It's only the version that changed.

See main post (with link to language support thread)

Screeny is not working in LazY Puppy.

How can this be fixed?

RSH wrote:Screeny is not working in LazY Puppy.

How can this be fixed?

Maybe gettext is not installed properly? The gettext.sh script should be in $PATH and eval_gettext is a function in that script. Just check your gettext package and maybe renew it from the lucid repos (Lazy is based on Lupu, yeah?)

If you have at least gtkdialog-0.8 it will work if the executable "gtkdialog" is in $PATH. This can be a symlink, often it's labelled "gtkdialog4". I could put in some gymnastics that find the correct exec but it has been around long enough now that distro maintainers should be aware. I believe wary/racy/precise/dpup all have similar symlinks and so it works fine there.

Thanks for you quick reply.

Yes, LazY is based on Lucid 528-4.

Lucid 528-4 dosn't have the gettext.sh also ---> only a binary "gettext" in /usr/bin ---> as is in LazY.

Downloading and installing gettext_0.17 from the lucid repo gives no success.

Changing to in line 183 inside the screeny script doesn't give any success (in lucid 528-4 gtkdialog is a symlink to gtkdialog3, gtkdialog4 is already installed in LazY)

Maybe the gtkdialog error is just a result of the missing gettext.sh script?

Any OS from where i can grab this script?

Hi 01micko.

Thanks for the script. Unfortunately no success. Only the error messages have changed.



BTW: 0.6 seems to work.

http://ftp.halifax.rwth-aachen.de/ubunt ... 3_i386.deb

There you go, hope that works