On Sat, Oct 13, 2018 at 8:06 PM Bram Moolenaar <[email protected]> wrote: > > > We have made great progress increasing test coverage, thanks for > everybody helping out! > > There is one big gap: The GUI code. We usually test by putting text in > the input buffer, which means we totally bypass all the GUI event > handling. > > For GTK we could inject events at the level of the callback functions. > E.g., invoke key_press_event() with a specific key event. And I suppose > call key_release_event() later to make everything work. > > We would need to do this for every callback function, and fill in the > event. I wonder if there is a more generic approach. > > For MS-Windows we can probably synthesise Windows messages, since they > are all handled in process_message(). Can we send ourselves a message? > > Which leaves two kinds of holes: - MacVim - Linux GUIs other than GTK (Athena, Motif, ...) - and in addition, can we be sure that GTK2 and GTK3 can be tested the same way?
Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
