Skip to main content

front end - Strange caching of Palette's TaggingRules


Please follow those steps to get the idea about the problem:




  1. Let's create a palette:


    nb = CreatePalette[
       DynamicModule[{},
        Panel["Hello you!", ImageSize -> 500, Alignment -> Center]

        ,
        SynchronousInitialization -> False,
        Initialization :> (
          CreateDocument@CurrentValue[EvaluationNotebook[], TaggingRules]
        )
       ],
       WindowTitle -> "Palette B ",
       TaggingRules -> {"B" -> 1123}
    ];



  2. And save it to users palettes directory.


    palettePath = FileNameJoin[{$UserBaseDirectory, "SystemFiles", 
        "FrontEnd", "Palettes", "TESTPalette.nb"}];

    NotebookSave[  nb,   palettePath   ];
    NotebookClose @ nb;


  3. Reset menus to show it there:



    MathLink`CallFrontEnd[ FrontEnd`ResetMenusPacket[{Automatic, Automatic}]]


    enter image description here





  4. Click on the item or run FrontEndTokenExecute["OpenFromPalettesMenu", FileNameTake @ palettePath] and we have it working:



    enter image description here






  5. Close the palette and delete it.


    DeleteFile @ palettePath


  6. Repeat steps 1-4 with different TaggingRules


     WindowTitle -> "Palette A",
     TaggingRules -> {"A" -> 1112}



The problem


Now there is a new Palette's Menu item - "Palette A" - and that notebook is opened when clicked, yet the old TaggingRules with "B" are prompted...



enter image description here





  • But the file is saved correctly:



    FilePrint @ palettePath

    shows that there is "A" inside TaggingRules. So "B" was somehow, cached somewhere.




  • Also, when one opens the notebook manually or with NotebookOpen @ paletePath it works well...




  • The problem remains after restarting Mathematica.





  • The SynchronousInitialization option is necessary, I wasn't able to reproduce the problem without it.




What is going on and how to deal with this?



Answer



As noted by ilian, this behaviour is explained in StoringAndTrackingPaletteStates tutorial.


Shortly, CurrentValue[$FrontEnd, System`PalettesMenuSettings] keeps those values cached.


In order to achieve what I described in the question we have to drop an entry that coresponds to our palette.


It doesn't really matter when it's done. Just do it before you need it to work :)



CurrentValue[$FrontEnd, System`PalettesMenuSettings] = DeleteCases[
  CurrentValue[$FrontEnd, System`PalettesMenuSettings],
  FileNameTake[palettePath] -> _
]

Comments

Post a Comment

Popular posts from this blog

functions - Get leading series expansion term?

Given a function f[x] , I would like to have a function leadingSeries that returns just the leading term in the series around x=0 . For example: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x)] x and leadingSeries[(1/x + 2 + (1 - 1/x^3)/4)/(4 + x)] -(1/(16 x^3)) Is there such a function in Mathematica? Or maybe one can implement it efficiently? EDIT I finally went with the following implementation, based on Carl Woll 's answer: lds[ex_,x_]:=( (ex/.x->(x+O[x]^2))/.SeriesData[U_,Z_,L_List,Mi_,Ma_,De_]:>SeriesData[U,Z,{L[[1]]},Mi,Mi+1,De]//Quiet//Normal) The advantage is, that this one also properly works with functions whose leading term is a constant: lds[Exp[x],x] 1 Answer Update 1 Updated to eliminate SeriesData and to not return additional terms Perhaps you could use: leadingSeries[expr_, x_] := Normal[expr /. x->(x+O[x]^2) /. a_List :> Take[a, 1]] Then for your examples: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x), x] leadingSeries[Exp[x], x] leadingSeries[(1/x + 2 + (1 - 1/x...
Post a Comment
Read more

mathematical optimization - Minimizing using indices, error: Part::pkspec1: The expression cannot be used as a part specification

I want to use Minimize where the variables to minimize are indices pointing into an array. Here a MWE that hopefully shows what my problem is. vars = u@# & /@ Range[3]; cons = Flatten@ { Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; Minimize[{Total@((vec1[[#]] - vec2[[u[#]]])^2 & /@ Range[1, 3]), cons}, vars, Integers] The error I get: Part::pkspec1: The expression u[1] cannot be used as a part specification. >> Answer Ok, it seems that one can get around Mathematica trying to evaluate vec2[[u[1]]] too early by using the function Indexed[vec2,u[1]] . The working MWE would then look like the following: vars = u@# & /@ Range[3]; cons = Flatten@{ Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; NMinimize[ {Total@((vec1[[#]] - Indexed[vec2, u[#]])^2 & /@ R...
Post a Comment
Read more

What is and isn't a valid variable specification for Manipulate?

I have an expression whose terms have arguments (representing subscripts), like this: myExpr = A[0] + V[1,T] I would like to put it inside a Manipulate to see its value as I move around the parameters. (The goal is eventually to plot it wrt one of the variables inside.) However, Mathematica complains when I set V[1,T] as a manipulated variable: Manipulate[Evaluate[myExpr], {A[0], 0, 1}, {V[1, T], 0, 1}] (*Manipulate::vsform: Manipulate argument {V[1,T],0,1} does not have the correct form for a variable specification. >> *) As a workaround, if I get rid of the symbol T inside the argument, it works fine: Manipulate[ Evaluate[myExpr /. T -> 15], {A[0], 0, 1}, {V[1, 15], 0, 1}] Why this behavior? Can anyone point me to the documentation that says what counts as a valid variable? And is there a way to get Manpiulate to accept an expression with a symbolic argument as a variable? Investigations I've done so far: I tried using variableQ from this answer , but it says V[1...
Post a Comment
Read more