Store Dynamic-accessible hidden metadata in a cell The 2019 Stack Overflow Developer Survey...
Circular reasoning in L'Hopital's rule
                
                    Is there a way to generate uniformly distributed points on a sphere from a fixed amount of random real numbers per point?
                
                    Loose spokes after only a few rides
                
                    Single author papers against my advisor's will?
                
                    Would an alien lifeform be able to achieve space travel if lacking in vision?
                
                    Make it rain characters
                
                    Can the Right Ascension and Argument of Perigee of a spacecraft's orbit keep varying by themselves with time?
                
                    How to type a long/em dash `—`
                
                    Button changing its text & action. Good or terrible?
                
                    60's-70's movie: home appliances revolting against the owners
                
                    Do warforged have souls?
                
                    How do spell lists change if the party levels up without taking a long rest?
                
                    Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
                
                    How did passengers keep warm on sail ships?
                
                    "is" operation returns false even though two objects have same id
                
                    Can the DM override racial traits?
                
                    Deal with toxic manager when you can't quit
                
                    How to support a colleague who finds meetings extremely tiring?
                
                    Match Roman Numerals
                
                    Huge performance difference of the command find with and without using %M option to show permissions
                
                    How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
                
                    Can a flute soloist sit?
                
                    Is an up-to-date browser secure on an out-of-date OS?
                
                    What do I do when my TA workload is more than expected?
Store Dynamic-accessible hidden metadata in a cell
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Notebook's TaggingRules inherit too muchGraphics copy pasteSaving my code before cell evaluations: Insurance against front end hanginghow to select all cells with specific property such as the ones that are closedHow can I programmatically ungroup cellsHow is CellContext->CellGroup supposed to work?How to close all tagged input cells without closing their output cells?How to Print a Cell Landscape in a Portrait Orientation Notebook?Cell @ CellGroupData[… in Cells familyDynamic docked toolbar that appears only in the Working screen environmentStop notebook from auto-scrolling upon printing
$begingroup$
Is there a way to store metadata in a cell in such a way that it can be accessed with Dynamic?
Think of e.g. how ExternalLanguage cells work. We can select whether they should use Python or NodeJS and this state is permanently stored in the CellEvaluationLanguage cell option.

The cell expression would be something like
Cell["", "ExternalLanguage",
 CellEvaluationLanguage->"NodeJS"]
It is unclear to me if CellEvaluationLanguage needs to be a built-in option for this to work. I tried something similar with an arbitrary option name and it did not work. For example, CurrentValue[EvaluationCell[], FooBar] = 123 will not set the FooBar option on the cell.
Next, I tried to use TaggingRules.
We can do
CurrentValue[EvaluationCell[], {TaggingRules, "FooBar"}] = 123
then examine the input cell's cell expression. It will have the FooBar tagging rule set. But it will also have inherited all tagging rules from the front end. On my machine I see this:

Is there a way that avoids these problems and still managed to store arbitrary hidden metadata in the cell?
What I am aiming for is implementing a similar selector to what we have for ExternalLanguage cells.  Here's a proof of concept with TaggingRules that still has the problem I described above. Evaluate the following to add a selector to the input cell:
CurrentValue[EvaluationCell[], 
  CellFrameLabels] = {{None, 
   Cell[BoxData[
     PopupMenuBox[
      Dynamic[CurrentValue[
        ParentCell[EvaluationCell[]], {TaggingRules, 
         "MyRule"}]], {6 -> "6", 24 -> "24"}]]]}, {None, None}}

front-end dynamic notebooks cells metadata
$endgroup$
add a comment |
$begingroup$
Is there a way to store metadata in a cell in such a way that it can be accessed with Dynamic?
Think of e.g. how ExternalLanguage cells work. We can select whether they should use Python or NodeJS and this state is permanently stored in the CellEvaluationLanguage cell option.

The cell expression would be something like
Cell["", "ExternalLanguage",
 CellEvaluationLanguage->"NodeJS"]
