I just starting using flutter web since it's stable release. One thing I observed about this is the UI is not zoomed in like other web app.
Below is the default starter app which appears on creating a new flutter project. I've just changed the body color of Scaffold to notice the issue properly.
It's good the it's zoom is not responsive to scroll wheel of a mouse but when I use the touchpad of my laptop to zoom in, it responds to it. The result of zoom is a bit unexpected.
Below is the result.
In this case I kept my cursor to the center of screen and zoomed it. Keeping the cursor anywhere leads to almost same kind of UI.
Any workaround for it? Or maybe if I can disable this pinch zoom feature ?
Related
I'm trying to learn the tauri gui toolkit with rust but ran into an issue with 2 finger scrolling on my laptop touchpad on the displayed page (in dev mode at least, havn't tried the release mode yet). The frontend is written in vuejs using the vue router.
If I use a two finger horizontal scroll on my touch pad, that causes the usual "back animation" that we can see in chrome, and it also changes the view to the last open router page (killing any running functions and processes on the front end)
Image of the issue, the white part is not a part of the frontend
I tried googling and going through the docs but found no information about this.
I'm a new user for hololens2. Recently, I am using hologrphic remoting player app because it can support my application tests.
What I expected to show on hololens when I set up this app with unity to use is my scene. However, it show me just black screen with 'receiving...' text.
I even wait for about 5 minutes after this text showed up, but this situation never changed. Plus, in unity, the game tab should show my scene, but it shows black screen too whenever I click the 'start' button to use the app.
How can I fix it?
I'm working on adding universal links to my iOS app and I'm figuring things out but I'm a little lost on what to do when the app is not fully close, just running in the background.
when I debug through the app, it goes to WillContinueUserActivity then it goes to ContinueUserActivity which is fine and expected but I noticed in doing this that the previous screen the user was on is still visible during all of this, is that expected?
I'd prefer to have it seamlessly go to the desired screen and not have some jarring transition.
I think it is expected and by design. You can't make those previous screens invisible programmatically.
Universal links will make the app open the desired page as soon as possible.
I am working on electron app where i open a child window which i want to be above all the windows (not above fullscreen windows though), I managed to do it by using
win.setAlwaysOnTop(true, "screen-saver");
It now stays on top of all other open apps and keynote app presentation mode, i want user to be able to click buttons inside my window but now the issue is as soon as user clicks on button or just window in my child window, keynote window minimizes (as focus shifts to my window).
What i tried : I tried almost all available window option given in electron docs with different variations, I also tried playing with modals, but obviously modals stay in window itself, i want to keep main app minimized and keep child window on top of other apps. I also found electron-modal package, but that also behaves same.
working example
I was trying different application to check is any other application is able to do it, and i found that zoom app window (in screen share mode) is able to stay on top of keynote app and you can click buttons inside that app, you can move window, and keynote app keeps running in the background with no issues. I am trying to achieve exactly same behaviour.
This is something that you won't be able to recreate with electron currently, except through a native node module that manipulates your window related OS flags.
You can follow this issue on the Electron repository, since the flags introduced there should resolve your issue, or at least give you a point of entry to make your own PR or node_module.
https://github.com/electron/electron/issues/10078
After i had successfully ported the app. the app is running fine and taking touches on native ios nibs files where used for dialogs. But it is not taking touches on menu items.
let me explain this. It has some different view of axis. like tap on somewhere on screen will open some other menu which was not tapped. it seems it is taking touches but opening the desired menus but the location of buttons are not proper..
I had similar. In my case I had implementation of touchesBegan,touchesMoved and touchesEnd in View class with calling super. On iOS it works fine and messages going directly to controller. With apportable SDK it does not work. Maybe you have the same situation.