I use Paraview (3.98) to display results from FEM simulations. The Properties detachable window accomodates some settings under Display (UnstructuredGridRepresentation), which creates GUI entries for "Opacity Table Values" and "Radius Table Values", which are very large and make the other settings go beyond the edge of the window. AFAIR it was not an issue in orevious version os Paraview. Is there a way to make the GUI less wide again?
I had a tough time overcoming this problem too, the solution for paraview 3.98 is to use the option --use-old-panels.
Or you could upgrade to PV 4.0.1 where this annoying bug has been fixed.
The problem occurs with 3.98 when the PointSprite plugin is loaded. You can not load the plugin if you're not using it and that will overcome the issue. As Zony suggested, you can always upgrade to 4.0.1 and this issue will disappear.
Related
Scope does not show enough information regarding cursor position in code.
How can I enlarge scope line in ABAP Debugger on the standard tab?
Probably a bug in your SAP GUI version. You should install the latest version.
See in SAP GUI 7.50 how the elements look better; the "scope" is left-aligned and has the biggest width possible, and all other information are right-aligned and their size is minimal:
I suppose this is resolution-dependent. On my 1920x1280 it goes fine out-of-the-box.
Did you try to drag the splitter between the editor and variable tab?
Usually it helps
Removing and clean installation of SAP GUI 7.50 solved the problem.
Backup connections before removing:
https://answers.sap.com/questions/409243/saving-connections-list-in-sap-logon.html
I downloaded Windows 64-bit with JDK 8 included of SQL Developer 18.1.
To run Oracle SQL Developed I just unzipped the file and run the sqldeveloper.exe contained in the folder.
Unfortunately, as you can see in the image the size of everything is extremely small and very difficult to see.
This issue appears exclusively with this software.
How can I resolve it?
I also faced a similar issue when installed this on Windows 10. The issue has to do with compatibility settings.
I have fixed it following the steps given below:
Get shortcut of sqldeveloper at your desktop
Ensure that you have admin rights in your PC
Right Click on sqldeveloper icon and select Properties.
Go to the Compatibility tab:
Compatibility mode change it to windows 7
Check the option of Override high DPI scaling beaviour
Select "System" in drop down below
Apply
Re-Launch the application
I guess this is a subjective statement - but that doesn't appear SMALL to me.
However, if you're using an OS accessibility feature to increase the size of text in your applications, the new 'Welcome Page' can interfere with that.
Uncheck 'show on startup' in the Welcome page
Restart SQL Developer.
You should be good.
The Welcome page uses JavaFX to render some HTML and this is apparently getting in the way due to a Java bug. We're looking to mitigate or fix this for a future release.
If that doesn't work, you can also try to actually increase the UI font size.
I talk about how to do that here
This is what it looks like bumped up to font size 14
Find your ide.properties file.
Windows: It's in your OS User's AppData, Roaming, SQL Developer, systemX.Y.Z..., o.sqldeveloper directory where X.Y.Z... represents your version of SQL Developer.
Linux/Mac: It's in your $HOME/.sqldeveloper, systemX.Y.Z, o.sqldeveloper directory.
You’ll notice this file is VERY well documented. There’s a section that speaks to Windows in particular. To change the default size for all look and feels, add this line, the uncommented one:
# To modify the font size for a particular locale under all
# look-and-feels, set the Ide.FontSize.<languageID> property. For
# example:
Ide.FontSize.en=14
2018 Update
On my 4k Mac Mini (2018 build if that matters):
Oracle 8 JDK
SQL Developer 18.3
Mac OS X look and feel
Ide.FontSize=21
This is how SQL Developer looks:
I changed font style and size from available settings from SQL developer.
We can change using Tools -> Preferences ->Code Editor -> Fonts
Fixed this for myself in Oracle Linux 8, but is also worth trying in RHEL and Fedora, if you use either of those.
If SQL Developer is running, close it.
With superuser privileges, open the following file for editing:
sudo nano /opt/sqldeveloper/sqldeveloper/bin/sqldeveloper.conf
Add the following two lines at the end:
AddVMOption -Dsun.java2d.uiScale=2
AddVMOption -Dsun.java2d.uiScale.enabled=true
Restart SQL Developer.
If the interface still looks too small, or too big, change the uiScale value (untested).
I had the same issue,
if you still could not fix the problem with the given solutions, for me also worked the following:
Go to the Display Settings;
Go to scaling and "reset it": change to another scale, for example, 100% and then to your preferred scale;
This should force the SQL-Developer Window to your preferred scale, unfortunately you have to repeat this procedure after every new SQL-Developer launch.
change the setting from "Compatibility tab" as highlighted in the above post was the only way to make the icon much more larger
In case anyone landed here looking for the same answer for a newer version of Oracle SQL Developer (like I did)…
As of v22.2.1, for macOS the preferences are now located in Oracle SQL Developer --> Settings…
You can adjust the font style and size under Code Editor --> Fonts
Hope that helps!
I'm
running IntelliJ 14
using Mac OS X layout
running on OS X (Yosemite)
IntelliJ is using DVORAK in general but not for keyboard shortcuts.
keyboard shortcuts are in QWERTY. As if they were scancode based instead of the key value after mapping.
Ideas?
edit 1
#gabriel hard to tell but here are some examples...
note: m, a and 0-9 are same on DVORAK and QWERTY
cmd+/ 'comment line' flashes code menu and sometimes moves to a brace (/ == {)
cmd+b works, goes to definition (b == n)
cmd+opt+l 'reformat' flashes code menu (l == p)
It turns out this is a problem in Java that has existed for some years, and is still present in Java 9. See the bug report here: https://bugs.openjdk.java.net/browse/JDK-8022079
JetBrains has been aware of the problem for some years, but is waiting for Oracle to fix it. See these JetBrains bug reports: https://youtrack.jetbrains.com/issue/IDEABKL-6493 and https://youtrack.jetbrains.com/issue/IDEA-63779
In those reports you'll find a work-around using a free tool called Karabiner. I have just verified that it works for IntelliJ. It will probably also work for other Java-based tools.
For OSX earlier than Sierra The work-around is:
Download and install Karabiner from https://pqrs.org/osx/karabiner/
In the OSX System Preferences, set your keyboard to the default "U.S. International" PC. If you don't often type diacritics and other international characters, it's easier to just set the keyboard to "U.S" instead.
In the Karabiner settings, type "dvorak" in the search box, then scroll down to the section For U.S. Input Source and check Use Dvorak Keyboard Layout (QWERTY to Dvorak)
From macOS Sierra onwards, as reported by user MithrilTuxedo in the comments, the procedure is different. You have to use Karabiner Elements (the new Karabiner core) with a configuration file. I have outlined the procedure at https://cpbotha.net/2016/12/16/dvorak-remapping-with-karabiner-elements-on-macos-sierra-works/ and summarise it here briefly:
Download and install Karabiner Elements.
Copy qwerty_to_dvorak.json from the examples and install it as the new karabiner.json configuration file.
If Karabiner Elements is running, it'll pick up the new file.
This bug will affect most Java-based tools such as those by JetBrains (IntelliJ, PyCharm, WebStorm, AppCode) and probably also Netbeans. The work-around summarised above should alleviate the problem in all cases.
I've had a similar problem using key combinations like ctrl+n in intellij 16 on linux (red hat). I use Colemak keyboard. I had two input sources setup in my operating system, system preferences .
English(US)
English(Colemak)
When I changed the order of the Input Sources, and put Colemak first, the problem seemed to go away.
System Tools > Settings > Keyboard > Input Sources
JetBrains are waiting for the bug to be fixed upstream in JDK, which of course will never happen. The other answer here is informative, but will only work on Mac OS, so if you're on linux or windows you're out of luck there.
I wrote a script to work around the issue, which you can find here. If you normally use GNOME keymap in pycharm on linux, then you're in luck - you can simply import my dvorak_settings.jar file and get back to coding.
Otherwise you can use the script to generate your own bugfixed keymap, read on...
The original keymap files are located in <pycharm>/lib/resources.jar/idea/Keymap_*.xml.
Example usage:
./to_dvorak Keymap_Emacs.xml -o Keymap_Emacs_Dvorak.xml
Have a browse over the generated file and if it looks sane, pack it up into the .jar file (see my dvorak_settings.jar example for the required structure) and import this in your IDE.
This problem is (finally!) fixed in IntelliJ IDEA 2017.1. See JetBrains issue JRE-172, “Wrong keys are picked up on dvorak layout in Mac OSX 10.6.2”.
It also seems to be fixed in other JetBrains tools. I tested that it's fixed in PyCharm 2017.1, CLion 2017.1, and AppCode 2017.1.
I have a coworker who needs to have multiple versions of LabVIEW on his computer. He has a bad habit of opening LV2010 code in LV2013. LabVIEW doesn't warn that you are about to change all of the code to a new version of LabVIEW, and this breaks the code running on a test system on the production floor.
Here is my question: does anyone know of any kind of hack or legitimate method of changing the windows title bar for a single application? I would like to be able to change the color of the title bar only on LabVIEW 2013 from blue to red or something.
If this isn't possible, does anyone have an idea of how to distinguish one application from another that looks almost identical?
Thanks for any advice you have to give.
Well, the good news is that LabVIEW 2014 on will have the version number in their icon. That doesn't help your situation much, though. I'm not sure about changing the title bar, but I think I can help with your second question.
The icons for those versions are indistinguishable, however, the mass compile LabVIEW does when you open a project from an older version is a dead giveaway. You know LabVIEW is performing a mass compile if, while the project is loading, "Compiling:" appears where "Loading:" normally does. Close out of LabVIEW without saving and open the right version of LabVIEW. If he still goofs, there's always reverting in whatever version control software you're (hopefully) using, and you can always save back to older versions in LabVIEW itself.
I currently have four (older) versions installed to support projects that are under warranty. One trick I've found to be helpful is to put a .txt document in the same directory I save my .lvproj with the LabVIEW version as the title. For example, if the code is written in LabVIEW 2012 I include a text document called LV2012.txt in my _Project folder. Not a foolproof plan, but it has definitely made me double check my open version of LabVIEW before double-clicking.
I would suggest to use get VI version property described here: http://digital.ni.com/public.nsf/allkb/0C72D335AA87DD6486256FC40069C17F
Than using version information change you title bar text or transparency(I am not sure about color) or other FP component using VI ref property node.
Is there any way to prevent start/load of DevExpress and/or Vissual assist?
Even if disabling it's up'n running the next time.
When using a limited cpu larger projects sometimes freezes everything for a bunch of minutes each time you forget to disable (and seems like I forget it each time).
Tried both out and one of them could be a nice contribute, if disabled by default.
I cannot tell you about VAssist, but automatic loading of CodeRush is controlled by the DevExpress--> Options-->Core-->Startup-->Load manually option.
I couldn't find the Startup option under Core; till I changed the Level to Expert from New User
To load it up again, you can go to Tools->Load DevExpress.
To bring up the options page, do Ctrl+Alt+Shift+O and change it to expert mode in bottom left pane.