For `type` "path" - a valid SVG path with the pixel values replaced by data values in `xsizemode`/`ysizemode` being "scaled" and taken unmodified as pixels relative to `xanchor` and `yanchor` in case of "pixel" size mode. There are a few restrictions / quirks
(self)
| 321 | |
| 322 | @property |
| 323 | def path(self): |
| 324 | """ |
| 325 | For `type` "path" - a valid SVG path with the pixel values |
| 326 | replaced by data values in `xsizemode`/`ysizemode` being |
| 327 | "scaled" and taken unmodified as pixels relative to `xanchor` |
| 328 | and `yanchor` in case of "pixel" size mode. There are a few |
| 329 | restrictions / quirks only absolute instructions, not relative. |
| 330 | So the allowed segments are: M, L, H, V, Q, C, T, S, and Z arcs |
| 331 | (A) are not allowed because radius rx and ry are relative. In |
| 332 | the future we could consider supporting relative commands, but |
| 333 | we would have to decide on how to handle date and log axes. |
| 334 | Note that even as is, Q and C Bezier paths that are smooth on |
| 335 | linear axes may not be smooth on log, and vice versa. no |
| 336 | chained "polybezier" commands - specify the segment type for |
| 337 | each one. On category axes, values are numbers scaled to the |
| 338 | serial numbers of categories because using the categories |
| 339 | themselves there would be no way to describe fractional |
| 340 | positions On data axes: because space and T are both normal |
| 341 | components of path strings, we can't use either to separate |
| 342 | date from time parts. Therefore we'll use underscore for this |
| 343 | purpose: 2015-02-21_13:45:56.789 |
| 344 | |
| 345 | The 'path' property is a string and must be specified as: |
| 346 | - A string |
| 347 | - A number that will be converted to a string |
| 348 | |
| 349 | Returns |
| 350 | ------- |
| 351 | str |
| 352 | """ |
| 353 | return self["path"] |
| 354 | |
| 355 | @path.setter |
| 356 | def path(self, val): |