Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] CAELiveMapper init not working properly #11

Open
pdolif opened this issue Aug 3, 2021 · 0 comments
Open

[BUG] CAELiveMapper init not working properly #11

pdolif opened this issue Aug 3, 2021 · 0 comments
Labels

Comments

@pdolif
Copy link
Member

pdolif commented Aug 3, 2021

The CAELiveMapper on init searches for a node of type Widget in the model (see https://github.com/rwth-acis/CAE-WireframingEditor/blob/master/src/js/mapper/CAELiveMapper.js#L45).
If no widget was found, it tries to create one (see https://github.com/rwth-acis/CAE-WireframingEditor/blob/master/src/js/mapper/CAELiveMapper.js#L89).

This is a nice-to-have feature, because every new frontend component needs to have a widget node.
However, it is not working properly in the CAE right now. The code of the init function is executed, but no widget is created.
One possible explanation for this could be, that at the time where the init function is called in the wireframing widget (see https://github.com/rwth-acis/CAE-WireframingEditor/blob/master/src/widget.js#L27), the SyncMeta widgets as the Canvas are not yet fully loaded. Therefore, they do not get the events sent from the wireframing editor (e.g. create new node for widget).

If you wait a few seconds before calling CAELiveMapper.init(editor), it seems to be working fine. This needs to be investigated and tested a bit more.

@pdolif pdolif added the bug label Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant