User Portlet
| Discussions |
|---|
| Sorry -- it took longer than I intended to get back to you. In the near term, you can work around the usage formatting issue by not using newlines in the usage message. We're going to handle that in an update coming soon, but if you make the... |
| So it turns out that there is a mechanism for doing this in Workbench's DocumentationTools: - On the F tab, click "Links", then "More Link Tools". You should see a "Make Sel" and a "Make Link" button, among some others. - Select the cell you... |
| Visible CellTags use the same style as the In/Out labels, so, to my knowledge, you can't change one without affecting the other. That said, you can change their styling by adding/altering the "CellLabel" style in a stylesheet. -Brian |
| I think you want to stick with Grid here and avoid MatrixForm and TableForm altogether. With a bit of array manipulation, you can add the row/column headers to the list and they will display when you wrap them in Grid[ ]. This function written... |
| If all you're looking for is an automatically generated unique identifier for each cell you want to link to, then you could use CellIDs. If you set the notebook option CreateCellID -> True (which you can set in the style sheet), then every cell... |
| I think all of these can be handled using the "SectionGrouping" type, which is what all of the documentation style sheets use for cell grouping. From... |
| Right. CreateDialog does some automatic option settings when it receives a Cell or list of Cells. If you use a Notebook expression though: [mcode]CreateDialog[ Notebook[{Cell[ BoxData[MakeBoxes[Module[{x, y, z}, z = x y; Sin[z]]]], "Input", ... |