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

front end - keyboard shortcut to invoke Insert new matrix

I frequently need to type in some matrices, and the menu command Insert > Table/Matrix > New... allows matrices with lines drawn between columns and rows, which is very helpful. I would like to make a keyboard shortcut for it, but cannot find the relevant frontend token command (4209405) for it. Since the FullForm[] and InputForm[] of matrices with lines drawn between rows and columns is the same as those without lines, it's hard to do this via 3rd party system-wide text expanders (e.g. autohotkey or atext on mac). How does one assign a keyboard shortcut for the menu item Insert > Table/Matrix > New... , preferably using only mathematica? Thanks! Answer In the MenuSetup.tr (for linux located in the $InstallationDirectory/SystemFiles/FrontEnd/TextResources/X/ directory), I changed the line MenuItem["&New...", "CreateGridBoxDialog"] to read MenuItem["&New...", "CreateGridBoxDialog", MenuKey["m", Modifiers-...
Post a Comment
Read more

How to thread a list

I have data in format data = {{a1, a2}, {b1, b2}, {c1, c2}, {d1, d2}} Tableform: I want to thread it to : tdata = {{{a1, b1}, {a2, b2}}, {{a1, c1}, {a2, c2}}, {{a1, d1}, {a2, d2}}} Tableform: And I would like to do better then pseudofunction[n_] := Transpose[{data2[[1]], data2[[n]]}]; SetAttributes[pseudofunction, Listable]; Range[2, 4] // pseudofunction Here is my benchmark data, where data3 is normal sample of real data. data3 = Drop[ExcelWorkBook[[Column1 ;; Column4]], None, 1]; data2 = {a #, b #, c #, d #} & /@ Range[1, 10^5]; data = RandomReal[{0, 1}, {10^6, 4}]; Here is my benchmark code kptnw[list_] := Transpose[{Table[First@#, {Length@# - 1}], Rest@#}, {3, 1, 2}] &@list kptnw2[list_] := Transpose[{ConstantArray[First@#, Length@# - 1], Rest@#}, {3, 1, 2}] &@list OleksandrR[list_] := Flatten[Outer[List, List@First[list], Rest[list], 1], {{2}, {1, 4}}] paradox2[list_] := Partition[Riffle[list[[1]], #], 2] & /@ Drop[list, 1] RM[list_] := FoldList[Transpose[{First@li...
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