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

[Bug 19541] Improve clipboard owner check on win#5451

Merged
livecodepanos merged 1 commit into
livecode:develop-8.1from
montegoulding:bugfix-19541
May 12, 2017
Merged

[Bug 19541] Improve clipboard owner check on win#5451
livecodepanos merged 1 commit into
livecode:develop-8.1from
montegoulding:bugfix-19541

Conversation

@montegoulding
Copy link
Copy Markdown
Contributor

This patch modifies the windows clipboard ownership
check to return true for a cleared or new raw clipboard
item so private clipboard data set on an otherwise
cleared clipboard is not inadvertently cleared.

A NULL m_object of the raw clipboard item is owned in the
sense that it should only exist if the clipboard has been
set.

This patch modifies the windows clipboard ownership
check to return true for a cleared or new raw clipboard
item so private clipboard data set on an otherwise
cleared clipboard is not inadvertently cleared.

A NULL m_object of the raw clipboard item is owned in the
sense that it should only exist if the clipboard has been
set.
@mention-bot
Copy link
Copy Markdown

@montegoulding, thanks for your PR! By analyzing the history of the files in this pull request, we identified @livecodefraser to be a potential reviewer.

@montegoulding montegoulding added this to the 8.1.5-rc-1 milestone May 12, 2017
@runrevmark
Copy link
Copy Markdown
Contributor

@livecode-vulcan review ok 5499ad2

@livecode-vulcan
Copy link
Copy Markdown
Contributor

💙 review by @runrevmark ok 5499ad2

livecode-vulcan added a commit that referenced this pull request May 12, 2017
[Bug 19541] Improve clipboard owner check on win

This patch modifies the windows clipboard ownership
check to return true for a cleared or new raw clipboard
item so private clipboard data set on an otherwise
cleared clipboard is not inadvertently cleared.

A NULL m_object of the raw clipboard item is owned in the
sense that it should only exist if the clipboard has been
set.
@livecode-vulcan
Copy link
Copy Markdown
Contributor

😞 test failure 5499ad2

  • try-community-armv6-android-api8: success
  • try-community-armv6-android-api9: success
  • try-community-js-emscripten-sdk1.35: success
  • try-community-universal-ios-iphoneos10.3: success
  • try-community-universal-ios-iphonesimulator10.3: success
  • try-community-universal-mac-macosx10.6: success
  • try-community-universal-mac-macosx10.9: success
  • try-community-x86-linux-debian7: success
  • try-community-x86-linux-debian8: success
  • try-community-x86_64-linux-debian7: success
  • try-community-x86_64-linux-debian8: success
  • try-community-x86-win32: success
  • try-community-x86_64-win32: failure

@livecodeali
Copy link
Copy Markdown
Member

@livecode-vulcan retry 5499ad2

livecode-vulcan added a commit that referenced this pull request May 12, 2017
[Bug 19541] Improve clipboard owner check on win

This patch modifies the windows clipboard ownership
check to return true for a cleared or new raw clipboard
item so private clipboard data set on an otherwise
cleared clipboard is not inadvertently cleared.

A NULL m_object of the raw clipboard item is owned in the
sense that it should only exist if the clipboard has been
set.
@livecode-vulcan
Copy link
Copy Markdown
Contributor

😎 test success 5499ad2

  • try-community-armv6-android-api8: success
  • try-community-armv6-android-api9: success
  • try-community-js-emscripten-sdk1.35: success
  • try-community-universal-ios-iphoneos10.3: success
  • try-community-universal-ios-iphonesimulator10.3: success
  • try-community-universal-mac-macosx10.6: success
  • try-community-universal-mac-macosx10.9: success
  • try-community-x86-linux-debian7: success
  • try-community-x86-linux-debian8: success
  • try-community-x86_64-linux-debian7: success
  • try-community-x86_64-linux-debian8: success
  • try-community-x86-win32: success
  • try-community-x86_64-win32: success

@livecodepanos livecodepanos merged commit a37e470 into livecode:develop-8.1 May 12, 2017
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.

6 participants