My fullscreen wine app, game for example, minimizing when loosing focus. I switch tag in awesome-wm and when I am back, I should press hotkey to run awful.client.restore(). If this game has 'windowed' mode and it enabled, game not minimizing.
I suspect, this is because wine apps has minimized=true by unknown reason. Awesome cant minimize app, when it has focus. I cant determine class of application to make rule, xprop output is empty. But for notepad.exe I can see class of this wine app.
Not sure I want to make rules for each fullscreen app. Advice me, please, why it happened and what is inside wm?
Related
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've developed an app based on NodeJS with Electron for a web agency and try to extend it to the touch bar functionality of the MacBook Pro.
Developers launch the app once, which then automatically starts various processes in the background, such as compiling SASS files, optimizing images, etc.
Typically, these developers work with programs such as SublimeText or Atom. However, it often happens that the app expects user input during programming or inserts hints to optimize the code. I would like to display these things in the Touch Bar so that the user does not have to switch between the apps during programming. Unfortunately, the touch bar view of my app is hidden when switching to SublimeText or another app and replaced by the current app in the foreground.
Is there a way to display an app's specific touch bar while the app is running (even hidden) permanently without replacing it? I wonder if that is at least natively possible?
I couldn't find any information about this on the Electron documentary or somewhere else…
Thank you in advance!
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
Is there a way to disable Chormium's shortcut keys in Linux? I've tried the --app and --kiosk flags but they don't disable the shortcuts, you can still create a new (though unusable) tab with Ctrl+T and can create a new (fully functional) window with Ctrl+N. Also, Chromium appears to do it's own check for Alt+F4 because even though I have it disabled in the window manager it will close Chromium. How do I disable all the shortcuts within Chromium? Window manager is matchbox, started with xorg + nodm (the default lightdm+openbox system didn't allow me to auto-restart the session or get rid of Alt+Tab).
This is for an embedded system using node.js in the background to handle hardware io, but it will need a network connection to function so I want to ensure users are locked out of the browsers (the various Ctrl+Alt+F* shortcuts have already been removed, Chromium is all that remains in making it a real kiosk system). Alt+F4 isn't a major concern (though it would be really nice to get rid of) because when Chromium crashes nodm will automatically restart it and it handles the Alt+F4 somewhat reasonably (black screen, flashing white, then it's back up - it's not a security concern just a severely ugly "feature" people might stumble accross).
I don't think chromium has an inbuilt interface for disabling os keyboard shortcuts like ALT+F4, but what you could do is intercept those key-presses with javascript and that should be enough to stop the key-presses from working.
To enable such a script on all your pages, you'd need something like greasemonkey, which chromium has a support for out of the box, you can read about it here.
Custom Keyboard Shortcuts - Chromium extensions
I need to have a working web browser in a fullscreen Direct3D application. For example, Valve's Source-based games (sort of) do it in the MotD window when you join a server. Any tips on where to look?
Second Life uses ubrowser (http://ubrowser.com/) to embed a browser over a 3D world. As the source code is available for the Second Life client (http://wiki.secondlife.com/wiki/Get_source_and_compile) it would be a good place to see how they have done it.
Note however, they are using OpenGL, not Direct3D... but there is nothing specific in ubrowser itself to OpenGL.