New answers tagged

4

Probably you should use NotebookEvaluate instead of SelectionEvaluate. According to the Documentation, By default, NotebookEvaluate evaluates the cells of a notebook in the same way that Get evaluates the lines of a package file. For example try: nb = CreateDocument[ExpressionCell[Defer[Pause[10]], "Input"]]; NotebookEvaluate[nb] Print["!"] The ...


1

This has been filed and officially accepted as an issue: Thank you for contacting Wolfram Technical Support. I was able to reproduce the issue, and consequently, I filed a report with our development team raising the issues and also shared your contact information with them so you can be notified once the issue is resolved. Thank you again for ...


6

An alternative way of getting a similar display would be to define a new function leftFramed that only puts a vertical extensible line to the left of the content: leftFrame /: MakeBoxes[leftFrame[obj_], _] := RowBox[{"\[LeftBracketingBar]", ToBoxes[obj]}] Framed[x -> leftFrame[ Column[{"Depression", "PTSD", "Diabetes Type II", "Smoker"}]]] ...


6

Would a CellFrame around a TextCell work? Framed[ x -> TextCell[ Column[{"Depression", "PTSD", "Diabetes Type II", "Smoker"}], "Text", CellFrame -> {{True, False}, {False, False}}]]


1

From the link in the comment above I have devised a solution included here for ParallelSubmit specific searches. Monitor can not be used so I make a progress function that will assist with the visual status update. progress[current_, total_] := Column[{StringRiffle[ToString /@ {current, total}, " of "], ProgressIndicator[current, {0, total}]}, ...


0

In version 10, we need to Evaluation->Quit Kernel and then Start Kernel to prevent the debugger tool window from reappear.


3

I think this question is a mistake from my side but I also think this answer may be useful for future visitors. testing involves low level notebook programming It seems I was just expecting from this to be too forgiving, if you make your functions self contained, independent from EvaluationNotebook[], it will work quite fine. Module[{nb, oCell}, nb = ...


8

You can overwrite specific NotebookEventActions which are responsible for that: CreateDialog[ Overlay[{DefaultButton[], CancelButton[], InputField[]}, {3}, 3], NotebookEventActions -> { "EscapeKeyDown" :> {}, "ReturnKeyDown" :> {}, PassEventsDown -> True } ] PassEventsDown -> True allows "\[AliasDelimiter]" to appear in the ...


3

A support case with the identification [CASE:3620463] was created. And a reply: [...] I have forwarded an incident report to our developers with the information you provided.


0

I realise this question is old, but in my quest to find a solution to a similar problem to OP I have come up with a solution using CellTags and FrontEndExecute (like Rolf M). I try to avoid Dynamic. Create a cell tag for the cell you want to evaluate with a button. This approach will Evaluate all cells with the same CellTag and depending on the scenario ...



Top 50 recent answers are included