Mercurial > dwindows
view win/dw.dll.x86.manifest @ 2801:b004cc75d574
Android: Remove the _DW_EVENT_THREADING experiment.
While it was more simple to launch a new thread to handle each event, this
approach had numerous drawbacks. No reasonable way to limit the number of
threads or memory consumed. Order of operations problems, the thread
scheduler would control the order in which the events were handled, not the
order of events produced by the UI.
The non-threaded version has been working and stable for a while now even
though it is more complicated for us to maintain our own event queue... this
allows us to make sure the events are handled in order and we can limit the
number of events in tight system resource situations.
author | bsmith@81767d24-ef19-dc11-ae90-00e081727c95 |
---|---|
date | Sun, 17 Jul 2022 21:03:31 +0000 |
parents | 000a94a1ddc1 |
children |
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="2.0.0.0" processorArchitecture="X86" name="dw" type="win32" /> <description>Dynamic Windows</description> <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!-- Windows 10 --> <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> <!-- Windows 8.1 --> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> <!-- Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> <!-- Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> <!-- Windows 8 --> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/> </application> </compatibility> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> </dependency> </assembly>