diff options
| author | Pietro Gagliardi <[email protected]> | 2014-04-02 10:17:24 -0400 |
|---|---|---|
| committer | Pietro Gagliardi <[email protected]> | 2014-04-02 10:17:24 -0400 |
| commit | d1c0b9b29d44a0cc9f81001a53d7d4a0b3a46576 (patch) | |
| tree | ca69cf48d97204a3eeb590862fa69e347741ffe0 | |
| parent | 973853c835d81a877191e209dcc710a6ec00a412 (diff) | |
Not using PostThreadMessage() (a few commits back) seems to fix the weird Invalid thread ID. error that happens when running package ui-based programs in wine for the first time (I assume that issue is related to the one that led to the PostThreadMessage() fix).
| -rw-r--r-- | todo.md | 4 |
1 files changed, 0 insertions, 4 deletions
@@ -63,10 +63,6 @@ super ultra important things: - 32-bit: it works, but if I save the class name converted to UTF-16 beforehand, wine indicates that the class name is replaced with the window title, so something there is wrong... - david wendt is telling me he's getting frequent crashes on his end with the GTK+ amd64 build... TODO re-evaluate; I think I fixed them all ages ago now -- occasionally I get - panic: error sending message to message loop to call function: Invalid thread ID. - when starting up the windows/386 build; race in ui()/msgloop()? - - happens the first time I run a new build in wine; also if my computer is running too slowly when running in wine - GTK+: stderr is flooded with ``` (test:17575): Gdk-CRITICAL **: gdk_device_ungrab: assertion 'GDK_IS_DEVICE (device)' failed |