Reputation
8,266
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
30 54
Newest
 Informed
Impact
~33k people reached

Aug
14
comment Reference to multiple stylesheets
@Kuba, my last paragraph indicates that multiple stylesheets lets you mix in "new styles". What I mean by this is stylenames which have not been previously defined. Input/Output are defined in Core.nb, which is ultimately inherited by nearly every stylesheet in the system. Not many styles you've heard of get defined in Core.nb because we don't want to insert hard-coded stylenames into effectively every stylesheet. So, you won't find Section or Title or Code, for example. But Input and Output are so universal to the way the system works, it seemed better just to put them in Core.nb.
Jun
26
comment Reference to multiple stylesheets
That having been said, your statement that multiple stylesheets "don't work" is not strictly true. They don't work for your purposes. But they do work. You can use multiple StyleData[StyleDefinition->...] cells to mix in new styles. So if, in your example, "StyleSheet2.nb" has styles which don't exist in "StyleSheet1.nb", then they will be amalgamated together in your new stylesheet. So it does do something, just not what you were hoping for. Sorry for the multiple commenting, but I don't feel like I'm actually answering your question. Unless you'd accept "no" as an answer. :)
Jun
26
comment Reference to multiple stylesheets
...and these particular computations, although we cache them as much as possible, are one of the most expensive computations in the system. Not to mention the amount of effort to implement which, as has been pointed out in this thread, has a very low payoff because very few people would ever use this feature.
Jun
26
comment Reference to multiple stylesheets
If I have two versions of "Title" inherited from different stylesheets and they define FontColor differently, it is no longer acceptable for me to just take the first one. I must figure out where the information came from for each style. If both stylesheets inherit from Default.nb, but only the second stylesheet overrides Default.nb's version of FontColor, then I must choose the second. If only the first overrides, then I must choose the first. This necessity to not just track option settings, but the precise provenance of each and every option setting is expensive...(continued)
Jun
26
comment Reference to multiple stylesheets
The multiple inheritance problem is not to be dismissed. Styles can be "re-rooted" (effectively told to ignore inheritance) by using StyleData[name, StyleDefinitions->None]. So, let's assume you have multiple stylesheets which inherit from Core.nb. Each one of them defines a new "Input" style. Some re-root "Input" and others don't. What to do? Also, the multiple inheritance problem introduces serious performance issues...(continued)
Jun
9
comment Faded output is printed from dynamic object
@MarcoB, set the aforementioned option setting on $FrontEnd. I.e., CurrentValue[$FrontEnd, {PrivateCellOptions, "EvaluationUnmatchedStyle"}] = {}
Apr
13
comment Faded output is printed from dynamic object
@IstvánZachar since v6 grouping constructs can now be applied without setting CellGrouping->Manual. What the Cell->Cell Grouping->Group Together menu command does is to apply a style which causes automatic grouping to work in exactly the way you want. And then the Group Normally menu command just clears that style information. While this is not strictly as powerful as manual grouping, it is sufficiently flexible to handle pretty much every real-world concern. And because it's done via styles, it's much less fragile than manual grouping, which is the source of lots of bugs.
Apr
6
comment Faded output is printed from dynamic object
Why do you use CellGrouping->Manual? What are you trying to achieve that you can't achieve other ways? I've seriously considered deprecating manual cell grouping (since it's easy to manually group cells under automatic grouping), and I'd like to understand what you find interesting about it.
Dec
11
comment How to work with characters from CJK Unified Ideographs Extension B correctly?
@Silvia No, you should definitely not consider it full support. My earlier statement stands unchanged for v10.
Nov
14
comment How often does Mathematica contact its license server?
@sakra It varies based upon how many processes MathLM is licensing. For a typical smaller licensing situation, it'll be 3-5 minutes. The answer is a range because there's a 2 minute ping, and the precise time depends upon how long it is from the kernel crash until the next expected ping, which will be the first point that MathLM has any indication that something might have gone wrong. After the second missed ping, MathLM waits 60 more seconds, then times out the license. For licenses of more than 30 processes, that time stretches out because the ping times stretch out.
Oct
24
comment FlipView can't handle CurrentValue[“MouseOver”]. Kernel crash
Fixed for 10.0.2.
Jul
28
comment Implementing efficient multiple undo
@jtbandes Thanks for the complaint (really!)...that's a pretty decent suggestion. It's odd that I've never tried that before despite the fact that I commonly do it in text editors.
Jul
15
comment How to get the new font in Mathematica 10?
@Szabolcs No. If you give a non-existent font, we let the operating system determine which font to use. The choice is entirely up to the operating system. But once we have a font (whether it matched or not), then we query it to see if it declares itself as being serifed or monospace, and use the appropriate Mathematica font with it. So, the behavior you're seeing is, in part, operating-system-dependent behavior that is outside of our control.
Jul
15
comment Implementing efficient multiple undo
@jVincent Speaking as someone who had to think about every aspect of the system, I'm always seeing lots of bugs and limitations, many of which might be rarely noticed outside of Wolfram. In some cases, things that should be undoable but aren't. In some cases, undo falls over and does the wrong thing (I have significant internal consistency checks that tend to prevent undo from causing harm, but it will stop and wipe the undo stack in such a case). But my own priority/embarrassment list might not match those found by users. So, we'll see what the community judgment is. :)
Jul
10
comment How to get the new font in Mathematica 10?
@Szabolcs I would be dropping nukes if you couldn't tell the difference between l/1/I and 0/O in code. I do wish the web font we're using did a better job of distinguishing l and I (there's a little curve on the bottom of the l, but it's pretty subtle).
Jul
10
comment How to get the new font in Mathematica 10?
Upvote if this describes you: Wait...are you suggesting that you're going to take away my Courier font? You'll have to pry it from my lifeless limbs. It was an inspired choice when Wolfram did it in 1988, and it's no less inspired today.
Jul
10
comment How to get the new font in Mathematica 10?
Upvote if this describes you: Proportional for coding? Are you insane? Do the people who thought this stinker up actually ever write code? There are so many great coding fonts out there today...let's modernize on one of those!
Jul
10
comment How to get the new font in Mathematica 10?
Upvote if this describes you: Proportional is totally the future, and a brilliant break from stodgy tradition! I'm so tired of being kicked around by pseudo-modern coding environments that can't even figure out modern typesetting!
Jul
7
comment How to wait until a Listen mode link gets connected to?
I can absolutely certify that the answer is correct (although incomplete...there is no timeout that I'm aware of). I'll add a bit more technical detail to the Community thread, where you ask slightly different questions and make a misleading assertion. But the answer as I now see it here is correct without qualification.
Jul
6
comment Evaluating an If expression inside Dynamic
@MichaelE2 The first argument of InputField can only be a settable lhs if it's inside of a Dynamic (and, of course, that Dynamic has a sensible setting function). Otherwise, what the FE receives is literally the evaluated argument of the InputField which, in this case, would be InputField[1, Number, Enabled->Dynamic[fuc == "1"]]. The a is long gone.