It is unclear to me if CellEvaluationLanguage needs to be a built-in option for this to work. I tried something similar with an arbitrary option name and it did not work. For example, CurrentValue[EvaluationCell[], FooBar] = 123 will not set the FooBar option on the cell.
Next, I tried to use TaggingRules.
We can do
CurrentValue[EvaluationCell[], {TaggingRules, "FooBar"}] = 123
then examine the input cell's cell expression. It will have the FooBar tagging rule set. But it will also have inherited all tagging rules from the front end. On my machine I see this:

Is there a way that avoids these problems and still managed to store arbitrary hidden metadata in the cell?
What I am aiming for is implementing a similar selector to what we have for ExternalLanguage cells.  Here's a proof of concept with TaggingRules that still has the problem I described above. Evaluate the following to add a selector to the input cell:
CurrentValue[EvaluationCell[], 
  CellFrameLabels] = {{None, 
   Cell[BoxData[
     PopupMenuBox[
      Dynamic[CurrentValue[
        ParentCell[EvaluationCell[]], {TaggingRules, 
         "MyRule"}]], {6 -> "6", 24 -> "24"}]]]}, {None, None}}

front-end dynamic notebooks cells metadata
$endgroup$
 
 
 
 
 
 
 $begingroup$
 TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
 $endgroup$
 – Kuba♦
 7 hours ago
 
 
 
add a comment |
$begingroup$
Is there a way to store metadata in a cell in such a way that it can be accessed with Dynamic?
Think of e.g. how ExternalLanguage cells work. We can select whether they should use Python or NodeJS and this state is permanently stored in the CellEvaluationLanguage cell option.

The cell expression would be something like
Cell["", "ExternalLanguage",
 CellEvaluationLanguage->"NodeJS"]
It is unclear to me if CellEvaluationLanguage needs to be a built-in option for this to work. I tried something similar with an arbitrary option name and it did not work. For example, CurrentValue[EvaluationCell[], FooBar] = 123 will not set the FooBar option on the cell.
Next, I tried to use TaggingRules.
We can do
CurrentValue[EvaluationCell[], {TaggingRules, "FooBar"}] = 123
then examine the input cell's cell expression. It will have the FooBar tagging rule set. But it will also have inherited all tagging rules from the front end. On my machine I see this:

Is there a way that avoids these problems and still managed to store arbitrary hidden metadata in the cell?
What I am aiming for is implementing a similar selector to what we have for ExternalLanguage cells.  Here's a proof of concept with TaggingRules that still has the problem I described above. Evaluate the following to add a selector to the input cell:
CurrentValue[EvaluationCell[], 
  CellFrameLabels] = {{None, 
   Cell[BoxData[
     PopupMenuBox[
      Dynamic[CurrentValue[
        ParentCell[EvaluationCell[]], {TaggingRules, 
         "MyRule"}]], {6 -> "6", 24 -> "24"}]]]}, {None, None}}

front-end dynamic notebooks cells metadata
$endgroup$
Is there a way to store metadata in a cell in such a way that it can be accessed with Dynamic?
Think of e.g. how ExternalLanguage cells work. We can select whether they should use Python or NodeJS and this state is permanently stored in the CellEvaluationLanguage cell option.

The cell expression would be something like
Cell["", "ExternalLanguage",
 CellEvaluationLanguage->"NodeJS"]
It is unclear to me if CellEvaluationLanguage needs to be a built-in option for this to work. I tried something similar with an arbitrary option name and it did not work. For example, CurrentValue[EvaluationCell[], FooBar] = 123 will not set the FooBar option on the cell.
Next, I tried to use TaggingRules.
We can do
CurrentValue[EvaluationCell[], {TaggingRules, "FooBar"}] = 123
then examine the input cell's cell expression. It will have the FooBar tagging rule set. But it will also have inherited all tagging rules from the front end. On my machine I see this:

