Tag Info

New answers tagged

1

i have a solution that uses the UndocumentedTestFEParserPacket as described by John Fultz! in this question. This funny named Tool parses a String Input into the real unchanged Mathematica BoxForm. This is my code: str0 = Sum::usage str1=StringJoin[ToString[StringReplace[#, "\\\"" -> "\""]]& /@ (Riffle[MathLink`CallFrontEnd[ ...


24

Yes, it is possible: The idea is to look at the underlying cell expressions in the documentation for those string property tables. As I said already in my comment above, basically we have two different situations here: the trend since Mathematica V6 that many options are not symbols any more but rather strings. function arguments, that are given ...


1

Here's something to get you started. It opens the documentation notebook and looks for a table row containing the appropriate string. I haven't tested it thoroughly so there are sure to be problems: findInDocs[s_Symbol, p_String] := fID[ToString[s], "\"" <> p <> "\""] findInDocs[s_Symbol, p_Symbol] := fID[ToString[s], ButtonBox[ToString@p, __]] ...


1

After contacting WRI support, I received the following response: The local documentation updates with Wolfram Mathematica. The most updated documentation would be the version on http://reference.wolfram.com/language/. The documentation update option may be irrelevant and has already been reported. So, local documentation only updates when Mathematica ...


6

What really makes Dialog a model dialog is: WindowFrame -> "ModalDialog" (*or*) WindowFrame -> "MovableModalDialog" So be careful when changing WindowFrame with the expectation that your dialog will remain modal. Funny proof is that the following: CreateDialog[DefaultButton[], WindowFrame -> "ModalDialog", Modal -> False] is a modal ...



Top 50 recent answers are included