|
Why does the GUI block?
|
|
02-16-2017, 11:06 PM
Post: #1
|
|||
|
|||
|
Why does the GUI block?
I was hoping to use Wings as a demonstration that you can have a GUI app that does not block when it's busy doing something heavy in the background without using low-level OS threads directly, but my attempt to produce a demonstration case failed horribly. (That is, I wanted to prove the value of Erlang-style concurrency vs. traditional "GUI thread" style concurrency.)
Steps to reproduce:
This test was with Wings 3D 2.1.5 freshly-installed onto a late 2012 iMac running macOS 10.12.3, then repeated in a Windows 10 VM under VMware Fusion on the same hardware. I don't know if the fact that the bevel step takes many minutes is also a bug. I didn't expect to be able to bog it down so easily. (6,144 polys!) |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Why does the GUI block? - tangent - 02-16-2017 11:06 PM
RE: Why does the GUI block? - dgud - 02-17-2017, 07:07 AM
RE: Why does the GUI block? - tangent - 02-17-2017, 08:03 AM
RE: Why does the GUI block? - Asticles - 02-17-2017, 05:07 PM
|
User(s) browsing this thread: 1 Guest(s)



