Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
interaction:axure_ideas [2015/08/05 15:48]
sam
interaction:axure_ideas [2018/09/24 13:47] (current)
Line 76: Line 76:
   * $axure('​@Page >> @*'); // %%//%% Finds all widgets with an owner (the page or master a widget is placed on) called '​Page'​. //   * $axure('​@Page >> @*'); // %%//%% Finds all widgets with an owner (the page or master a widget is placed on) called '​Page'​. //
   * $axure('​@First,​ @Second, #​Thrid'​);​ // %%//%% Finds multiple widgets with specific names or ids. //   * $axure('​@First,​ @Second, #​Thrid'​);​ // %%//%% Finds multiple widgets with specific names or ids. //
 +
 +=== Workaround ===
 +
 +A workaround is to use the AxureEx functions **childOf**,​ **parentOf** and **labelContains**. See [[axure.ex_api]].
  
 ---- ----
Line 87: Line 91:
  
 Make it so that interaction styles such as MouseDown, MouseOver can be specified in custom widget styles. A widget that is assigned a custom widget style where interaction styles are specified use these interaction styles. Make it so that interaction styles such as MouseDown, MouseOver can be specified in custom widget styles. A widget that is assigned a custom widget style where interaction styles are specified use these interaction styles.
 +
 +=== Workaround ===
 +
 +A workaround is to use the Axure function **css** and change the appearance of widget with javascript. See [[axure_api]].
 +
  
 ---- ----
Line 98: Line 107:
  
 A custom widget style can specify panel formatting. When such a style is assigned to a widget, this formatting then applies to all panel states of the widget. A custom widget style can specify panel formatting. When such a style is assigned to a widget, this formatting then applies to all panel states of the widget.
 +
 +=== Workaround ===
 +
 +A workaround is to use the Axure function **css** and change the appearance of widget with javascript. See [[axure_api]].
 +
  
 ---- ----
Line 110: Line 124:
 Show the context in which a master or dynamic panel is used as a "​background"​ image, when a master or dynamic panel is edited. A master can be used in multiple contexts, so the master must be opened from the context that should be showed in the background. Show the context in which a master or dynamic panel is used as a "​background"​ image, when a master or dynamic panel is edited. A master can be used in multiple contexts, so the master must be opened from the context that should be showed in the background.
  
----- +Editing a master or dynamic panel state in context would work much the same way group editing is done in Axure 8. **In Axure 9 dynamic panels can be edited inline :) **
-====== Masters ​in repeaters ======+
  
-=== Problem === 
- 
-If a repeater uses a master and the OnItemLoad event on the repeater change widgets in the master. It is not rendered correctly in Axure. Currently it only works when viewed in a browser. 
- 
-=== Solution === 
- 
-Fix the bug. 
  
 ---- ----
Line 138: Line 144:
     * Widget C     * Widget C
     * Widget D     * Widget D
 +
 +**This feature is implemented in Axure 8 :) **
  
 ---- ----
Line 232: Line 240:
  
 All widgets should have a "​ignore mouse events"​ property. Modern browsers support this in as a style. All widgets should have a "​ignore mouse events"​ property. Modern browsers support this in as a style.
 +
 +=== Workaround ===
 +
 +Use a group and use the events on the group. This is a workaround in some of the situations where "​ignore mouse events"​ is needed.
  
 ---- ----
Line 251: Line 263:
   OnClick: Set "​Property A" on "​Master A"   OnClick: Set "​Property A" on "​Master A"
 </​code>​ </​code>​
 +
 +**In Axure 9 simple components can be create :) **
  
 ---- ----
Line 289: Line 303:
  
 This requires a "Add function"​ function on widgets, pages and masters and a "​Invoke function"​ in actions. This requires a "Add function"​ function on widgets, pages and masters and a "​Invoke function"​ in actions.
 +
 +=== Workaround ===
 +
 +In Axure 8 custom events on masters can be fired from actions. Use this workaround to define functions. Or use AxureEx to define real custom functions, that can be called from any expression in an action. See [[axure.ex_api]]. ​
  
 ---- ----
Line 318: Line 336:
  
 In the "​Update"​ action there should be a "[X] Refresh repeater items" checkbox. In the "​Update"​ action there should be a "[X] Refresh repeater items" checkbox.
 +
 +=== Workaround ===
 +
 +Use AxureEx to update repeaters without refreshing the repeater. See [[http://​b2grli.axshare.com/#​g=1&​p=repeater_a]].
 +
  
 ---- ----
Line 331: Line 354:
  
 The values of global variables are "​lost"​ when the user go back in browser history. It would be great to have persistent variables. These could be stored in local storage, in cookies or on a server. The values of global variables are "​lost"​ when the user go back in browser history. It would be great to have persistent variables. These could be stored in local storage, in cookies or on a server.
 +
 +=== Workaround ===
 +
 +Use AxureEx to store data in session or local storage. Use AxureEx to load and save repeater data to local or session storage. See [[http://​b2grli.axshare.com/#​g=1&​p=repeater_a]].
 +
  
 ---- ----
Line 342: Line 370:
  
 Datasets for repeaters can be shared between different repeaters. This would require that a repater can be set to "​inherit"​ its dataset from another repeater widget, or that repeater datasets and repeater widgets are decoupled. Datasets for repeaters can be shared between different repeaters. This would require that a repater can be set to "​inherit"​ its dataset from another repeater widget, or that repeater datasets and repeater widgets are decoupled.
 +
 +=== Workaround ===
 +
 +Use AxureEx to load and save repeater data to local or session storage. See [[http://​b2grli.axshare.com/#​g=1&​p=repeater_a]].
  
 ---- ----
Line 375: Line 407:
  
 Add a "[ ] Local" check box to each global variable. If it is checked the value of the variable is "​forgotten"​ each time you go to a new page. Add a "[ ] Local" check box to each global variable. If it is checked the value of the variable is "​forgotten"​ each time you go to a new page.
 +
 +=== Workaround ===
 +
 +Write you actions in javascript :) [[http://​b2grli.axshare.com/#​g=1&​p=javascript]].
 +