On 12/10/2015 at 01:33, xxxxxxxx wrote:
As far as I know, it is not possible to select another object when you are in point mode.
You must switch to model mode, before you can select another object.
Is this correct, or is there another way. For example using some code or a plugin?
-Pim
On 12/10/2015 at 01:44, xxxxxxxx wrote:
Hi
Maybe to use https://developers.maxon.net/docs/Cinema4DPythonSDK/html/modules/c4d.threading/index.html
On 12/10/2015 at 01:55, xxxxxxxx wrote:
Sorry, I am not sure what you mean.
Do you mean I should start a second (threaded) process to check for another object?
-Pim
On 12/10/2015 at 02:03, xxxxxxxx wrote:
i think yes, or python threading
or make doc notification for your plug-in/script - user should select 2 objects in point mode
On 12/10/2015 at 02:41, xxxxxxxx wrote:
Hello,
the point mode etc. defines how the default tools work. You can still select another object using SetActiveObject().
Best wishes,
Sebastian
On 12/10/2015 at 04:01, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Hello,
the point mode etc. defines how the default tools work. You can still select another object using SetActiveObject().
Best wishes,
Sebastian
The issue is that the want to select another object when in point mode.
Switch between a Null object and points of a spline.
Selecting both objects, then go to point mode, does not resolve the issue.
Once a spline point is selected, the user cannot select the null.
Perhaps there is another option?
-Pim
On 12/10/2015 at 07:45, xxxxxxxx wrote:
The only place where there is an enforced mode select restriction is in the editor view using the mouse cursor. Because the mouse is acting as the tool.
But you should still be able to select things in the OM and with code regardless of what mode you're in.
With a few objects in the scene and also C4D in points mode.
This script will always select the next object no matter what type it is.
import c4d
def main() :
op = doc.GetActiveObject()
if op.GetNext() is not None:
nextOp = op.GetNext()
nextOp.SetBit(c4d.BIT_ACTIVE)
c4d.EventAdd()
if __name__=='__main__':
main()
-ScottA
On 12/10/2015 at 08:23, xxxxxxxx wrote:
Originally posted by xxxxxxxx
The only place where there is an enforced mode select restriction is in the editor view using the mouse cursor. Because the mouse is acting as the tool.
-ScottA
The thing is, that the user wants to select the null.
In the plugin I have no control / I do not know when this should be done.
I thought about using the keyboard.
That would trigger the selection of the null and that is doable in the plugin, because then I have an event I can react upon.
See another post, for my question how to get a character input.
Thanks, Pim
On 12/10/2015 at 08:37, xxxxxxxx wrote:
I'm still using R13 so I'm not sure about this.
But I thought I remember hearing something about sticky keys. Where while you hold down a certain key it switches the tool mode. And then when you let go of the key it goes back to the originally set tool mode.
I could be wrong though.
-ScottA
On 12/10/2015 at 12:09, xxxxxxxx wrote:
I think that you can switch between selection using control.
But I could be wrong.
-Pim