diff options
Diffstat (limited to 'NxWidgets/nxwm/src/cfullscreenwindow.cxx')
-rw-r--r-- | NxWidgets/nxwm/src/cfullscreenwindow.cxx | 77 |
1 files changed, 0 insertions, 77 deletions
diff --git a/NxWidgets/nxwm/src/cfullscreenwindow.cxx b/NxWidgets/nxwm/src/cfullscreenwindow.cxx index 6b0d13fa0..2087543cd 100644 --- a/NxWidgets/nxwm/src/cfullscreenwindow.cxx +++ b/NxWidgets/nxwm/src/cfullscreenwindow.cxx @@ -96,13 +96,6 @@ CFullScreenWindow::~CFullScreenWindow(void) bool CFullScreenWindow::open(void) { - // Get the window control - - NXWidgets::CWidgetControl *control = m_window->getWidgetControl(); - - // Register to receive callbacks on a few select window events - - control->addWindowEventHandler(this); return true; } @@ -174,74 +167,4 @@ void CFullScreenWindow::clickStopIcon(int index) } #endif -/** - * Handle an NX window mouse input event. - * - * @param e The event data. - */ - -#ifdef CONFIG_NX_MOUSE -void CFullScreenWindow::handleMouseEvent(void) -{ - // The logic path here is tortuous but flexible: - // - // 1. A listener thread receives mouse input and injects that into NX - // 2. In the multi-user mode, this will send a message to the NX server - // 3. The NX server will determine which window gets the mouse input - // and send a message to the listener. - // 4. The listener will call the NX message dispatcher will will do the - // message callback. - // 5. The callback goes into an instance of NXWidgets::CCallback that is - // part of the CWidget control. - // 6. That callback will update mouse information then raise the - // mouse event, - // 7. Which will finally call this function -- still running deep on the - // stack in the listener thread. - // 8. This function will then call back into the wiget control to process - // the mouse input. - - // Get the CWidgetControl associated with the window - - NXWidgets::CWidgetControl *control = m_window->getWidgetControl(); - - // And perform a poll - - control->pollEvents(); -} -#endif - -/** - * Handle a NX window keyboard input event. - */ - -#ifdef CONFIG_NX_KBD -void CFullScreenWindow::handleKeyboardEvent(void) -{ - // The logic path here is tortuous but flexible: - // - // 1. A listener thread receives keyboard input and injects that into NX - // 2. In the multi-user mode, this will send a message to the NX server - // 3. The NX server will determine which window gets the keyboard input - // and send a message to the listener. - // 4. The listener will call the NX message dispatcher will will do the - // message callback. - // 5. The callback goes into an instance of NXWidgets::CCallback that is - // part of the CWidget control. - // 6. That callback will update keyboard information then raise the - // keyboard event, - // 7. Which will finally call this function -- still running deep on the - // stack in the listener thread. - // 8. This function will then call back into the wiget control to process - // the keyboard input. - - // Get the CWidgetControl associated with the window - - NXWidgets::CWidgetControl *control = m_window->getWidgetControl(); - - // And perform a poll - - control->pollEvents(); -} -#endif - |