Skip to content

PixelStream bugfix: do not set ContentSize to zero on empty SizeHints event#21

Merged
rdumusc merged 1 commit intoBlueBrain:masterfrom
rdumusc:master
May 20, 2016
Merged

PixelStream bugfix: do not set ContentSize to zero on empty SizeHints event#21
rdumusc merged 1 commit intoBlueBrain:masterfrom
rdumusc:master

Conversation

@rdumusc
Copy link
Copy Markdown

@rdumusc rdumusc commented May 20, 2016

No description provided.

@dnachbaur
Copy link
Copy Markdown
Contributor

+1

@dnachbaur
Copy link
Copy Markdown
Contributor

Changelog?

@rdumusc
Copy link
Copy Markdown
Author

rdumusc commented May 20, 2016

I can add a Changelog entry, but its a very small bugfix that probably nobody ever observed

@rdumusc
Copy link
Copy Markdown
Author

rdumusc commented May 20, 2016

done

@rdumusc rdumusc merged commit 4490feb into BlueBrain:master May 20, 2016
rdumusc pushed a commit to rdumusc/Tide that referenced this pull request Jan 22, 2018
The bug was introduced in BlueBrain#21 by using a binary copy of MovieContent via
Content::clone(). The binary copy did not (and should not) recreate the
actions, as they are already serialized by Content when sending to the
wall processes. They should only be created when making a new object on
the master process, which includes loading from xml.

Other minor cleanups, including creating the actions for
PixelStreamContents only when loading from xml to be consistent, even
though in this case the the order of the operations was different so
the problem was not visible.
rdumusc pushed a commit that referenced this pull request Jan 23, 2018
The bug was introduced in #21 by using a binary copy of MovieContent via
Content::clone(). The binary copy did not (and should not) recreate the
actions, as they are already serialized by Content when sending to the
wall processes. They should only be created when making a new object on
the master process, which includes loading from xml.

Other minor cleanups, including creating the actions for
PixelStreamContents only when loading from xml to be consistent, even
though in this case the the order of the operations was different so
the problem was not visible.
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.

2 participants