Violating such a basic rule makes it a nightmare to maintain a bigger project in the long run. If not, the modification will be something like replacing obj.Shape access with Part.getShape(obj), which is essentially what this patch does. I think it is very much doable without writing something Wern...

ah ... that's a pity. In your -asm3 branch it is possible. Is it very difficult to implement it here also ? Is there a technical hurdle ? May-be there would be other use-cases than Asm4 The technical difficulty is to make it secure. Calling into object opens up a lot more attack surface. I'll work ...

EDIT: does this allow to call methods on objects ? Like : No, you cannot call methods. The equivalent expression will be Group.<<Box.>>.Placement.Matrix * Group.<<$Cube.>>.Placement.Matrix ^ -1 The result is a matrix, but you can bind it directly to a Placement property.

The latest update brought improvements in Expression auto complete: now the labels of objects can be used and a completion list is shown. However, this ends after the constraints. Especially the named constraints are not offered. It used to be like that: Already when typing something like SketchXXX...

Thanks for the detailed review, wmayer. You are a great project leader without doubt. 50cefc5104d62fc2d1ba87c7df79a28ff6a6ef5c Console: improve console logging facility Why is the if-check in ConsoleSingleton::Log reversed? Oops, that must be a typo or something. aa7d780f5d6ea492d8c379d810fff420f3ff...

mlampert wrote: ↑Mon Sep 02, 2019 3:01 am What's the status on this? Is the null Shape property here to stay?

There are quite a few exceptions in Path due to this and I need to know how to proceed.

There should be no null shape any more in upstream. Please report if otherwise.

chrisb wrote: ↑Sun Sep 01, 2019 5:16 pm Is this the place to add more regressions?
- Autocompletion of expressions is not working

There is a fix for auto complete in recent accepted PR. Which version have you tried. Maybe you can report to the big merge thread first.

Zolko wrote: ↑Sun Sep 01, 2019 3:06 pm hum, thinking of it, I see the problem: you can't propose the commit if it's untested, and I can't test Asm4 because I can't compile Pyside2/Shiboken.

I have already submitted the PR here

PR link here Changes include: Add internal function list/tuple(). Spreadsheet range expression can be expanded to list or tuple, e.g. list(A1:A10) Use Python number protocol in OperatorExpression, so you can doing something like matrix * vector, rotation * vector, or formatted string like <<This is ...

So what's really missing is the possibility, in the ExpressionEngine, to make operations on Placements (or on matrices, quaternions, vectors, I don't know). If you could extract that part from your version of the ExpressionEngine parser and make a PR for v19 would be great. Yes, I know. If you are ...