I usually work in VNC, on a UNIX box, typically from a Windows PC latop.
I occasionally want to capture screen clippings of GUI applications running in VNC. Problem: often they are transient - any key press, etc., causes what I want to capture to disappear.
Usually on Windows my scren capture tools (Windows 7's snipping tool, or SnagIt) have a keyboard or mouse shortcut that takes priority. However, apparently VNC managed to install itself underneath, so all keyboard and input events get sent to VNC and Linux and the app.
So here's how to capture such a transient GUI popup or the like in VNC:
VNC has its own shortcut. On my machine, F8.
Press F8. Go to the VNC options menu. Unselect "send keyboard events to server" and "send mouse events to server". Now enter the screen capture shortcut. Undo so that VNC works again.
Not nice, but I can use it. Will have to see whether AutoHotKey is underneath all of these so can shortcut.
Andy "Krazy" Glew is a computer architect, a long time poster on comp.arch ... and an evangelist of collaboration tools such as wikis, calendars, blogs, etc. Plus an occasional commentator on politics, taxes, and policy. Particularly the politics of multi-ethnic societies such as Quebec, my birthplace. Photo credit: http://docs.google.com/View?id=dcxddbtr_23cg5thdfj
Wednesday, October 24, 2012
GMake order dependent inconsistency
I dislike how GMake is inconsistent about ordering:
You can define rules out-of-order
top-rule: sub-rule1 sub-rule2
@echo top-rule
sub-rule1:
@echo sub-rule1
sub-rule2:
@echo sub-rule2
You can define rules out-of-order
top-rule: sub-rule1 sub-rule2
@echo top-rule
sub-rule1:
@echo sub-rule1
sub-rule2:
@echo sub-rule2
but if you want to do something like collecting the sunb rules in a variable this breaks
top-rule: $(SUBRULES)
@echo top-rule
SUBRULES+= sub-rule1
sub-rule1:
@echo sub-rule1
SUBRULES+= sub-rule1
sub-rule2:
@echo sub-rule2
@echo top-rule
SUBRULES+= sub-rule1
sub-rule1:
@echo sub-rule1
SUBRULES+= sub-rule1
sub-rule2:
@echo sub-rule2
because the variable is expanded when encountered
It must be fixed by rearranging
SUBRULES+= sub-rule1
sub-rule1:
@echo sub-rule1
SUBRULES+= sub-rule1
sub-rule2:
@echo sub-rule2
sub-rule1:
@echo sub-rule1
SUBRULES+= sub-rule1
sub-rule2:
@echo sub-rule2
top-rule: $(SUBRULES)
@echo top-rule
@echo top-rule
Darn! But I like being able write things out of order, top-down.
In general, I like languages that have relaxed order dependencies. Like some RTL languages (notably Intel iHDL). Even C++ has relaxed ordering in some places.
But the inconsistencies such as above are painful and confusing.
--
Single assignment is the easiest way to do non-order dependent.
But accumulation - += - is very much required.
Q: is the accumulation done order dependent, or not?
What is needed is accumulating += - probably order dependent.
And then expanding.
With an error if expanding results in changes to variables already being expanded. ??
Or relaxation.