Bug: Wrong position of %wrap_handle about pythonocc-generator HOT 7 CLOSED

Interface files were updated on the pythonocc-core side (see tpaviot/pythonocc-core@1d7982b). However, there's not any difference at compilation time, what about runtime ?

from pythonocc-generator.

I am working on it. It requires many new imports. Takes a while to go through it manually.

from pythonocc-generator.

@tpaviot What I am currently working on is the following:

I renamed all opencascade::handle occurences to OccHandle_XXX. This OccHandl_XXX is defined in %wrap_handle.

Therefore, to successfully compile the module, the wrap_handle of a class must be imported. This way, you can make sure to not forget any import related to handles.

from pythonocc-generator.

IMHO, failing early (at compile time) is much better than failing at runtime (at some user).

It requires too many tests to check all of these problems at runtime.

from pythonocc-generator.

This is not yet fixed in the generator! There are still wrap_handles for the H-Classes, e.g. %wrap_handle(StepShape_HArray1OfShapeDimensionRepresentationItem) at the bottom of StepShape.i

from pythonocc-generator.

I fixed it locally. Shall I make a PR?

from pythonocc-generator.

No need for a PR, I cherry-picked it. Thank you.

from pythonocc-generator.