I am using awesome window manager (new to it). The normal keybinding for changing size for the window in tiling mode is Super+h & Super+L but it only resizes the terminal window (I am using alacrity & it is resizing that), but if I try to resize another window instance firefox, it is not resizing that. Any solution will be appreciated
I'd recommend https://github.com/lcpz/awesome-copycats for newcomers. Also this is a related question: What is incwfact and setwfact of awesome.client
Basically what you need is hidden in this documentation page:
https://awesomewm.org/doc/api/classes/tag.html
incmwfact: Increase master width factor
And here: https://awesomewm.org/doc/api/classes/client.html
incwfact: Change window factor of a client.
Example from my config:
K.win is the Mod4 Key which is the windows key on my keyboard.
I'm "expanding" the current window (client) to the location indicated by the arrow key. Actually I'd need some extra code for up/down to work correctly in all cases but I rarely have vertically stacked windows.
awful.key(
{K.win},
"Right",
function()
awful.tag.incmwfact(0.05)
end,
),
awful.key(
{K.win},
"Left",
function()
awful.tag.incmwfact(-0.05)
end,
),
awful.key(
{K.win},
"Down",
function()
awful.client.incwfact(-0.05)
end,
),
awful.key(
{K.win},
"Up",
function()
awful.client.incwfact(0.05)
end,
),
Related
my app user base is of an older age group and I'm having some issues when they have increased the screen size via accessibility options.
I'm going to guess Apple doesn't allow you to override this in your app? I'd rather them squint than think the app is useless because a 1/4 of the UI is off screen!
Failing that is there a way to detect it and at least pop a dialog to warn them?
Using Flutter.
You can override default system scaling if you absolutely have to via:
return MaterialApp(
builder: (context, child) => MediaQuery(
// or whatever `textScaleFactor` you want
data: MediaQuery.of(context).copyWith(textScaleFactor: 1.0)
child: child ?? SizedBox.shrink(),
),
// ... the rest of your MaterialApp setup
);
... but you shouldn't, ESPECIALLY given your target audience are visually impaired and you should instead be fixing your app and accommodating responsive UI to handle such use cases.
This is an "Accessibility" (a11y) topic.
Indeed, you can't override screen zoom settings in Apple devices. You can override some settings for Android though (through MediaQuery you should be able to set textScaleFactor).
But this makes sense: we can't just ignore the needs of visually impaired users. We should build apps and UIs that react to such settings without overflowing, even though the Layout worsen a bit.
When it comes to a11y, you don't necessarily need to re-think the whole layout as responsive (Layout Builders, etc.), but you should make your text containers flexible. For example, say you have:
Row(
children: [
Text("Hello a11y!"),
],
),
then, you should consider wrapping your Text in a Flexible container to avoid Overflow (so that your text can go down to a new line).
Vaadin 14.2.0.alpha7 added new functionality to Dialog component (https://vaadin.com/api/platform/14.2.0.alpha7/com/vaadin/flow/component/dialog/Dialog.html), especially the resizing availability. Unfortunately I was unable to find a way to have dialog being created with width I need neither to set the width programmatically after the dialog is opened.
Here are few lines of code I use for described purposes (unsuccessfully):
dialog.isResizable = true
dialog.width = "900px"
dialog.addOpenedChangeListener { event ->
println("!!!opened-changed event fired")
dialog.width = "900px"
println("!!!dialog width = ${dialog.width}")
}
dialog.addResizeListener { event ->
println("!!! on resize event width = ${dialog.width}")
}
When I open the dialog it appears with its limited width (around 500px), the OpenedChanged event being fired and prints that dialog has 900px width (while its not!), when I resize it manually the Resize event being fired and prints that dialog has around 600px width (after I increased it a bit manually using mouse).
I know that early versions of Dialog had limited width (around 500px) in templates and there is workaround with importing styles to adjust dialog width. I was hoping with new version to increase dialog width without touching templates and client-side.
Is there any way to set dialog width and adjust on being opened programmatically without touching client-side templates?
P.S. The 14.2.0 version announced to be published on April so I believe the question is suitable even for now its prerelease version.
This happens due to the max-width setting of ~560px to comply with the materials design. There is a ticket about it here: Dialog Size - Material Theme. (In the default Lumo theme this works out of the box. You can verify it by commenting out #Theme(value = Material::class, variant = Material.LIGHT) in MainLayout.kt)
Unfortunately, as style targets the overlay part, the only one way to overcome this is using style files. On the other hand, it should be pretty straightforward in the current version :)
I created a pull request to your repo with the changes needed. Feel free to use it, if you want Make width acccept values more than 500px :)
how can i change the theme or default background color for ios.. it's conflicting with my background image. I'd like to set it to transparent.. Thanks
First let's understand how scenes in react-native-router-flux works. When you define them in your navigator, like below,
<Scene sceneStyle={{marginTop: 64}} title="Home" key="home" component={Home} />
You simply say that, my content should render below the pre defined navbar. Which can be 54 or 64 depending on your OS. So when you use Router,
<Router navigationBarStyle={{backgroundColor: 'transparent'}}>
and add navigationBarStyle to every Scene you have by introducing that line, you almost forgot what you've done above, setting your Scene to align itself some margin below the navigationBar. Therefore you see nothing (white space) in your simulator.
In order to have what you need, do this where you want your image to appear full screen with navigation controls:
Actions.refresh({
key: 'home',
navigationBarStyle: {backgroundColor: 'transparent'},
sceneStyle: {marginTop: 0},
});
Or you can introduce this settings in your Scene component where you define it.
I tested this solution and it works on iOS, can't tell the same for Android, so please back up your code before making changes. You can further customize it to remove borderBottom line.
Is it possible to make my devTools dock to bottom by default?
I am completely new at electron, and this project took me 8 minutes to set up so excuse my design.
what i want
contents.openDevTools([options])
options Object (optional)
mode String - Opens the devtools with specified dock state, can be right, bottom, undocked, detach. Defaults to last used dock state. In undocked mode it's possible to dock back. In detach mode it's not.
So in your code in the Main process, it should be something like this
mainWindow.webContents.openDevTools({ mode: 'bottom' })
webContents API
This can be eaisly done as follows
window.webContents.openDevTools({ mode: "bottom"});
or as follows
mainWindow.webContents.openDevTools({ mode: 'detach' });
use { mode: 'undocked' } , then you can see the different options to put you devtool when it's launched, but maybe you can't use some mode, like bottom or right. good luck!
Ok, So I'm a bit lost on this. jQuery UI documentation states that on resizable i can have visible handles which as i understand are visible icons/pictures (do I understand this correctly?)
If specified as a string, should be a comma-split list of any of the following: 'n, e, s, w, >ne, se, sw, nw, all'. The necessary handles will be auto-generated by the plugin.
So I should have handles all over my object if I specify 'all' ? If so, it does not seem to work--I only have something visible on 'se' corner.
Now looking at jQuery UI resizable source code, it seems that this is the only way it is supossed to work :
if ('se' == handle) {
axis.addClass('ui-icon ui-icon-gripsmall-diagonal-se');
};
Am I missing something? Can I create them on my own?
That code is telling the widget to only bother setting up a nice icon for the SE handle, if they're automatically generated. It's still actually creating the handles as a small, invisible box in each corner which can be dragged, just without any icon (the jQuery UI iconset actually doesn't have any other similar handles).
Refer to the API doc for how to attach them to your own DOM objects, which you can easily customise the appearance of. Quick example:
$('#targetToMakeResizable').resizable({handles : { ne : ".jquerySelectorForNEHandle", sw: ".jquerySelectorForSWHandle" }, aspectRatio : true});
Alternatively, you can just override the base css for .ui-resizable-handle.ui-resizable-{direction} with your own settings.
Here's a jsfiddle to demonstrate both methods. Note that rotating the icon in the way I've done it is probably not going to work in every browser.