Skip to main content

manipulate - Question about making TabView remember what tab to open


Background: Consider the following ( for the purpose of illustrating this question ) simplified, but working snippet of code.


 TabView[

  {
   {patt, "Pattern" -> 1},
   {motif, "Motif" -> Column[{
      Button["Type", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100],
      Button["New shape", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100],
      Button["Pixel", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100]}]}
  },
  Dynamic[tab]]

I have a GUI in a Module / Manipulate construction which contains a tabview that displays several views of the same data on its tabs. Each tab contains a series of buttons to further specify the particular view on that tab. Each tab consists several buttons and other controls, i.e. setterbars, 2D sliders. After each click or other action on a control the data is modified and all views are recalculated and displayed on the tabs.



The issue is that after each tab the tabview always returns to page 1. I have already made accomodations by using the following format of TabView:


  TabView[{ 
   {value1, "Tabname"->CodeOnTab1}, 
   {valueN, "Tabname"->CodeOnTabn} }, 
  Dynamic[VAR]

As I understand the Tabview opens tabN if VAR is set to valueN. This leads to the following question: what is the best =coding strategy= to make a TabView aware of the tab it should display ( open ) when it is re-displayed ( considering the last user action ) ? The goal / criteria is: minimal code use.



Answer



I may have misunderstood your problem, but it looks like you just need to create a persistent local variable keeping the value of the tab which was last open. One way to do this:


DynamicModule[{tab},

   myCustomTab[] :=
      TabView[
       {
          {patt, "Pattern" -> 1},
          {motif, "Motif" -> 
             Column[{
               Button["Type", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100],
               Button["New shape", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100],
               Button["Pixel", Print[" NOT IMPLEMENTED YET"], ImageSize -> 100]}]}
       },

       Dynamic[tab]]
]

What matters is that you create a closure, so the variable tab is not local to the function myCustomTab (in the sense that it is not re-initialized on every function's invocation).


EDIT


Ok, it is probably a good time to explain what I mean by code generation, since I mentioned this technique many times already. Basically, I mean that you will be better off by creating your own DSL for UI. I will illustrate it here simplistically with rule application, but generally I would rather use recursion, which is more powerful. You can notice that your code is full of repeated elements, and this is true even for such a small code snippet. Here is one way to reduce the boilerplate:


This is a function written by @Szabolcs, which will be handy here


ClearAll[withRules]
SetAttributes[withRules, HoldAll]
withRules[rules_, expr_] :=

  First@PreemptProtect@Internal`InheritedBlock[
    {Rule, RuleDelayed},
    SetAttributes[{Rule, RuleDelayed}, HoldFirst];
    Hold[expr] /. rules
]

This is the starting point:


myTab = 
  myTabView[
   {"Pattern" -> 1,

     "Motif" -> Column[{
         myButton["Type", noimpl[]],
         myButton["New shape", noimpl[]],
         myButton["Pixel", noimpl[]]}]
    }];

This is an auxiliary function:


Clear[dressTabView];
dressTabView[lrules_] :=
   t : myTabView[{__Rule}] :>

     DynamicModule[{tab},
        Append[
           Replace[t, e : (label_ -> w_) :> {withRules[lrules, label], e}, 2],
           Dynamic[tab]]];

This is a chain of transformations needed to generate your widget with tab memory:


myTab /. dressTabView[{"Motif" :> motif, "Pattern" :> patt}] /.
    myButton[args__] :> Button[args, ImageSize -> 100] /.
       noimpl[] :> Print[" NOT IMPLEMENTED YET"] /.
          myTabView -> TabView


The main point is, as usual, to separate the specific from the general.


Comments

Post a Comment

Popular posts from this blog

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

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

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