![]()
That un-stoppable noise that flashes in my face constantly as I try and concentrate on coding. please.. PLEASE.. let me turn it off.
![]()
That un-stoppable noise that flashes in my face constantly as I try and concentrate on coding. please.. PLEASE.. let me turn it off.
$ arduino-cli sketch new MyFirstSketch
just curious — which noise are you talking about ?
That text flashes constantly whenever I modify a file outside the IDE. It might also flash when I modify a file in the IDE but I never do that, I use an outside editor.
In either case I have to move the window slightly below the desktop to obscure it.
Like a 5-year-old jumping and waving his hands in front of me while I'm trying to work.
OK - never seen that..
That "5-year old" is telling you that the IDE language server is building its index of variables and functions used in the sketch so that it can provide name completion and the links to definitions.
Is it really that distracting ?
All 'blinking' does is tell me "something is happening". Something is always happening.
The fact that what is actually doing is trivia makes my point. No one cares.
More to the point: Yes. YES it is very distracting, it draws my attention to something with no information. I can't be the only one this bothers.
If you want the "did something" light on, fine. just please add a check-box in prefs to turn it off.
I don't want the service off, I want the blinking off.
But as you use an external editor why not position the IDE out of sight whilst editing code then you won't see the blinking
That is what I currently do, however I'm constantly going back to it and hitting the -> button to flash/compile.
It's a pain.
Blinking should be reserved for things that need attention and compel/suggest action, not for developers to tell you some cool thing did something. If it fails.. then I might want to know.
We obviously disagree about the utility, nothing worth arguing about. Doesn't bother you, fine. But it's top-level on the IDE and distracting, I'm asking that it be configurable.
Really? No one else finds this annoying?
If you look back I have said nothing about the utility of the flashing message but its presence dos not bother me. In fact, having had problems in the past where the language server appears not to run I am quite reassured when I see the message
If it did not flash and stayed steady during the index building process then if it stopped how would I know ?
Feel free to raise an issue on GitHub but don't hold your breath waiting for it to be implemented
I have no idea what you are talking about, and yes, some/many of us care about the language server because I use the 'show definition' function often and obviously name completion. It may be used more by professional programmers, but that is just my educated guess.
I believe you misunderstand.
"no one cares" -- that it's working. Blinking a message that says nothing specific is a needless distraction. I might very much care if it stopped working,
ie- there is no blinking light on your car dashboard that says "Wheel are still attached!"
I don't care about the feature one way or another, I care that every time my file auto-saves in the editor blinkblinkblink "look at me" breaks my concentration.
As several others have said, we either have no idea what you are talking about or it doesn't bother us. While typing this, I want to open the IDE and run a compile. I was careful to look all over the screen, but I see nothing 'blinking'. Unfortunately, I have Autosave OFF, as many do, but if I did turn it on, as it once was, I know because I just tried it: the ONLY visible thing is a black dot on the affected tab that goes off after the file auto-saves. NO blinking.
All that aside, when someone comes on the forum and starts complaining, and they admit to using a different editor, my first thought is, since you have that editor and a problem, the odds appear quite high to me that it is your editor choice, since I and a handful of others have already said 'what problem'
If it's repeating fast enough, it might be considered blinking. But the reason it appears is to show that the IDE feature you might actually be depending on, the code assistance like Go to Definition, is not yet ready.
It's common to say there should be an option/setting and -- not that you're saying this specifically -- that having choices is always better. That's just not universally true.
If the background work required was close enough to instant, then there would be no point. A better improvement would be to slightly defer the initial appearance of the message; then if it's actually done by then, there's no reason to show it at all. You'd need a bunch of timings in a wide variety of setups/situations to see whether that is worth it.
How about: position the IDE window slightly above and behind your working editor window, so that the IDE toolbar is visible, but the status bar with the message is covered. (The IDE window would probably be smaller than your editor, since you're not writing code there.) This might require an extra click, depending on your OS/desktop, but no window shuffling.
CLI doesn't blink.
it's not "my particular editor" it's any outside editor as far as I can tell. and it doesn't always do it that's part of the maddening bit. I start working and then without warning rebuilding sketch starts spinning and generally calling attention to itself.
"Indexing" also spins and moves. It should not be calling for my attention.
I keep saying "blinking" but that's a bit of an illusion, its because messages pop up and go away it feels like blinking. The motion/spinning is pulling my attention for no reason.
This is what I'm talking about. this visual noise is intolerable, as several have suggested I have to obscure this part of the window to get anything done. That's annoying I would like to have a "stop doing that" button.
Tell me I'm crazy for wanting that Jack Russel spinning text to cease.
-Curt
Where?
Right side, lower, that's the bottom of the IDE