There is at least one editing option that we should consider removing.
Is there any legitimate use for this. It's just as distracting as an animated avatar.
Don
Ooo, thanks for pointing that out Don, I hadn't noticed the Marquee button before but will use it a lot now 
Rob
Can we make it go the other way?
Please remove the "marquee" editing option · Issue #104 · arduino/forum-assets · GitHub
I don't think it should be necessary to log onto Github, Facebook, Twitter, Google+, Flicker, or any other such external website to find out information about the Arduino forum.
Don
Graynomad:
Ooo, thanks for pointing that out Don, I hadn't noticed the Marquee button before but will use it a lot now
I already do.
Well, not a lot.
Just very occasionally when I think something is particularly noteworthy.
Note: I am not using it now. 
This should be fixed, please test it again.
Am I fixed?
This should be fixed, please test it again.
The phrase "This should be fixed" can be interpreted two ways:
- "This should be fixed" could mean that 'this' is is something that is indeed broken and we should fix it.
- "This should be fixed" can also be interpreted as 'this' is is something that was previously broken and we think we have fixed it.
The moving '<-M' still shows up in the 'Quick Reply' window so I guess it isn't fixed yet.
Don
Indeed, reopening the bug. Please remove the "marquee" editing option · Issue #104 · arduino/forum-assets · GitHub Was marked as fixed yesterday but the fix (looking at the code) was only disabling the effect of the button, not the effect of the code.
mastrolinux:
This should be fixed, please test it again.
Precisely what should be "fixed"? There is or was no "bug" as far as I could see.
One contributor whinges that he doesn't like something that (many) others do.
So what? No-one else has any problem with it. Oh. I see. One other does. Well, that makes two out of - how many?
What is actually going on here? Star chamber?
Admittedly the "code" box seems to have been almost fixed, but are there so few other concerns now that we can have this "storm in a teacup"?
This is no bug, and there's nothing to be fixed, as Paul__B already told about.
This marquee has been available before, and was seldom used (for obvious reasons i might add).
Let's solve the real problems first.
And keep away from over-regulating, please.
Please don't put words into my mouth. I didn't say it was a bug, I said that its use was distracting and I asked that it's removal be considered since it didn't seem to have any legitimate purpose.
Two of the resident comedians seem to have agreed with me with their demonstrations of distracting uses. Maybe I misunderstood and these were supposed to represent legitimate uses.
I certainly didn't expect this to be given high priority but I still think that the elimination of the distraction that this 'feature' can create outweighs any redeeming social value it may have.
Don
Maybe I misunderstood and these were supposed to represent legitimate uses.
Nope, the marquee is very annoying, but I have to say I can only remember seeing it used 2-3 times.
Rob
The marquee is as useful as the "message icon". See: What is the point of "message icon"? Just what is the point? - Website and Forum - Arduino Forum
Having something like that, which virtually no-one uses, and when they use it causes screams of annoyance, is just UI clutter. For example, I notice that the icons for bullet points are on the second line of icons. If we got rid of some of the less useful ones it might all fit in one line. I mean, who needs right justification? We aren't producing a school newspaper! Or middle justification? Or shadowed text? And why have Teletype and Pre tags? Code should go into code tags, and text is basically describing the problem.
For example, I notice that the icons for bullet points are on the second line of icons. If we got rid of some of the less useful ones it might all fit in one line. I mean, who needs right justification? We aren't producing a school newspaper! Or middle justification? Or shadowed text? And why have Teletype and Pre tags? Code should go into code tags, and text is basically describing the problem.
Nick, I have to respectfully disagree. I usually take the extra time to enhance a post, especially when some technical information is needed and you're trying to highlight some details. It can save misunderstandings, errors and also use the screen space more effectively.
- It's great to have the ability to scale a picture (width and height)
and also use the numerous HTML symbols/characters/entities that
can enhance readability. - Some useful web characters:
Ω ⏚∿ ϕ ∞ ⊡—►|—⊡ ⊡—╱╲╱╲╱╲—⊡
☛
The
[pre]
bbCode is especially useful for creating small mono-spaced sections of information.
[b]Initial State PinMode Function[/b]
Input High Z pinMode(pin, INPUT);
Input Pullup pinMode(pin, INPUT_PULLUP);
Output pinMode(pin, [color=red]OUTPUT[/color]);
EDIT:
I see it's recommended on GitHub to remove the text sizing and font control ... I also disagree with that. There is no extra load on the server to format a bit of text and although I'm quite new here, I haven't seen any abuse of these features in the forum.
You make some valid points, but this is getting bizarrely personal:
One contributor whinges that he doesn't like something that (many) others do.
Two of the resident comedians seem to have agreed with me ...
What is actually going on here? Star chamber?
Is there a problem with putting in minor requests? The implementation team can always put them to the bottom of the list.
Nah, It's not meant to be personal ... just voicing a different opinion.
But the point is, unless there is a consensus, they should not be on the list at all as they are not problems that require attention!
Wow! Something new. Was this on the list? If I quote you, only your text appears, not those you quoted!
I don't know if that is good, bad or what!
Is there a problem with putting in minor requests?
Considering that team is hardly getting around to major problems
I think people should hold out on the nit picks to try to keep the admins
focused on fixing the serious bugs.
p.s. Why are several bugs on github said they are going to be fixed yet there appears to be no signs
of progress on them