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

Remove FlutterWindowProperties and get the screen size automatically #72

Merged
merged 1 commit into from
Apr 27, 2021

Conversation

swift-kim
Copy link
Member

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.

Fixes flutter-tizen/flutter-tizen#83 (screen size issue).

The target branch of this PR should be changed after #67 is merged.

Copy link

@bbrto21 bbrto21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
@swift-kim swift-kim changed the base branch from embedders-for-profiles to flutter-2.0.1-tizen April 27, 2021 01:28
@swift-kim swift-kim merged commit 94bd946 into flutter-tizen:flutter-2.0.1-tizen Apr 27, 2021
swift-kim added a commit that referenced this pull request Jun 7, 2021
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Sep 27, 2021
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
@swift-kim swift-kim mentioned this pull request Nov 1, 2021
7 tasks
swift-kim added a commit that referenced this pull request Nov 14, 2021
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Dec 9, 2021
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Dec 17, 2021
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Feb 7, 2022
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Feb 11, 2022
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request May 12, 2022
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim added a commit that referenced this pull request Aug 5, 2022
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
swift-kim pushed a commit that referenced this pull request Sep 1, 2022
Otherwise, depending on Impeller will cause an explicit dependency on
whatever VM variant :libdart picks. And, some other unit-test in the
engine explicitly link in the JIT variant which leads to duplicate
symbol errors in profile and release modes.
swift-kim added a commit that referenced this pull request Sep 1, 2022
…72)

The screen width/height/dpi values returned by the system_info API
are just pre-defined values and do not represent the actual
properties of the display. The correct values can be only obtained
after ecore_wl2_display is created.
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.

[arm64] Current status on rpi4
2 participants