rustbasic

Yes, you try to find a temporary solution. I did this and it worked fine on Windows 10 with two different DPI monitors. ``` fn main() -> eframe::Result { let...

I tested it with the test example below and there was no problem with the fullscreen function. ``` fn main() -> eframe::Result { let native_options = eframe::NativeOptions { viewport: egui::ViewportBuilder::default()...

As below, we have confirmed that there are no problems with the FullScreen function or other functions in Windows 10. ``` use display_info::DisplayInfo; fn main() -> eframe::Result { let displays...

> As I said in #4770 and #4658: > > We need a proper test for this, otherwise we will just go around in circles. `ScrollArea` is getting way to...

completed.

Note : Seems to work fine on Windows10 + Chrome + (Monitor 1.25 & 2.0) ( Could it be depends on the OS? )

Please see below. ``` let outer_rect = ui .ctx() .input(|i| i.viewport().outer_rect.unwrap_or(egui::Rect::ZERO)); let inner_rect = ui .ctx() .input(|i| i.viewport().inner_rect.unwrap_or(egui::Rect::ZERO)); ```

This is about turning off a specific event in TextEdit. Users can turn off unwanted events or handle the events that are turned off directly.

If you have two monitors and the viewport is on a different screen than your program: The frame rate is 30. Sometimes in this case the frame rate can be...

> * Is this a duplicate of [Speed ​​issues on Windows when `immediate viewport` is on another screen #5249](https://github.com/emilk/egui/issues/5249) ? It's a duplicate, except for the symptom of `FPS 50`...