Is there a way that avoids these problems and still managed to store arbitrary hidden metadata in the cell?
What I am aiming for is implementing a similar selector to what we have for ExternalLanguage cells.  Here's a proof of concept with TaggingRules that still has the problem I described above. Evaluate the following to add a selector to the input cell:
CurrentValue[EvaluationCell[], 
  CellFrameLabels] = {{None, 
   Cell[BoxData[
     PopupMenuBox[
      Dynamic[CurrentValue[
        ParentCell[EvaluationCell[]], {TaggingRules, 
         "MyRule"}]], {6 -> "6", 24 -> "24"}]]]}, {None, None}}

front-end dynamic notebooks cells metadata
front-end dynamic notebooks cells metadata
asked 10 hours ago
SzabolcsSzabolcs
164k14448947
164k14448947
 
 
 
 
 
 
 $begingroup$
 TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
 $endgroup$
 – Kuba♦
 7 hours ago
 
 
 
add a comment |
 
 
 
 
 
 
 $begingroup$
 TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
 $endgroup$
 – Kuba♦
 7 hours ago
 
 
 
$begingroup$
TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
$endgroup$
– Kuba♦
7 hours ago
$begingroup$
TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
$endgroup$
– Kuba♦
7 hours ago
add a comment |
                                2 Answers
                            2
                        
active
oldest
votes
$begingroup$
You can give "Input" cells a default TaggingRules option of TaggingRules -> {}. Then, using CurrentValue will not include the notebook tagging rules. For example:
SetOptions[
    EvaluationNotebook[],
    StyleDefinitions -> Notebook[
        {
        Cell[StyleData[StyleDefinitions->"Default.nb"]],
        Cell[StyleData["Input"],TaggingRules->{}]
        },
        StyleDefinitions->"PrivateStylesheetFormatting.nb"
    ]
]
Then,
CurrentValue[EvaluationNotebook[], TaggingRules] = {"parent" -> "default"};
CurrentValue[EvaluationNotebook[], TaggingRules]
{"parent" -> "default"}
Let's try using CurrentValue to modify a cell:
CurrentValue[EvaluationCell[], {TaggingRules, "key"}] = "value";
CurrentValue[EvaluationCell[], TaggingRules]
{"key" -> "value"}
The notebook tagging rule is not included.
$endgroup$
 
 
 
 
 
 
 $begingroup$
 Looks good. So you think- TaggingRulesis the way to go? This won't be an Input style cell anyway, so setting default- TaggingRulesfor the style is completely fine.
 $endgroup$
 – Szabolcs
 7 hours ago
 
 
 
 
 
