I got accustomed to then I write file name in Save dialog in Windows PC, it writes into file name label. In linux I must focus on label, and then write. It's annoying, but I can't find how to disable quick search. I see source, GTK documentation, asking questions to developers, but no help. There is this mice hidden? GTK2-3, no matter.
In the answers on this site I see recomendations for developers, not users. I want recompile GTK, or write the key in .gtkrc-2.0/3.0 to disable this functionality.
I found, that GTK developers is very hard of hearing, and don't like adding configurable options.
This "feature" is called typeahead and hardcoded in GTK libs, so no config or build options, just fixing code needed. It's a pity...
https://www.reddit.com/r/archlinux/comments/33x4wk/gnomegtk_316_file_chooser_typeahead/
But I find filename and strings to modify:
/gtk+-3.22.7/gtk/gtkfilechooserwidget.c b/gtk+-3.22.7/gtk/gtkfilechooserwidget.c
gtk_tree_view_set_search_column (GTK_TREE_VIEW (priv->browse_files_tree_view), -1);
/gtk+-3.22.7/gtk/ui/gtkfilechooserwidget.ui b/gtk+-3.22.7/gtk/ui/gtkfilechooserwidget.ui
0
Now need find source of GTK, because there is no option to disable this behavior...
Related
For the most part I very much like Qt Creator, but a few projects I'm working on require me to switch between my editor and my web browser for reference. Qt Creator is currently interpreting Alt+Tab to autocomplete, and then switching my window focus; this is a mild problem but it's really starting to get to me.
I've tried going to Tools→Options→Keyboard and searching for Alt+Tab, but found nothing. Is there a way to get it to selectively ignore the key combination without disabling autocomplete on the whole?
To complete the picture, I'm on Linux Mint 19.04 using XFCE desktop environment; or occasionally Maté. If I need to access something in system settings to do this I'm happy to; I just don't want to keep excessively second-guessing my code when I return to it.
Auto-complete is bound to Ctrl+Space by default, not Alt+Tab. In tools/options/keyboard, search for "CompleteThis" to see what it's bound to.
Maybe what you want is to disable auto-complete and use only manual-complete? That is, have the auto-complete list only show when you press ctrl+space, but never automatically. You can do that in options/text editor/completion.
So I'm contributing, for the sake of learning a bit more of the innards of ST3, to a repository making a new package for Laravel's Blade templating.
In the .sublime-syntax file, the scope is currently set as scope: text.blade, which works fine except for that fact that I cannot make the autocompletion popup appear for my snippets. For that, I need to change the scope to source.blade. But doing to kills the ability of using div.foo+ tab to expand it to <div class="foo"></div>.
I know I could change auto_complete_selectorin my preference to include text, but that's just a solution for me. We wouldn't want to have a package that asks you to change your preferences, we'd want it to just work.
Would there be a way, in my syntax file, to have the autocomplete popup activate while still in the textscope and keeping both features (popup for autocomplete and the tab to expand)?
I'm not sure which is the best solution. It maybe makes sense that the default setting for auto_complete_selector doesn't work in the text scope, but I don't understand why it's not working in text.html. Anyway, the way I see it, you have two options, each of them having their cons.
Don't mess with the user's setting, but communicate the need to adjust the auto_complete_selector, e.g. by using the Messaging system provided by Package Control. Con: users might ignore READMEs or install messages.
Override the user's setting by including a .sublime-settings that adds text.blade to the auto_complete_selector (I've seen packages doing just that!) Con: interferes with user settings.
On a side note, I'm wondering whether it wouldn't be more appropriate to use text.html.blade as a scope.
is there a function / class in wxwidgets that allows me to find out what keyboard layouts are installed and then change them?
I looked through the documentation and came across wxLanguage and wxKeyboardstate, but they don'T seem to be the answer.
No. This is done using the standard system-global methods and wxWidgets doesn't provide access to it. FWIW wxLanguage is only used to select the locale to use and you can also retrieve the default user language, but not the keyboard layout.
So when I create a new Qt project inside Qt Creator I'm only asked for some simple details like location of the project, build targets, the main window class name (along with header, source and form file) and at the enda choice to add it to version control.
After I create the project I'm only given the qt core and gui modules. My question is how do I add other modules (such as network or opengl). I've looked and looked, yet I cannot find anything on how to add other Qt modules easily. I know I can edit the .pro file, but unfortunately I don't know all the modules in Qt, nevermind the name I'm supposed to put there. Adding external libraries is easy, but how come there's no (obvious) option to add Qt libraries?
Help would be much appreciated ^_^ Thanks!
Oh yeah... I'm running Arch Linux if that's any help.
Edit your .pro file. It should has one line like this:
QT += core gui
Append the desired modules in this line. To get the module's names, just remove the "Qt" part in this list. (e.g. QtSql turns "sql")
I can't find that either.
It seems that in older versions of the "New project" wizard you used to be able to specify which modules you wanted to use, but even then you were not able to alter your choice later. And this seems gone now, so your only choice is to manually edit the .pro file.
As others have pointed out, you simply #include the module you want in the source and add the name of the module in the .pro file to the QT variable.
However the actual documentation you need which no one else has mentioned is the qmake Project Files page. qmake is very powerful and it's well worth getting familiar with how it works and I think that's why they don't provide a complete GUI for it, as it can handle some very complex scenarios.
You have to read the documentation to add the modules.
Frankly speaking, I never really felt like that there needs to be a GUI for that.
This seems a known problem but I have not found a good workaround. I like the style of the
non-native QFileDialog, especially the feature that allows the user to input the path directly
which is very convenient since the user can easily copy/paste the folder/file name from other applications. However, it seems very slow when the dialog is first launched. The native option
is quite responsive but the problem is that it does not provide an input field so for the user to select a folder he/she has to walk into the directory, which can take many mouse clicks and is not fun. I am not sure if you have experienced similar problem or if I miss something.
BTW, my PyQt version is 4.4.3 and I am working on Windows XP.
Thanks,
Bing