Skip to content

Conversation

@bbrto21
Copy link

@bbrto21 bbrto21 commented Jun 27, 2022

  • The view should be responsible for the life cycle of the engine, and
    the engine should stop naturally when the view is destroyed.

Signed-off-by: Boram Bae boram21.bae@samsung.com

* The view should be responsible for the life cycle of the engine, and
  the engine should stop naturally when the view is destroyed.

Signed-off-by: Boram Bae <boram21.bae@samsung.com>
* There is no need to explicitly assign null to a unique pointer in
  the destructor of engine.

Signed-off-by: Boram Bae <boram21.bae@samsung.com>
@bbrto21 bbrto21 merged commit f9b374c into flutter-tizen:flutter-3.0.0-tizen Jun 29, 2022
swift-kim pushed a commit that referenced this pull request Aug 5, 2022
* The view should be responsible for the life cycle of the engine, and
  the engine should stop naturally when the view is destroyed.
* There is no need to explicitly assign null to a unique pointer in
  the destructor of engine.

Signed-off-by: Boram Bae <boram21.bae@samsung.com>
swift-kim pushed a commit that referenced this pull request Sep 1, 2022
* The view should be responsible for the life cycle of the engine, and
  the engine should stop naturally when the view is destroyed.
* There is no need to explicitly assign null to a unique pointer in
  the destructor of engine.

Signed-off-by: Boram Bae <boram21.bae@samsung.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants