Impossibility to use something else than Vec3f to specfy the layout of a new in python

[rgiot]

When trying to set the layout property of a node using a 3-sized tuple, we obtain such error

TypeError: LayoutProperty.__setitem__(): arguments did not match any overloaded call:
  overload 1: argument 2 has unexpected type 'tuple'
  overload 2: argument 1 has unexpected type 'node'

As it is very common in python to use tuples instead of Vec3f, tuple of 3 elements should be allowed. The same comment apply for lists

Issue #16 let suggest that I should not have this error. Maybe it is not activated in the pip version of python ?

[bpinaud]

Why not simply using Tulip datatype:

c = tlp.Coord(3,4,1)

[tulipdev]

Of course this works, but it is somewhat counter intuitive for people new to Tulip's API. The pythonic way would be assigning c = [x,y,z], but I thought that was already possible, we had a discussion on that way back then. -- Benjamin

…

On Tue, 4 Jun 2019 at 05:21, Bruno Pinaud ***@***.***> wrote: Why not simply using Tulip datatype: c = tlp.Coord(3,4,1) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#120?email_source=notifications&email_token=AEJ73FRHARQMCKKMFVV3Q3LPYV4M7A5CNFSM4HSQ7TX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2SPMI#issuecomment-498411441>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEJ73FWVKS5ARALTVZAR2CDPYV4M7ANCNFSM4HSQ7TXQ> .

[fqueyroi]

Maybe you get this error because you use a tuple of integers instead of floats as input. You should try

viewLayout[n] = (0.,0.,0.) or viewLayout[n] = (0.0,0.0,0.0)

Since, according to the description of this change in Tulip-Python 5.1:

Warning

In order to successfully set a property values using a tuple, the types of the elements it contains and its length are constrained according to the the property type:

• for tlp.ColorProperty: the tuple must contain 3 or 4 integers between 0 and 255
• for tlp.LayoutProperty and tlp.SizeProperty: the tuple must contain 2 or 3 float (meaning the value will fail to be set if the tuple contains integers)

[anlambert]

As explained by @fqueyroi , the issue you observed is due to the fact you are using int litterals instead of float ones in your tuple.

I will try to see if I can improve this behavior but I remember that I had no choice to proceed like this at the time I implemented this (in order to be able to create graph properties on the fly from Python using type inference).

[rgiot]

@fqueyroi Thanks for pointing that, I have never thought about that. I'll pay more attention to the doc next time ...
@anlambert ok, so feel free to close the issue if it is not doable