Skip to content

Replace ecore_pipe to glib api in TizenEventLoop - #192

Open
JSUYA wants to merge 1 commit into
flutter-tizen:masterfrom
JSUYA:remove_ecore_pipe
Open

Replace ecore_pipe to glib api in TizenEventLoop#192
JSUYA wants to merge 1 commit into
flutter-tizen:masterfrom
JSUYA:remove_ecore_pipe

Conversation

@JSUYA

@JSUYA JSUYA commented Aug 7, 2026

Copy link
Copy Markdown
Member

Replace Ecore pipes and per-task timers with a single GLib source that tracks the earliest Flutter task on the Tizen main context.

Preserve delayed execution, posting order, worker-thread scheduling, re-entrant callbacks, and source cleanup. Remove the remaining Ecore dependency from display refresh reporting by using the existing 60 Hz constant.

#146

@JSUYA
JSUYA force-pushed the remove_ecore_pipe branch from 609e79c to 64daebe Compare August 7, 2026 06:02
Replace Ecore pipes and per-task timers with a single GLib source that
tracks the earliest Flutter task on the Tizen main context.

Preserve delayed execution, posting order, worker-thread scheduling,
re-entrant callbacks, and source cleanup. Remove the remaining Ecore
dependency from display refresh reporting by using the existing 60 Hz
constant.
@JSUYA
JSUYA force-pushed the remove_ecore_pipe branch from 64daebe to a2b7f08 Compare August 7, 2026 07:15
@JSUYA

JSUYA commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

@codex review

@JSUYA JSUYA self-assigned this Aug 7, 2026
@JSUYA JSUYA added the enhancement New feature or request label Aug 7, 2026
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: a2b7f0810e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

} else {
display.refresh_rate = 1 / fps;
}
display.refresh_rate = 60.0;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The Linux embedder (fl_display_monitor.cc) gets the real per-monitor refresh_rate via gdk_monitor_get_refresh_rate() and updates it on hotplug. GDK isn't available on Tizen, but the same value is obtainable by directly parsing the refresh field from the wl_output.mode event - no Ecore needed. Could you at least file a follow-up issue for the hardcoded 60.0 instead of leaving it silent?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

ecore_animator_frametime_get() returns the default value of 1 / 60.0f unless otherwise set. Therefore, apply 60.0 to match existing behavior.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You're right that ecore_animator_frametime_get() defaults to 60, but it doesn't actually reflect the real monitor's frame rate, so this will need to be fixed eventually. Even if not right now, could we at least leave a follow-up issue for it?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

um... #193 I have made an issue. However, I am not sure if we will be able to resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants