On Fri Dec 6 16:34:37 2024 +0000, Gabriel Ivăncescu wrote:
> Well Typed Arrays will need something similar (they override all input
> indices, and override defineProperty), when I made the first dispex
> revamp with them, it wasn't clear how it would interact with the host
> object implementation. Well, it's clear now that we need a way to
> override them, I guess.
> And btw Typed Arrays really need that DISPID optimization as well (or my
> original hack, which didn't cover enums only) to skip DISPID for every element.
`lookup_prop()` allows overriding all indices. It could probably use "don't enum" mentioned recently.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6970#note_89979
On Fri Dec 6 10:42:56 2024 +0000, Jacek Caban wrote:
> Thanks. This intentionally doesn't touch `PROP_EXTERN`, as deleting
> those requires interaction with the host object. For all jscript knows,
> the host may choose to ignore the delete. Fixing accessor and function
> properties should cover everything prototypes currently need, so those
> should be in good shape for the code freeze.
> It could be useful to allow external properties to opt into this delete
> mechanism for cases where host-owned properties should always behave
> like regular ones. Examples include `constructor`, `prototype`, and
> possibly constants like `Node.TEXT_NODE`.
> For cases like document and window, we might introduce a flag in
> `property_info` to modify name lookup. Jscript could continue searching
> the prototype chain and use returned info only if the search fails.
> Storage properties seem more complicated. None of the solutions that
> come to mind feel ideal, but this is a very niche corner case. I doubt
> any reasonable code depends on it, so it seems safe to ignore for now.
> It also doesn't seem like something Proton needs to worry about.
Well Typed Arrays will need something similar (they override all input indices, and override defineProperty), when I made the first dispex revamp with them, it wasn't clear how it would interact with the host object implementation. Well, it's clear now that we need a way to override them, I guess.
And btw Typed Arrays really need that DISPID optimization as well (or my original hack, which didn't cover enums only) to skip DISPID for every element.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6970#note_89973
This MR adds support for getting a Bluetooth adapter's properties from its corresponding `org.bluez.Adapter1` object, and making them available to userspace via device properties and the `IOCTL_BTH_GET_LOCAL_INFO` ioctl, updating these properties whenever a `PropertiesChanged` signal is received for the adapter.
It also adds code for creating and removing radio PDOs on receiving `InterafacesAdded` and `InterfacesRemoved` signals from BlueZ, respectively.
--
v5: winebth.sys: Implement IOCTL_BTH_GET_LOCAL_INFO.
https://gitlab.winehq.org/wine/wine/-/merge_requests/6936
This MR adds support for getting a Bluetooth adapter's properties from its corresponding `org.bluez.Adapter1` object, and making them available to userspace via device properties and the `IOCTL_BTH_GET_LOCAL_INFO` ioctl, updating these properties whenever a `PropertiesChanged` signal is received for the adapter.
It also adds code for creating and removing radio PDOs on receiving `InterafacesAdded` and `InterfacesRemoved` signals from BlueZ, respectively.
--
v4: winebth.sys: Implement IOCTL_BTH_GET_LOCAL_INFO.
winebth.sys: Update radio PDO properties on receiving PropertiesChanged for an org.bluez.Adapter1 object.
winebth.sys: Remove the corresponding radio PDO on receiving InterfacesRemoved for a org.bluez.Adapter1 object.
winebth.sys: Create new radio PDOs on receiving InterfacesAdded for objects that implement org.bluez.Adapter1.
winebth.sys: Set radio PDO properties from the device's corresponding org.bluez.Adapter1 object properties.
https://gitlab.winehq.org/wine/wine/-/merge_requests/6936
This PR updates the behaviour of `NtQueryDirectoryFile`, bringing it in line with current Windows behaviour. The need for this update was discovered when attempting to build the Unreal Engine with MSVC under Wine. In certain cases conditional include statements do not behave as expected, due to MSVC depending on undocumented behaviour of `NtQueryDirectoryFile`.
We ran tests on multiple versions of Windows, and discovered that the behaviour has changed since the original Wine implementation, but the documentation has not. The source code for our test tool, and a set of results can be found [here](https://github.com/TensorWorks/NtQueryDirectoryFile-Test). As of Windows 8, calling `NtQueryDirectoryFile` with a re-used handle, a new mask, and setting the `RestartScan` flag to True, causes the cached results to be erased and a new scan to be performed with the updated mask. Currently, Wine performs as did earlier versions of Windows, where the changed mask is ignored, and the cache is reused. This can cause `NtQueryDirectoryFile` under Wine to falsely report that files exist, when they do not.
This PR corrects this behaviour, invalidating the cache when required. Implementing this exposed further undocumented behaviour of `NtQueryDirectoryFile`, where a search for a non-existent file will return either `STATUS_NO_MORE_FILES` or `STATUS_NO_SUCH_FILE`, depending on whether or not the handle had been previously used regardless of the value of `RestartScan`. This was reflected in a `winetest` which allowed for the response to be either `STATUS_SUCCESS` or `STATUS_NO_MORE_FILES`. This test has been updated to only allow current Windows behaviour, and `NtQueryDirectoryFile` will return either `STATUS_NO_MORE_FILES` or `STATUS_NO_SUCH_FILE` as appropriate.
This patch also adds unit tests for the new behaviour of `NtQueryDirectoryFile`. These tests pass when running `winetest` under Windows, and under Wine with these changes in place, but they will fail under older versions of Wine.
--
v5: ntdll: Add tests to confirm filemasks are tied to handles and not directories
https://gitlab.winehq.org/wine/wine/-/merge_requests/6904
This MR adds support for getting a Bluetooth adapter's properties from its corresponding `org.bluez.Adapter1` object, and making them available to userspace via device properties and the `IOCTL_BTH_GET_LOCAL_INFO` ioctl, updating these properties whenever a `PropertiesChanged` signal is received for the adapter.
It also adds code for creating and removing radio PDOs on receiving `InterafacesAdded` and `InterfacesRemoved` signals from BlueZ, respectively.
--
v3: winebth.sys: Implement IOCTL_BTH_GET_LOCAL_INFO.
winebth.sys: Update radio PDO properties on receiving PropertiesChanged for an org.bluez.Adapter1 object.
winebth.sys: Remove the corresponding radio PDO on receiving InterfacesRemoved for a org.bluez.Adapter1 object.
winebth.sys: Create new radio PDOs on receiving InterfacesAdded for objects that implement org.bluez.Adapter1.
winebth.sys: Set radio PDO properties from the device's corresponding org.bluez.Adapter1 object properties.
https://gitlab.winehq.org/wine/wine/-/merge_requests/6936