Mazranel
Mazranel
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
I'm not very fond of XAML app development
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
I knopw there are Avalonia, Uno, Maui, WPF, etc but those all use XAML as far as I'm aware
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
What GUI frameworks can I use with it?
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
Does .NET run on BSD OSes?
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
I'm thinking of moving away from Mono for this reason, I just don't know if any other decent frameworks
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
BSD support would be a huge maybe, but I'd still like to have that option available
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
And that might not even work across multiple operating systems
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
That makes things a lot more annoying for me. Say a certain distro doesn't have X11, I don't want to have to maintain an X11 and Wayland version
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
That won't be super cross-platform though will it?
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
I Haven't learned the WPF / XAML side of things yet, as I personally dislike it
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
Do you have any recommendations?
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
seems Mono is a bit buggy
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
it is no longer working
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
except that the terminal issue now always returns the secondary monitor
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
Seems that using PointToClient makes everything work as intended
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
This happens on the primary monitor as well. The size is 2560x1440 and it will return something like (3078, 600)'
26 replies
CC#
Created by Mazranel on 6/16/2024 in #help
Using Screen.FromPoint(Cursor.Position) always returns `Display 0`
Cursor.Position also returns incorrect values. For example, the secondary monitor is 1920x1080 and it will return something like (1920, 1230)
26 replies
CC#
Created by Mazranel on 6/5/2024 in #help
Memory leaks with OpenFileDIalog, SaveFIleDialog, and DataGridView in WinForms
Yes
28 replies
CC#
Created by Mazranel on 6/5/2024 in #help
Memory leaks with OpenFileDIalog, SaveFIleDialog, and DataGridView in WinForms
ah, right
28 replies
CC#
Created by Mazranel on 6/5/2024 in #help
Memory leaks with OpenFileDIalog, SaveFIleDialog, and DataGridView in WinForms
Also, why wouldn't the runtime give the memory back to the OS if it's done using it?
28 replies