this shouldn't be an executable
if vsel is set, set it visually selected when toggling on the VisualSelect mode
rename Rotate to RotateStack
create proc & keymaps for rotating visual selection
v is now used for Visual Mode. Use P for creating Povray images.
Use a variable for rotation angle
Translate visual selection
short cuts to change visual selection
Export vselect to vsel.
This is not done automatically, due to issues in memory management.
The main problem is that, you cannot modify the atoms in an
atomselect selection, but you should create a new selection from
scratch.
rotation and translation should be on vselect, so export it.
initialize variables in namespace eval
puts the output of RIncr/TIncr
initialize vsel if not initialized
keep a single repid/delete it on destroy till implementing full support for multiple molids
delete old vsel atom selections
get mol id before destroying atom selection
export vselect to vsel, rather than applying the selection.
vsel is traced, and changes applied immediately. Hence
Export is not needed in translate/rotate procs
don't need it, since we are now managing things through vsel
auto-update