On 2016-01-04 17:42:37 +0000, Snke Ludwig said:

  1. Are GUI events for the different platforms are abstracted or native?

Native. For Windows, you basically just have to create your window as
usual. DispatchMessage is called internally to dispatch events to the
window procedure.

I skimed through the vide.d sources to get an idea how it's done. This
is my current understanding, please feel free to correct:

  1. vibe uses an own window class

  2. it creates a windows at position 0,0 with dimensions 0,0 as message
    only window (so not visible)

  3. window messages are handled by Win32EventDriver.onMessage(...)

  4. this handler handles manual and socket events but no GUI events.
    There is currently no way to register a "callback" like for file or
    network events through the vibe framework.

  5. all messages not handled are forwarded to the default window
    procedure (I think it's the OS at this point)

Assuming I'm right so far, the following should be true as well:

  1. to implement a GUI application I have to subcalls the vibe window
    class and provide my own window message handling function and later
    call the vibe window function to keep everything running. My own
    messages will be processed BEFORE vibe's messages in this case.

General questions:

a) What is this "filewriters" stuff about?

b) Do you plan to abstract away the GUI event handling like it's done
for files and network stuff?

Robert M. Münch
http://www.saphirion.com
smarter | better | faster