add a comment |
$begingroup$
This works for your explicit case:
CurrentValue[EvaluationCell[], CellFrameLabels] = {
   {
    None,
    Cell[
     BoxData[
      PopupMenuBox[
       Dynamic[
        CurrentValue[
         ParentCell[EvaluationCell[]],
         {TaggingRules, "MyRule"}, 
         FrontEnd`SetOptions[
          ParentCell[EvaluationCell[]],
          TaggingRules -> {"MyRule" -> None}
          ]
         ]
        ],
       {6 -> "6", 24 -> "24"}
       ]
      ]
     ]},
   {None, None}
   };
Options[EvaluationCell[], TaggingRules]
SetOptions didn't like operating on the ParentCell so I had to force it to pull that from the kernel, but it should still perform alright I think.
Basic Idea
Here's a kinda solution. I'm gonna assume when the CurrentValue isn't defined you use a default value. If that's the case you can do this:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
That forces the TaggingRules to be directly set rather than updated. Here's a proof of concept. First set up some state that can be inherited:
SetOptions[EvaluationNotebook[], 
  TaggingRules -> {"parentKey" -> "default"}];
Now usually we'd get inheritance:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 "default"
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"parentKey" -> "default", "key" -> "default"}}
With this trick though we don't:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"key" -> "default"}}
Is it elegant? No. But it works if that's all you care about.
$endgroup$
add a comment |
                                Your Answer
                            
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "387"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmathematica.stackexchange.com%2fquestions%2f195082%2fstore-dynamic-accessible-hidden-metadata-in-a-cell%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
                                2 Answers
                            2
                        
active
oldest
votes
                                2 Answers
                            2
                        
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
You can give "Input" cells a default TaggingRules option of TaggingRules -> {}. Then, using CurrentValue will not include the notebook tagging rules. For example:
SetOptions[
    EvaluationNotebook[],
    StyleDefinitions -> Notebook[
        {
        Cell[StyleData[StyleDefinitions->"Default.nb"]],
        Cell[StyleData["Input"],TaggingRules->{}]
        },
        StyleDefinitions->"PrivateStylesheetFormatting.nb"
    ]
]
Then,
CurrentValue[EvaluationNotebook[], TaggingRules] = {"parent" -> "default"};
CurrentValue[EvaluationNotebook[], TaggingRules]
{"parent" -> "default"}
Let's try using CurrentValue to modify a cell:
CurrentValue[EvaluationCell[], {TaggingRules, "key"}] = "value";
CurrentValue[EvaluationCell[], TaggingRules]
{"key" -> "value"}
The notebook tagging rule is not included.
$endgroup$
 
 
 
 
 
 
 $begingroup$
 Looks good. So you think- TaggingRulesis the way to go? This won't be an Input style cell anyway, so setting default- TaggingRulesfor the style is completely fine.
 $endgroup$
 – Szabolcs
 7 hours ago
 
 
 
 
 
add a comment |
$begingroup$
You can give "Input" cells a default TaggingRules option of TaggingRules -> {}. Then, using CurrentValue will not include the notebook tagging rules. For example:
SetOptions[
    EvaluationNotebook[],
    StyleDefinitions -> Notebook[
        {
        Cell[StyleData[StyleDefinitions->"Default.nb"]],
        Cell[StyleData["Input"],TaggingRules->{}]
        },
        StyleDefinitions->"PrivateStylesheetFormatting.nb"
    ]
]
Then,
CurrentValue[EvaluationNotebook[], TaggingRules] = {"parent" -> "default"};
CurrentValue[EvaluationNotebook[], TaggingRules]
{"parent" -> "default"}
Let's try using CurrentValue to modify a cell:
CurrentValue[EvaluationCell[], {TaggingRules, "key"}] = "value";
CurrentValue[EvaluationCell[], TaggingRules]
{"key" -> "value"}
The notebook tagging rule is not included.
$endgroup$
 
 
 
 
 
 
 $begingroup$
 Looks good. So you think- TaggingRulesis the way to go? This won't be an Input style cell anyway, so setting default- TaggingRulesfor the style is completely fine.
 $endgroup$
 – Szabolcs
 7 hours ago
 
 
 
 
 
add a comment |
$begingroup$
You can give "Input" cells a default TaggingRules option of TaggingRules -> {}. Then, using CurrentValue will not include the notebook tagging rules. For example:
SetOptions[
    EvaluationNotebook[],
    StyleDefinitions -> Notebook[
        {
        Cell[StyleData[StyleDefinitions->"Default.nb"]],
        Cell[StyleData["Input"],TaggingRules->{}]
        },
        StyleDefinitions->"PrivateStylesheetFormatting.nb"
    ]
]
Then,
CurrentValue[EvaluationNotebook[], TaggingRules] = {"parent" -> "default"};
CurrentValue[EvaluationNotebook[], TaggingRules]
{"parent" -> "default"}
Let's try using CurrentValue to modify a cell:
CurrentValue[EvaluationCell[], {TaggingRules, "key"}] = "value";
CurrentValue[EvaluationCell[], TaggingRules]
{"key" -> "value"}
The notebook tagging rule is not included.
$endgroup$
You can give "Input" cells a default TaggingRules option of TaggingRules -> {}. Then, using CurrentValue will not include the notebook tagging rules. For example:
SetOptions[
    EvaluationNotebook[],
    StyleDefinitions -> Notebook[
        {
        Cell[StyleData[StyleDefinitions->"Default.nb"]],
        Cell[StyleData["Input"],TaggingRules->{}]
        },
        StyleDefinitions->"PrivateStylesheetFormatting.nb"
    ]
]
Then,
CurrentValue[EvaluationNotebook[], TaggingRules] = {"parent" -> "default"};
CurrentValue[EvaluationNotebook[], TaggingRules]
{"parent" -> "default"}
Let's try using CurrentValue to modify a cell:
CurrentValue[EvaluationCell[], {TaggingRules, "key"}] = "value";
CurrentValue[EvaluationCell[], TaggingRules]
{"key" -> "value"}
The notebook tagging rule is not included.
answered 8 hours ago


Carl WollCarl Woll
73.6k398192
73.6k398192
 
 
 
 
 
 
 $begingroup$
 Looks good. So you think- TaggingRulesis the way to go? This won't be an Input style cell anyway, so setting default- TaggingRulesfor the style is completely fine.
 $endgroup$
 – Szabolcs
 7 hours ago
 
 
 
 
 
add a comment |
 
 
 
 
 
 
 $begingroup$
 Looks good. So you think- TaggingRulesis the way to go? This won't be an Input style cell anyway, so setting default- TaggingRulesfor the style is completely fine.
 $endgroup$
 – Szabolcs
 7 hours ago
 
 
 
 
 
$begingroup$
Looks good. So you think
TaggingRules is the way to go? This won't be an Input style cell anyway, so setting default TaggingRules for the style is completely fine.$endgroup$
– Szabolcs
7 hours ago
$begingroup$
Looks good. So you think
TaggingRules is the way to go? This won't be an Input style cell anyway, so setting default TaggingRules for the style is completely fine.$endgroup$
– Szabolcs
7 hours ago
add a comment |
$begingroup$
This works for your explicit case:
CurrentValue[EvaluationCell[], CellFrameLabels] = {
   {
    None,
    Cell[
     BoxData[
      PopupMenuBox[
       Dynamic[
        CurrentValue[
         ParentCell[EvaluationCell[]],
         {TaggingRules, "MyRule"}, 
         FrontEnd`SetOptions[
          ParentCell[EvaluationCell[]],
          TaggingRules -> {"MyRule" -> None}
          ]
         ]
        ],
       {6 -> "6", 24 -> "24"}
       ]
      ]
     ]},
   {None, None}
   };
