Tag Info

Hot answers tagged

42

Prelude The items in this post are not generally regressions; they are simply changes and enhancements that may break code or cause problems in moving from one version to another. The bullet points are offered as specific solutions to instances of incompatibility, and not as recommendations of general practice. For example, Plot Themes are a powerful tool ...


28

I use this function getList[name_String] := Module[{options, idx}, options = Names[name <> "`*"]; options = ToExpression /@ options; options = {#, Options[#]} & /@ options; idx = Range[Length[options]]; options = {#[[1]], TableForm[#[[2]]]} & /@ options; options = Insert[options[[#]], #, 1] & /@ idx; options = ...


25

While trying to debug this issue myself, I stumbled across Todd Gayley's name in the source of one of the documentation .m files and contacted him directly. Todd was super great to work with---and at the end of an hour of screensharing he provided an easy workaround. The workaround essentially short-circuits one tiny feature of a normal documentation ...


25

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 ...


17

Possibly this way: << PrimalityProving` ?PrimalityProving`* or alternatively (see the copy&paste issue in the comments) ?"PrimalityProving`*" See also the help under ref/Information, subsection "Generalizations & Extensions". In some cases you have to provide a string argument: Information["*Values"]


16

The function you are looking for is Documentation`HelpLookup["some input"]. This is the function that is executed when you hit F1 (after the front end figures out what is under the cursor).


16

Even though documentation indices built with Mathematica 8 or older are not compatible with Mathematica 9, indices built with 9 are compatible with 8 or older. And even though Mathematica 9 can choke up converting documentation notebooks, it has no problems generating documentation indices. So the workaround to points 1 and 4 in the question above is to ...


15

/: is the short-hand notation for TagSetDelayed, which is creating UpValues. It's useful for over-loading how a particular function behaves with a specific head. For example: In[1]:= h /: Plus[x : h[arg1_, arg2_], y : h[arg3_, arg4_]] := Plus[arg1, arg2, arg3, arg4] In[2]:= h[1, 2] + h[3, 4] Out[2]= 10 The benefit being you don't have to ...


15

I will answer the technical part of the question - namely, how to get the entire graph. How one would go about analyzing and visualizing it, is another story. This will open and parse a given guide notebook, and get the links to other notebooks: ClearAll[getLinks]; getLinks[file_] := With[{nb = NotebookOpen[file]}, With[{result = ...


15

As of Mathematica 9, multiple autocomplete templates are supported and the different templates are delimited by newlines. So for your example, you'll need to define them as: myfunc::usage = "foo[x,y,z] will combine x, y and z for you. foo[x,y,z,w] will be even better.";


14

Using this webcrawler code from Wolfram site, and Guides page in online docs as the starting url: webcrawler[rooturl_, depth_] := Flatten[Rest[NestList[Union[Flatten[Thread[# -> Import[#, "Hyperlinks"]] & /@ Last /@ #]] &, {"" -> rooturl}, depth]]]; style = {VertexStyle -> White, VertexShapeFunction -> "Point", EdgeStyle -> ...


14

A Graphics object describes what amounts to a state-machine. Each object allowed in the primitive list has one of three actions associated with it add to state, display something while accounting for the current state, and save/restore state. Note, this can be modeled by a stack based system quite easily. According to the documentation, the first two ...


14

Although I haven't examined it to see how complete it is, putting Virtual Book into the search bar of the Documentation Center quickly found this: http://reference.wolfram.com/language/tutorial/VirtualBookOverview.html Which can be accessed locally with: tutorial/VirtualBookOverview


14

This is not a bug, the tick specification used in the documentation is incorrect. The tick specification in these examples is {bottom, left} which is the short form of {bottom, left, top, right} which was an older tick specification that was deprecated in v7 (according to the docs). But, it was allowed to continue to work until v10. The form you are ...


13

Another possibility: << PrimalityProving` Names["PrimalityProving`*"] {CertificateDiscriminant, CertificateK, CertificateM, CertificateNextPrime, CertificatePoint, CertificatePrime, fact, HilbertPolynomial, ModularInvariantj, PointEC, PointECQ, PrimeQCertificate, PrimeQCertificateCheck, ProvablePrimeQ}


13

The notebook DocumentationNavigator.nb has all the inter-dependencies built-in (they're arguments supplied to TreeBrowse`LoadVirtualCells and other undocumented functions that build up the documentation center. We can then parse the raw text contents of this notebook to pull out this list. I do that in the following, but I haven't restricted it solely to ...


13

This is from Wolfram technical support: De-select Help > Internet Connectivity > "Allow Mathematica to access the Internet" and then try using the Documentation Center. If this fixes the hang then have them allow internet connectivity again and test the Documentation Center again. Finally, setting my proxy settings to "Direct connection to ...


13

how to reproduce the default hashing behaviour when explicitly choosing a method Hash[1, "Expression"] (* 6568131406215528669 *) re-create the default hashing behaviour in different versions? Not possible as far as I know. The one-argument Hash implementation may change between versions. The algorithm has been most recently ...


12

This answer is intended to be progressively updated as I gain experience with this functionality myself. I assume you are using Wolfram Workbench and the documentation authoring tools it provides. As the documentation describes, you need to make sure that your package(s) are in a proper directory structure for a Mathematica application. You can do this by ...


12

Your g[1] and g[2] are simply acting as Head: g[1] := Plus; So there is no mystery in this syntax: {g[1][a, b], Plus[a, b]} {a + b, a + b} Head /@ {g[1][a, b], Plus[a, b]} {Plus, Plus} So you need to read: Head Everything Is an Expression But maybe there is a bit more to it than meets the eye. You actually almost wondered into ...


12

Do you mean a list of functions ending in Q? ?*Q


11

I've always considered the "suitable for symbolic manipuation" line to be a bit of truth wrapped in marketing speak and not meant to mean anything mathematically precise. The documentation center guides and tutorials are good examples of hyperbole in technical documentation (see for instance, the opening lines in Mathematical Typesetting). Coming to the ...


11

Update 2015, stylesheet approach: We can safely customize basic stylesheets by copying them first to $UserBaseDirectory: styleDir = FileNameJoin[{"SystemFiles", "FrontEnd", "StyleSheets", "Wolfram"}] If[! DirectoryQ@#, CreateDirectory@#] &@ FileNameJoin[{$UserBaseDirectory, styleDir}] CopyFile @@ ( FileNameJoin[{#, styleDir, "Reference.nb"}] & ...


11

One may also call up the old navigator palette with TreeBrowse`DocsNavigatorLookup[False]


11

This is a documentation bug. Our source notebooks do contain documentation for experimental and future features, but they are supposed to be stripped in the process of being bundled with the product. In this case the bug is that the usage statement is marked as not to be included, but is still ending up in the built documentation. We apologize for the ...


10

This answer in not the answer you want. There are almost certainly more options for a button's appearance than are documented in the Help Center. As far a I know there is no way to discover what appearance options apply to buttons. This seems to be a deliberate policy on the part of WRI. I recently had a exchange of email with WRI tech suppor on a related ...


10

I made a little interactive thing ('reportPackages') that often proves helpful. It lives in my own utilities package: ?? reportPackages reportPackages::usage = "reportPackages produces a window with a SetterBar and a button. The SetterBar lists all currently linked Packages (from $Packages). The button produces a clickable ...


10

Update 2: Found a few more and started to document which elements apply to which controls. The total number of elements is now 27 (or 29 if you include All and None). I could not find examples for the InteractiveTradingChart elements or for the UpdateButton. Can anyone help there? appearanceList = {"AutorunPlayButton", "BookmarksButton", ...


10

I decided to create a repository of usually undocumented lists (or just a links to similar topics) of available options: AppearanceElements for Manipulate and friends MouseAppearance styles All Font families All the Properties that ColorData supports? Events for EventHandler. AFAICT additional two that work: "MouseExited"/"MouseEntered" EventHandler ...


10

Padding Without padding of any kind the over-all aspect ratio and element (primitive) aspect ratio are the same and as specified: g0 = Graphics[{Opacity[0.5, Red], Rectangle[{0, 0}, {3, 2}]}, AspectRatio -> 2/3, Background -> GrayLevel[0.8], PlotRangePadding -> 0] (There is a one pixel discrepancy along the right edge where the background ...



Only top voted, non community-wiki answers of a minimum length are eligible