Skip to main content

gui construction - Problems with visual update in GUI


Consider the following. When clicking in "Browse" and then choosing a file, the path will remain the original one and won't change to the one of the file I chose:


nb = EvaluationNotebook[];

DynamicModule[
 {path1 = FileNameJoin[{$HomeDirectory, "Desktop", "file.nb"}],
  path2 = FileNameJoin[{$HomeDirectory, "Desktop", "file.xls"}]}, 

 CreateDialog[
  Column[{Row[{InputField[Dynamic[path1], String, Enabled -> False], 
      FileNameSetter[Dynamic[path1], 
       "Open", {"Mathematica Notebook" -> {"*.nb"}}]}], 
    Row[{InputField[Dynamic[path2], String, Enabled -> False], 
      FileNameSetter[Dynamic[path2], 
       "Open", {"Excel files" -> {"*.xls", "*.xlsx"}}]}]}], 
  NotebookEventActions :> {"WindowClose" :> (SetOptions[nb, 
       Visible -> True])}]
]


Answer



The behaviour is indeed inconsistent: CreateDialog uses the option WindowSize -> All, where All (god knows why) causes the unexpected behaviour with dynamic content. See resolution of the problem at the end of the post.


The following even more simple example clearly shows that something fishy is going on: only path2 can be set via the second button but not path1:


DynamicModule[{path1 = "path #1", path2 = "path #2"},
  CreateDialog@Grid@{
     {FileNameSetter[Dynamic@path1, 
       "Open", {"Mathematica Notebook" -> {"*.nb"}}], Dynamic@path1},
     {FileNameSetter[Dynamic@path2, 
       "Open", {"Excel files" -> {"*.xls", "*.xlsx"}}], Dynamic@path2}
     }];


Removing the CreateDialog wrapper causes both FileNameSetters to work as expected, which indicates that it is the special context of the dialog window that causes the erroneous behaviour. Since CreateDialog[expr] is just a specialized CreateWindow[DocumentNotebook[expr]], we have to look at the options CreateDialog uses as defaults for its internal CreateWindow. As it turns out, the blame lies with WindowSize. Compare the behavior of the following two examples where only the value of WindowSize differs.


This is faulty:


DynamicModule[{path1 = "path #1", path2 = "path #2"},
 CreateWindow[DocumentNotebook@Grid@{
     {FileNameSetter[Dynamic@path1, 
       "Open", {"Mathematica Notebook" -> {"*.nb"}}], Dynamic@path1},
     {FileNameSetter[Dynamic@path2, 
       "Open", {"Excel files" -> {"*.xls", "*.xlsx"}}], Dynamic@path2}
     }, WindowSize -> All]]


This works as expected:


DynamicModule[{path1 = "path #1", path2 = "path #2"},
 CreateWindow[DocumentNotebook@Grid@{
     {FileNameSetter[Dynamic@path1, 
       "Open", {"Mathematica Notebook" -> {"*.nb"}}], Dynamic@path1},
     {FileNameSetter[Dynamic@path2, 
       "Open", {"Excel files" -> {"*.xls", "*.xlsx"}}], Dynamic@path2}
     }, WindowSize -> {200, 200}]]


And then I remembered: Strange behavior of CreateDialog in (Dynamic)Module


The options for CreateWindow (to make it look like it is a dialog) are:


{WindowSize -> {200, 200}, Deployed -> True, ShowCellBracket -> False,
 WindowFloating -> False, StyleDefinitions -> "Dialog.nb",
 WindowFrame -> "ModelessDialog"}

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

How to remap graph properties?

Graph objects support both custom properties, which do not have special meanings, and standard properties, which may be used by some functions. When importing from formats such as GraphML, we usually get a result with custom properties. What is the simplest way to remap one property to another, e.g. to remap a custom property to a standard one so it can be used with various functions? Example: Let's get Zachary's karate club network with edge weights and vertex names from here: http://nexus.igraph.org/api/dataset_info?id=1&format=html g = Import[ "http://nexus.igraph.org/api/dataset?id=1&format=GraphML", {"ZIP", "karate.GraphML"}] I can remap "name" to VertexLabels and "weights" to EdgeWeight like this: sp[prop_][g_] := SetProperty[g, prop] g2 = g // sp[EdgeWeight -> (PropertyValue[{g, #}, "weight"] & /@ EdgeList[g])] // sp[VertexLabels -> (# -> PropertyValue[{g, #}, "name"]...
Post a Comment
Read more