From b512ec023528db01b5d8229fd2c25e378955a9c3 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Mon, 6 May 2019 18:13:03 -0600 Subject: [PATCH] Trival removal of spaces dangling at the end of lines. --- include/graphics/twm4nx/iapplication.hxx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/graphics/twm4nx/iapplication.hxx b/include/graphics/twm4nx/iapplication.hxx index 9818da1f0..7ca62c4cc 100644 --- a/include/graphics/twm4nx/iapplication.hxx +++ b/include/graphics/twm4nx/iapplication.hxx @@ -95,7 +95,7 @@ namespace Twm4Nx * called. These two behaviors are mutually exlusive. * * NOTE: Both the start() and getSubMenu() return values are ignored - * if the event() method returns an event with recipient = + * if the event() method returns an event with recipient = * EVENT_RECIPIENT_APP. In that case, the application will be fully * responsible for handling the menu selection event. * @@ -116,7 +116,7 @@ namespace Twm4Nx * typically, create a new thread to host the application. * * NOTE: Both the start() and getSubMenu() return values are ignored - * if the event() method returns an event with recipient = + * if the event() method returns an event with recipient = * EVENT_RECIPIENT_APP. In that case, the application will be fully * responsible for handling the menu selection event. * @@ -162,7 +162,7 @@ namespace Twm4Nx * @return. Either, (1) an event with recipient = EVENT_RECIPIENT_APP * that will be generated when menu item is selected, or (2) any other * value (preferabley zero) that indicates that standard, built-in - * event handling should be used. + * event handling should be used. */ virtual uint16_t getEvent(void) = 0;