Remove return values on some closures; replace some custom widgets #432
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.
fn AppData::handle_messages
previously returnedAction
, however:Action::empty()
andAction::UPDATE
, hence we could replace withbool
UPDATE
when any message was removed from the stack is a good enough approximation, hence we don't need a return value at allSimilarly,
Adapt
's message and timer handlers can also get away without using any return values (on the assumption that a timer is only requested when it is likely that something will happen, and thatAdapt
only makes things happen by adjusting its state; these appear reasonable assumptions given the intended usages).Also, replace a couple more instances of custom widgets in examples.
Also increase the default font size to 16px (12pt).