Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

[22780] Ensure the compositorType property can be set to "none" #7378

Open
wants to merge 1 commit into
base: develop-9.6
Choose a base branch
from

Conversation

livecodepanos
Copy link
Contributor

This patch ensures the compositorType property can be set to "none".
Previously this enumeration value was set to read-only, thus an error
was thrown when attempting to set the compositorType to "none"

Closes https://quality.livecode.com/show_bug.cgi?id=22780

This patch ensures the compositorType property can be set to "none".
Previously this enumeration value was set to read-only, thus an error
was thrown when attempting to set the compositorType to "none"
@livecodepanos livecodepanos added this to the 9.6.1-rc-1 milestone Jun 12, 2020
@livecodepanos livecodepanos modified the milestones: 9.6.1-rc-1, 9.6.2-rc-1 Aug 20, 2020
@livecodepanos livecodepanos modified the milestones: 9.6.2-rc-1, 9.6.3-rc-1 Nov 24, 2020
Copy link
Contributor

@runrevmark runrevmark left a comment

Choose a reason for hiding this comment

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

So we need to check whether this was a 'bug' introduced in the refactor - the docs state none is returned if no compositor... And this change allows setting to none certainly, but it will still return empty in that case.

It might be just a docs bug if none has never figured as a compositor type!

@runrevmark runrevmark added the WIP label Jun 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants