Skip to content

[2108] Improve actor creation tool using the latest selection dialog changes#2110

Open
gcoutable wants to merge 1 commit intomainfrom
gco/enh/new-actor-selection-dialog
Open

[2108] Improve actor creation tool using the latest selection dialog changes#2110
gcoutable wants to merge 1 commit intomainfrom
gco/enh/new-actor-selection-dialog

Conversation

@gcoutable
Copy link
Copy Markdown
Member

@gcoutable gcoutable commented Apr 2, 2026

Bug: #2108
Signed-off-by: Guillaume Coutable guillaume.coutable@obeo.fr

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@gcoutable
Copy link
Copy Markdown
Member Author

I put in draft because there are upcoming change on the selection dialog I would like to take into account.

@gcoutable gcoutable linked an issue Apr 2, 2026 that may be closed by this pull request
@gcoutable gcoutable force-pushed the gco/enh/new-actor-selection-dialog branch 3 times, most recently from 5794eff to 115c0ce Compare April 7, 2026 13:52
@gcoutable gcoutable marked this pull request as ready for review April 7, 2026 14:18
@gcoutable gcoutable force-pushed the gco/enh/new-actor-selection-dialog branch from 115c0ce to 6b4e1d3 Compare April 7, 2026 14:20
@gcoutable gcoutable changed the title [2108] WIP Improve actor creation tool [2108] Improve actor creation tool using the latest selection dialog changes Apr 7, 2026
@gcoutable gcoutable force-pushed the gco/enh/new-actor-selection-dialog branch 2 times, most recently from af053dd to ae13828 Compare April 8, 2026 09:00
…changes

Bug: #2108
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@gcoutable gcoutable force-pushed the gco/enh/new-actor-selection-dialog branch from ae13828 to 90abbc8 Compare April 8, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to create an actor from the Part palette

1 participant