-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add data.Frame event #38
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Copyright (c) HBP 2016 Jafet Villafranca <jafet.villafrancadiaz@epfl.ch> | ||
|
||
set(ZEROBUFDATA_INCLUDE_NAME zerobuf/data) | ||
|
||
include(zerobufGenerateCxx) | ||
zerobuf_generate_cxx(ZEROBUFDATA | ||
${OUTPUT_INCLUDE_DIR}/${ZEROBUFDATA_INCLUDE_NAME} frame.fbs) | ||
|
||
set(ZEROBUFDATA_PUBLIC_HEADERS ${ZEROBUFDATA_HEADERS}) | ||
set(ZEROBUFDATA_LINK_LIBRARIES PUBLIC ZeroBuf) | ||
|
||
set(ZEROBUFDATA_INCLUDE_NAME zerobuf/data) | ||
set(ZEROBUFDATA_NAMESPACE zerobufdata) | ||
common_library(ZeroBufData) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
// Copyright (c) 2016, Human Brain Project | ||
// Jafet.VillafrancaDiaz@epfl.ch | ||
// | ||
namespace zerobuf.data; | ||
|
||
// Event containing the data frame range information. It is based on the same | ||
// units as the zerobuf.render.Frame, i.e. number of frames. | ||
// It may be used as a base event that defines the available range of frames | ||
// coming from a certain data source, being also possible to use the | ||
// zerobuf.render.Frame event at the same time, which would define the frame | ||
// subrange used by a rendering animation to loop within. | ||
|
||
table Frame | ||
{ | ||
// starting frame number in the data frame range | ||
start:uint; | ||
// end frame number in the data frame range | ||
end:uint; | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all could have been handled in the GUI, why did we add a new event ?
The GUI is the one who commands a frame ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The GUI only knows what it receives from Livre, which at the moment is the render.Frame event (start, current, end, delta). Now, Livre and the GUI are using this interval of frames to loop between them in an animation, and this range can also be modified from the GUI, being possible to focus on a specific segment of the visualization.
This new data.Frame event is adding semantics for the range of frames that the data source provides, so we can easily know the available range from the GUI, but at the same time change the range within which the rendering should animate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We ( @favreau and I ) had this conclusion 6 months ago and it was rejected :) Anyways good to have it.