--
v8: winex11: Map message pos to physical DPI in move_resize_window.
win32u: Avoid changing thread DPI context in process_hardware_message.
win32u: Factor hardware message point DPI mapping together.
win32u: Use map_window_points with explicit DPI over screen_to_client.
win32u: Split hardware message window lookup to a separate helper.
win32u: Use per-monitor DPI window_from_point in process_mouse_message.
win32u: Parameterize window_from_point dpi.
server: Pass window's per-monitor DPI in set_window_pos.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5819
On Thu Aug 29 07:47:26 2024 +0000, Rémi Bernon wrote:
> This is a huge amount of changes and it doesn't seem really justified? I
> think you can do everything you need with DEV_BROADCAST_HDR already and
> do not need any internal structs, or am I missing something?
I mean, DEV_BROADCAST_HANDLE has a dbch_nameoffset which you can use to put the device name in it, and use that for filtering?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6315#note_80369
Rémi Bernon (@rbernon) commented about include/wine/dbt.h:
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Lesser General Public License for more details.
> + *
> + * You should have received a copy of the GNU Lesser General Public
> + * License along with this library; if not, write to the Free Software
> + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
> + */
> +
> +#ifndef __WINE_WINE_DBT_H_
> +#define __WINE_WINE_DBT_H_
> +
> +#include <wine/plugplay.h>
> +#include <wine/debug.h>
> +
> +struct device_notification_details
This is a huge amount of changes and it doesn't seem really justified? I think you can do everything you need with DEV_BROADCAST_HDR already and do not need any internal structs, or am I missing something?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6315#note_80368