Options[EvaluationCell[], TaggingRules]
SetOptions didn't like operating on the ParentCell so I had to force it to pull that from the kernel, but it should still perform alright I think.
Basic Idea
Here's a kinda solution. I'm gonna assume when the CurrentValue isn't defined you use a default value. If that's the case you can do this:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
That forces the TaggingRules to be directly set rather than updated. Here's a proof of concept. First set up some state that can be inherited:
SetOptions[EvaluationNotebook[], 
  TaggingRules -> {"parentKey" -> "default"}];
Now usually we'd get inheritance:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 "default"
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"parentKey" -> "default", "key" -> "default"}}
With this trick though we don't:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"key" -> "default"}}
Is it elegant? No. But it works if that's all you care about.
$endgroup$
add a comment |
$begingroup$
This works for your explicit case:
CurrentValue[EvaluationCell[], CellFrameLabels] = {
   {
    None,
    Cell[
     BoxData[
      PopupMenuBox[
       Dynamic[
        CurrentValue[
         ParentCell[EvaluationCell[]],
         {TaggingRules, "MyRule"}, 
         FrontEnd`SetOptions[
          ParentCell[EvaluationCell[]],
          TaggingRules -> {"MyRule" -> None}
          ]
         ]
        ],
       {6 -> "6", 24 -> "24"}
       ]
      ]
     ]},
   {None, None}
   };
Options[EvaluationCell[], TaggingRules]
SetOptions didn't like operating on the ParentCell so I had to force it to pull that from the kernel, but it should still perform alright I think.
Basic Idea
Here's a kinda solution. I'm gonna assume when the CurrentValue isn't defined you use a default value. If that's the case you can do this:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
That forces the TaggingRules to be directly set rather than updated. Here's a proof of concept. First set up some state that can be inherited:
SetOptions[EvaluationNotebook[], 
  TaggingRules -> {"parentKey" -> "default"}];
Now usually we'd get inheritance:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 "default"
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"parentKey" -> "default", "key" -> "default"}}
With this trick though we don't:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"key" -> "default"}}
Is it elegant? No. But it works if that's all you care about.
$endgroup$
add a comment |
$begingroup$
This works for your explicit case:
CurrentValue[EvaluationCell[], CellFrameLabels] = {
   {
    None,
    Cell[
     BoxData[
      PopupMenuBox[
       Dynamic[
        CurrentValue[
         ParentCell[EvaluationCell[]],
         {TaggingRules, "MyRule"}, 
         FrontEnd`SetOptions[
          ParentCell[EvaluationCell[]],
          TaggingRules -> {"MyRule" -> None}
          ]
         ]
        ],
       {6 -> "6", 24 -> "24"}
       ]
      ]
     ]},
   {None, None}
   };
