I just installed spyder 4.0.1 and am overwhelmed by all the bells and whistles. Which settings should I change/uncheck in order to get back to spyder 3 default behaviour?
Two most pressing problems are with the auto-complete (using TAB) in the editor:
The first item is black on dark blue and therefore illegible. Can I adjust that?
There are way too many irrelevant suggestions. Can I adjust that?
(Python/anaconda/win7 in case it makes a difference.)
(Spyder maintainer here) My answers:
The first item is black on dark blue and therefore illegible. Can I adjust that?
No, but that dark blue color comes from the Windows classic theme, which is really ugly. In the normal Windows 10 theme things look as expected:
There are way too many irrelevant suggestions. Can I adjust that?
Yes. Please see my answer about that: https://stackoverflow.com/a/59724907/438386
Related
The editor for the GUI is a complete mess. When I create a brand new script, the spacing and font are relatively ok.
However, if I open any existing function, it is shown with way too much space between lines, and spaces and tabs show way more space than they should. An example is shown below:
I tried selecting the Edit - Preferences - General - Use custom file editor options, and chose "notepad++ -n%l %f. I have notepad++ installed already on my computer.
When I selected this option and clicked ok, the Octave GUI crashed. When I tried to reopen a file now, I get the error "could not start custom file editor".
If I change the font, it temporarily fixes the issue. But none of the changes persist. Often clicking OK crashes octave. And any time it's reopened, the fonts revert to default, and the spacing problems returns.
How can I make the editor show an appropriate leading and space width?
I would also like to be able to further customize, if possible. For example I'd like it to use a dark theme. But for now just showing a reasonable space between lines would make this at least useable.
I'm using Windows 10, Octave version 6.4.0
does anybody knows how to disable the green highlight in Spyder editor as I show in the picture below?
Thanks
Spyder has many settings which the user can change.
In Preferences>Tools>Appearance>Edit Selected Scheme we can select the colors of several highlights, including current cell. (followed by OK then Apply, which can take a few seconds, then OK).
Setting this to #19232d (which seems to be the color of the overall dark theme background) at least gives the appearance of highlighting having been stopped.
There seems to be no way of setting such a color to transparent (in the CSS sense).
Under Tools>Preferences>Editor it seems as though we can unset highlighting of the current cell, but this appears to get overwritten by the Highlight Occurrences after selection, and setting that to something huge in the hopes it would not kick in did not seem to work.
However, I do not claim to be a Spyder expert and would welcome feedback from those who are and who perhaps know of ways of stopping highlighting in certain areas completely.
(Spyder maintainer here) This is caused by a bug in our code. It'll be fixed in our 4.2.0 version, to be released in November 2020.
In the meantime, the solution is to reactivate the option Highlight current line, present in the menu Tools > Preferences > Editor > Display.
I am a beginner in vscode.
When I write code the tooltip annoys me, because I use divided screen in macOS
so I want to make the tooltips semi-transparent without press ctrl
like this image:
Try this colorCustomization in your settings:
"workbench.colorCustomizations": {
"editorSuggestWidget.background": "#ff000060"
}
The last two digits, in this case 60 are opacity. There a few more editorSuggestWidget options to change too.
https://wannabedev.tistory.com/37
I found it, here is a screenshot:
Unfortunately, that's a visual studio feature not yet available in visual studio code.
At present, the only option is to disable the pop-up altogether, in which case you don't get the hinting, which is not ideal.
There are a lot of threads on GitHub about the position and opacity of the tool tip (search terms like 'tooltip intellisense position' you'll find a bunch). You can add your voice there.
There seems to be no corresponding element in the graphical language provided by makecode (its possible using lab.open-roberta.org editor). I didn't find anything in the Javascript section either.
Does somebody know a workaround (like accessing the RGB LED on a lower level)?
Click on the first tab "Basic" and then choose "set led to $color".
Obviously irritating that that code block is not subsumed beneath the "LED" tab.
Just installed sIFR into the site I am building (a personal portfolio site). When using it on pages with slimbox popups, sIFR overlaps the slimbox and makes it dificult to see the image. I tried applying a high z-index to the items I didn't want overlapped, but that didn't solve anything. Here is a screenshot of what it looks like (since my site is not online yet):
http://users.sephiroth.ws/DemonicGoblin/sifr.png
Is there a way to hide the sIFR when a slimbox link is clicked, or a way to adjust the z-index for a way to it not to be always on top? This happens on the latest version of all major browsers (I couldn't test Safari or Chrome though, even though I doubt it will differ)
I ahvent been able to find any information regarding this subject, so if it has been fixed in the sIFR beta it would be nice to know. Thanks.
In sIFR 2 you need to set the sWmode parameter to "opaque". This should allow HTML elements to be displayed on top of the Flash movie.
In sIFR 3, the parameter is wmode, though you can also use opaque: true.
Thank you so much - just saved my day.
I saw that lightbox break - so did I nearly:)!!!
But what a straight forward answer and solution thanks!! again
The file in mention is:
sifr.js
and put a code like:
sIFR.replaceElement(named({sSelector:"h1", sFlashSrc: "http://localhost/ddddddd/templates/template/i_font_swf/carbon_std_swf.swf", sCase: "upper", sColor: "#86ca29", sWmode:"opaque", sBgColor:"#fff"}));
I just write it cause took me some time to remember where this setting initially was - when I did the sIFR long ago.