Skip to content

Bugfix: properly activate and deactivate fps fields when necessary#732

Open
Perdu wants to merge 1 commit intoclementgallet:masterfrom
Perdu:fix_fps_fields
Open

Bugfix: properly activate and deactivate fps fields when necessary#732
Perdu wants to merge 1 commit intoclementgallet:masterfrom
Perdu:fix_fps_fields

Conversation

@Perdu
Copy link
Copy Markdown
Contributor

@Perdu Perdu commented Apr 14, 2026

movieRecording is not initialized yet and isChecked() does not return an accurate value at that point in the code.
As a consequence, we can't edit framerate on new record (without switching to playback and then back to recording mode).
As a fix, we activate the fields by default and deactivate them on movie load.

(Fixes my 59c2985 changes)

movieRecording is not initialized yet and isChecked() does not return
an accurate value at that point in the code.
As a fix, we activate the fields by default and deactivate them on
movie load.
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.

1 participant