Welcome to The Bug Genie
Please fill in your username and password below, and press "Continue" to log in.If you have not already registered, please use the "Register new account" tab to do so.
![]() Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
There are no comments
There is nothing attached to this issue
This issue has no duplicates
There are no code checkins for this issue |
|||||||||||||||||||||||||||||
Really delete this comment?
Instead of/as a complement to using a global space for linking, could we envision some "Screen To Canvas" and "Canvas To Screen" value operator on vectors ? This is basically two translation operators oriented toward opposite directions. We can do that by hand using Add and Sub value operators (I think), but this is tedious and difficult to maintain.
As an example:
Export ⇑ top
Right click on P1 shows menu "Export" (as usual) and "Export Global". Select "Export Global" -> the value exported in in fact the operation Canvas To Screen(Outline1, P1.origin). E.g : (50, 30)Import ⇑ top
Right click on P2 shows menu "Connect" (as usual) Select "Connect" and the local space coordinates of P2 are connected to (50, 30). This is not the desired value. Right click on the value node and "Convert" to "Local Space". This now the desired value (20, 10).The whole thing is still dynamic. The previous behavior is preserved and this is transparent for all already implemented features are the origin is still expressed internally as local layer coordinate space.
Thoughts ?