Questions about options attribute

Hi everyone,

I’ve been working on getting the ipyleaflet models to clojure kernel and getting the right values of options attribute of each model was the most error prone part.

Which made me wonder, how is the end user expected to use the options attribute on the python side? Is there any useful example of passing a custom options list to the widget constructor, like Map(options=[foo, bar, baz])? Is there any useful example of using the widget’s default options and mutate it after initializing?

[nighcoder]

I also noticed something wich looks like a bug. If I declare the widget, render it, drag the map, then look at the state of the widget, there’s a new key there named: :_dragging.

I’ve checked the clojure code and I don’t use the :_dragging key anywhere, only :dragging which should mirror the python property. My guess is that the JavaScript is sending this property in a msg-update, since I see it defined here. Note that the JavaScript code includes also a definition for dragging, but I don’t see it used lower in code, only _dragging.

[martinRenou]

Indeed there are some issues with those attributes. Do you mind opening a separate issue for that? It seems unrelated to the original discussion.