text formating - notation to make text portion grey or 'disabled'
I'd like to make some text within table cells grey (i.e. disabled) in the same way that I can make portions of text bold, italics, etc.
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
-
Inappropriate?Could this be done with the use of text wrappers similarly to how *bold* _italics_ and [links] work? How about {disabled text}? Don't know if the curly brackets are an option....
Use Case: I use the table tool to simulate a property inspector object. There are times when I need a property to be displayed to the user for informational purposes, but disabled.
I’m trying to be helpful
-
Inappropriate?I see that this week the List object received this feature. Could the same notation be used for tables as well?
-
Inappropriate?Hm, this is a problem. In menus, one uses "-disabled-" to disable entries. Perhaps this should be harmonized within all text controls and "-" is not an option I guess.
-
I wonder if --this-- could work? -
Inappropriate?I don't know... we have [ ] and { } and & & and -- --
Perhaps one should change to something more basic:
{disabled:blah blah blah} {linked:blah->here.bmml} {underline:text}
How many other "styles" will follow? Will this be understood by the user?
I tend to say -disabled text- is ok, according the scope:
-this will render a paragraph
as disabled text-
-this is a disabled menu-
-or a disabled accordion-
File, Edit, Options, -Setup-, Tools, Windows (disabled menu)
But I would not support a -disabled- text within a paragraph, as where in a mockup will this be needed??
I’m confident
-
Inappropriate?--this-- works for me, just thought that -this- would be more consistent with the menu object.
-
My fear with using -this- is that it might accidentally disable some text that people didn't intend to have disabled...still, what are the chances? Thoughts? Should we go for it? Of course one would just have to change it to \-this\- to make Mockups ignore the markup and show it as -this- again. -
Inappropriate?Ok guys I went for it, -this- will be disabled EVERYWHERE throughout the app. Give it a shot! http://www.balsamiq.com/products/mock...
I fear this might break some little corner of the app somehow, so let me know if it does and we'll pull it out (since it was a 3-lines-of-code change).
I’m feeling brave!
-
Inappropriate?O, I'm sure it will "just work". :)
However..... If it does break some little corner somewhere, I am also alright with --this--, I was just commenting that it might be frustrating if it was -this- in some controls and --this-- in others.
I’m confident
-
Inappropriate?good point since "- text -" actually matches a litterary form - at least in French - ahah.
so using -- sounds like a good idea to me :) -
We only match dashes (and *s and [s and _s) if they are attached to text, so -this- becomes disabled, but - this - stays as it is. Try it out! http://www.balsamiq.com/products/mock... -
Giacomo, if either '-' character is adjacent to text on at least one side, it'll activate the 'disabled text' feature. For example, the following all end up with gray text: "Text - more text (1-5)", "Text - more text (1- 5)", "Text - more text (1 -5)". -
This reply was removed on 12/10/09.
see the change log -
Inappropriate?Jm,
Writing it like this should work if you need a workaround.
Text \- more text (1 -5)
I’m being helpful
-
Thank you - I didn't know escaping had been implemented.
Loading Profile...