Options[EvaluationCell[], TaggingRules]
SetOptions didn't like operating on the ParentCell so I had to force it to pull that from the kernel, but it should still perform alright I think.
Basic Idea
Here's a kinda solution. I'm gonna assume when the CurrentValue isn't defined you use a default value. If that's the case you can do this:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
That forces the TaggingRules to be directly set rather than updated. Here's a proof of concept. First set up some state that can be inherited:
SetOptions[EvaluationNotebook[], 
  TaggingRules -> {"parentKey" -> "default"}];
Now usually we'd get inheritance:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 "default"
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"parentKey" -> "default", "key" -> "default"}}
With this trick though we don't:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"key" -> "default"}}
Is it elegant? No. But it works if that's all you care about.
$endgroup$
This works for your explicit case:
CurrentValue[EvaluationCell[], CellFrameLabels] = {
   {
    None,
    Cell[
     BoxData[
      PopupMenuBox[
       Dynamic[
        CurrentValue[
         ParentCell[EvaluationCell[]],
         {TaggingRules, "MyRule"}, 
         FrontEnd`SetOptions[
          ParentCell[EvaluationCell[]],
          TaggingRules -> {"MyRule" -> None}
          ]
         ]
        ],
       {6 -> "6", 24 -> "24"}
       ]
      ]
     ]},
   {None, None}
   };
Options[EvaluationCell[], TaggingRules]
SetOptions didn't like operating on the ParentCell so I had to force it to pull that from the kernel, but it should still perform alright I think.
Basic Idea
Here's a kinda solution. I'm gonna assume when the CurrentValue isn't defined you use a default value. If that's the case you can do this:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
That forces the TaggingRules to be directly set rather than updated. Here's a proof of concept. First set up some state that can be inherited:
SetOptions[EvaluationNotebook[], 
  TaggingRules -> {"parentKey" -> "default"}];
Now usually we'd get inheritance:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 "default"
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"parentKey" -> "default", "key" -> "default"}}
With this trick though we don't:
CurrentValue[
 EvaluationCell[],
 {TaggingRules, "key"},
 FEPrivate`FrontEndExecute@
  FrontEnd`SetOptions[FrontEnd`EvaluationCell[], 
   TaggingRules -> {"key" -> "default"}]
 ]
Options[EvaluationCell[], TaggingRules]
"default"
{TaggingRules -> {"key" -> "default"}}
Is it elegant? No. But it works if that's all you care about.
edited 9 hours ago
answered 10 hours ago
b3m2a1b3m2a1
28.7k359166
28.7k359166
add a comment |
add a comment |
Thanks for contributing an answer to Mathematica Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmathematica.stackexchange.com%2fquestions%2f195082%2fstore-dynamic-accessible-hidden-metadata-in-a-cell%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
$begingroup$
TaggingRules problem is known: mathematica.stackexchange.com/q/139017/5478
$endgroup$
– Kuba♦
7 hours ago