-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor plotting and block handling #177
Conversation
6cb2b13
to
b378339
Compare
b378339
to
a46f832
Compare
a46f832
to
ad725ac
Compare
Use approach with non-blocking IO and draw() (process data and draw in the UI thread).
Use single block list instead of three, filter if needed.
Make sure there's no inverse dependency here, do the remote source (flowgraph) registration via message handling. Also remove unused remote flowgraphs if the blocks change.
Simplifies Block class, can be used later with messages.
Remove subclass, it's not needed.
Do not silently do nothing for std::complex etc.
d0aedce
to
a2374a7
Compare
namespace opendigitizer::meta { | ||
|
||
template<typename T> | ||
struct is_dataset { |
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.
There is an existing gr::DataSetLike<T>
concept that defines this.
|
||
for (const auto &s : sources) { | ||
if (!s.IsMap()) ERROR_RETURN("source is no map"); | ||
if (!s.IsMap()) throw std::runtime_error("source is no map"); |
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.
If you use gr::exception(...)
, you would get implicitly also the std::source_location
and time trace when/where this exception was thrown.
Things that this does not yet contain: