Ok, so after some experimentation, I see that the PWM_PRINTSCRN_APP
environment variable cannot take arguments. A way around this problem is to
have a simple app referenced by PWM_PRINTSCRN_APP and have that app spawn
“snapshot” with the appropriate arguments. This works and produces output.
However, there is another issue. When invoked in this manner, a significant
part (but not all) of the screen is left “grayed” out and won’t come back to
the original display until a console switch takes place. The printed output
is OK though (except for a small part of the screen which contains PtRaw
widgets that is printed as white - which were never expected to print
properly anyway and, for us, is not a problem)
As another issue, I’ve also noticed that the interpretation of y-coords in
the “-o” and “-A” arguments seems incorrect. It would appear that the
y-coord in the “-A” argument is not as the height of the area to be
captured, but rather the y coord of the bottom right corner. The x-coord is
interpreted correctly however.
Again, keep in mind that this is Photon 1.13
“Lionel Johnson” email@example.com wrote in message
I’ve been trying to get the environment variable - PWM_PRINTSCRN_APP to
work. According to the documentation, if this variable is set, activation
the PrintScreen key should invoke whatever is defined. I have tried:
export PWM_PRINTSCRN_APP=“snapshot -o00 -A1024768”
where “dosnapshot” is a script file containing:
snapshot -o00 -A1024768
In both cases, the normal snapshot app does not appear (indicating that
there is some effect), but neither do I get an automatic (i.e.
involved) capture and print.
However, if I set
the normal snapshot dialog pops up and works correctly.
I’m using 4.25 and Photon1.13 (stuck with 1.13 because of client
Any input would be useful