Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
re-init to default not possible when app built
GabbyG
Active Participant
10-24-2001 10:25 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I've been using the invoke node method "re-init to default" quite often throughout the entire project. Now that I have run it through the application builder, it seems, that this feature is not available when "not in edit mode" (error 431).
I would dearly like to use is. Any thoughts, please ?
I would dearly like to use is. Any thoughts, please ?
7.1 -- 2013
CLA
CLA
Dennis_Knutson
Knight of NI
10-24-2001 11:47 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
For the latest on this often discussed topic, see http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000D4020000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0.
Labviewguru
Active Participant
10-24-2001 11:49 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Gabriela,
I would offer the suggestion that using this method may be a bad practice. Relying on the default values is really not a good idea, because those values are otherwise untraceable, and the results can be confusing at best.
Defining a value on the diagram, either as a constant, or as an input to the subVI, is probably the best method I can suggest as an alternative to your desribed method.
I tried looking in the reference property nodes, and could not find a setting for default value. I suppose that this is because NI forsaw the issues that could arise from this. The best thing to do is to declare your defaults explicitly. You never know what can happen otherwise.
Good luck.
Also, please let us know how you solve this issue.
I would offer the suggestion that using this method may be a bad practice. Relying on the default values is really not a good idea, because those values are otherwise untraceable, and the results can be confusing at best.
Defining a value on the diagram, either as a constant, or as an input to the subVI, is probably the best method I can suggest as an alternative to your desribed method.
I tried looking in the reference property nodes, and could not find a setting for default value. I suppose that this is because NI forsaw the issues that could arise from this. The best thing to do is to declare your defaults explicitly. You never know what can happen otherwise.
Good luck.
Also, please let us know how you solve this issue.
10-25-2001 04:53 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi
unlike the "set current to default" I used the "re-init to default" in the run of the program. Mainly to have a solidly working single action push button. When the mechanical action is set to pulsing, I had sometimes problems in loops, maybe due to a double click or what ever. So I prefer to reset the switch as one action of the "true" case.
This can of course be achieved by using a property node and a "write to value".
Other instances were a clean up at leaving or a clean up at entry (like for errors so you are not tripped by an old false display while tracing).
All this can be be done by an explicit setting with a constant.
It's just a pity, that I find out now and have to go through all places.
BTW: I found that a boolean switch with a
puls action (default for OK or reset) has no property to to use. At first this was amazing as well.
Gabriela
unlike the "set current to default" I used the "re-init to default" in the run of the program. Mainly to have a solidly working single action push button. When the mechanical action is set to pulsing, I had sometimes problems in loops, maybe due to a double click or what ever. So I prefer to reset the switch as one action of the "true" case.
This can of course be achieved by using a property node and a "write to value".
Other instances were a clean up at leaving or a clean up at entry (like for errors so you are not tripped by an old false display while tracing).
All this can be be done by an explicit setting with a constant.
It's just a pity, that I find out now and have to go through all places.
BTW: I found that a boolean switch with a
puls action (default for OK or reset) has no property to to use. At first this was amazing as well.
Gabriela
7.1 -- 2013
CLA
CLA
