Xcontrol boolean state default

I have made an XControl. The State ability contains 3 booleans among other values. One of the booleans, the first one I defined, is giving trouble. Even though I set it True, and select "Make current value default" then "Apply Changes" then "Save", I can not get a Property read of the value to return True on the first attempt. Also, program behavior that depends on this value does not properly default. I have also checked that the default value for the "Read" property and the "Write" property that access this value are also set to True. In the Init ability, I also can not get the three states to keep a True value in this item.
Something, somewhere has decided very firmly that the default value for this item must be False, and I cannot get it changed.
Any ideas?
Solved!
Go to Solution.

It's hard for me to reproduce, since I don't have daqmx installed.
Howeve you could try debugging your init ability by placint a break point inside the VI.
And you could inspect the variant from a previous run (if the owning VI is saved) with my Variant XControl.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

Xcontrol always returns default value

I have an Xcontrol that holds an enum in the data in shift register. I have a control on the Xcontrol and that should update the value that will be returned whent the control is read, but the control only ever returns the default value of the enum. I have tried updating the value in the data in shift register, and the data in element of the display state in shift register, and neither works. I can change the Xcontrol using the value propery of a property node. How do I do the same thing with a front panel control of the Xcontrol?

Post your code so we can see what you're doing. We might be able to give some advice then.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

Select boolean State not getting cleared.

Hi ,
I have an a link in my main page say Main.jspx. on clicking the link a popup will get opened say popUp.jspx.
In the popup i have a view object dropped as a table without selection enabled.
i have added three more columns which has select boolean radio component with group condition as below
#{backing_Main.table1.rowIndex}
Suppose i get 50 records in the table and i change the selection state of any of the 50 records and close the popup, the selection state of the radio buttons is not being cleared.
How to clear the selection state when i open the popup again.
Thanks in advance..

Hi!
First, the bindings.Atribute.inputValue should be of type Boolean (not boolean) to render the state of check box correctly by my experience.
Second, all input components bidned to non-attribute (non-writtable) values are automaticalty rendered in read-only mode. The expression #{bindings.Atribute.inputValue==true} is read-only: it is not possible to write changed state of check box into boolean epression.
Regards,
PaKo

How do you transfer different types of data through a data socket (data types: clusters, images and boolean states)

I am attempting to transfer positional data (on a predetermined route) overlaid on a map and indications of boolean output states to secondary computer through datasocket (LabVIEW 8.6, Datasocket 4.5). Is it required to compress all these parts into an array which is bundled and transmitted to the secondary computer which then would have to be unbundled and separated out of the array? Is this the only option, or are there other methods? Also how would we go about these methods?

Hi Maruti,
It seems like the way you described would be the way to do it unless you wanted to pass all the data seperately.
Check out this KB relating to passing clusters through datasocket: http://digital.ni.com/public.nsf/allkb/1085057DB6F930058625672400646805?OpenDocument
Kind Regards,
Owen.S
Applications Engineer
National Instruments

Change Boolean state when switching between cases

I have a case structure with a true and false case. In the false case
I have two boolean I can turn on and off by clicking on them. When
changing to the true case I disabled the two booleans using a property
node. However when switching to the true case the booleans are
disabled and remain in their last state, i.e. if they were true (on) in
the false case, they remain true (on) in the grayed out disabled false
case. How do I change the state of the boolean in addition to
disableing it. i.e. if in the false case the boolean is in the true
state (on) and I switch to another case the booleans are disabled using
the property node and return to the false (off) state? I have attached
a example vi.
Thank you for your help.
Danny
Attachments:
Property node and select function.vi ‏14 KB

Jorge already gave you some useful advice, but I would really recommend that you rethink your approach.
Here are some points:
I am not sure why you place the booleans inside the case structure.
You song and dance is just an "invert" (see picture). Even better leave it all out and swap the contents of the two cases!
There is no reason to constantly spin the loop writing the same properties over and over. It is sufficient to recalculate when one of the controls change. Use an event structure!
You can eliminate the second switch by placing the diagram constants in the two cases.
Attached is a quick draft using events to duplicate your existing functionality. See if it gives you some ideas.
Message Edited by altenbach on 02-03-2008 02:23 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
invert.png ‏3 KB
Property_node_and_select_functionMOD.vi ‏18 KB

Changing boolean state and read change

Hello Everybody,
sorry to bother you, but as a new user of Labview, I still have problems to program VI's. I try to do my best alone, but right now I have been in a dead end for a while... Thats why I come back to you.
Here is my problem:
- in A VI I made, I have a boolean , which command if data are recorded or not. When recording is on, the led enlights, when it is off the led is of.
- Actually, I would like to link the recording action to something more complicated:, I would like the changing state of the boolean to enlights several leds in a specific order.
Thus, when the boolean change, this should change the state of the leds.
I managed to do so, when pressing the button in the boolean_count.VI, that has the result I would like to obtain.
My problem is that, the change of state is not initiated only by a push button. It depends of several state (true or false), which order the recording or not.
To simulate that, I have tried to do same as previously, but with 2 booleans, which have to be both true to initiate a change. I tried to do so in the file Try_out_boolean.VI
But iin this file, when I push my buttons, there is no change of state in the right part of my panel...
I hope You can underrstand what I mean. If you have any suggestions, I will be glad to read them.
Solved!
Go to Solution.
Attachments:
Try_out_boolean.vi ‏15 KB
boolean_count.vi ‏12 KB

in the property node "1and2" of your Try_out_boolean.vi, you read the property "BindingLEDVisible".
(as well as I downloaded) That makes no sense.
-> click with the mouse on this property node an choose the property "Value" instead.
Then your application should react as wanted.
Thre may be other improvements possible, e.g. using event structures instead of continually polling -
but that is another topic...
i hope, this helps a little bit.

How can i test the boolean state of button action?

Hello,
in as2.0, how can i test the boolean value if a button was
pressed or not?
I have a simple function im trying to work with like this...
button_btn.onRelease = function (success:Boolean) {
if (success) {
trace("we pressed the button - value is true");
else {
trace("value is false");
working with booleans in this way is new to me - any pointers
will do - thanks!

Well, I'm not really that familiar with using video in flash,
but from what I understand of what you are going for, these are my
suggestions:
If the code within your button has scope of the variable you
are testing for:
_global.myInfoObject;
button_btn.onRelease = function(){
if( myInfoObject.code == (value your are testing for) ) {
trace("value is correct);
} else {
trace ("value incorrect");
if you aren't in scope you can always maybe forward the
onRelease function to some handler that is in scope:
var myInfoObject;
var release = function(){
//to do code here;
button_btn.onRelease = release;
I hope some of these ideas help a little.
You can always send your .fla to my email at
[email protected] and I'll take a look at it.

Prerequisite boolean statement for SET and its value in ggb1

hi all,
i read in sap help and wonder where and how to create the set and assign the value to it. any advice is appreciated.
thanks
COBL-BLART IN DOCMNT-TYPE OR COBL-WAERS IN CURRENCY
This statement contains two sets: DOCMNT-TYPE and CURRENCY. The set DOCMNT-TYPE contains the values SA and SB; the set CURRENCY contains the currency codes DEM, SFR, LIT, BRF, and HFL. Both sets use dimensions from table COBL.
The combined statement is true if the document type is SA or SB, or the document's currency code is DEM, SFR, LIT, BRF, or HFL.

hi,
sets are created in GS01
hope this helps
ec

Extract "lineageId and Name" from sysssispackages Using XQuery

Hi All,
can someone help me, how to Extract "lineageId and Name" from sysssispackages?
Below query gives me the XML structure of SSIS package but need to pull only those 2 values from that
SELECT
Package= CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML)
FROM [msdb].[dbo].[sysssispackages]
Thanks

Thanks Latheesh for responding
Below is the sample structure
<DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="SSIS.Package.2">
<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>
<DTS:Property DTS:Name="VersionComments" />
<DTS:Property DTS:Name="CreatorName">MyWorld\Sar</DTS:Property>
<DTS:Property DTS:Name="CreatorComputerName">MYWORLD</DTS:Property>
<DTS:Property DTS:Name="CreationDate" DTS:DataType="7">3/22/2014 8:12:40 PM</DTS:Property>
<DTS:Property DTS:Name="PackageType">5</DTS:Property>
<DTS:Property DTS:Name="ProtectionLevel">1</DTS:Property>
<DTS:Property DTS:Name="MaxConcurrentExecutables">-1</DTS:Property>
<DTS:Property DTS:Name="PackagePriorityClass">0</DTS:Property>
<DTS:Property DTS:Name="VersionMajor">1</DTS:Property>
<DTS:Property DTS:Name="VersionMinor">0</DTS:Property>
<DTS:Property DTS:Name="VersionBuild">17</DTS:Property>
<DTS:Property DTS:Name="VersionGUID">{3A8DDC68-97D0-4463-94AB-C9E1EF617E35}</DTS:Property>
<DTS:Property DTS:Name="EnableConfig">0</DTS:Property>
<DTS:Property DTS:Name="CheckpointFileName" />
<DTS:Property DTS:Name="SaveCheckpoints">0</DTS:Property>
<DTS:Property DTS:Name="CheckpointUsage">0</DTS:Property>
<DTS:Property DTS:Name="SuppressConfigurationWarnings">0</DTS:Property>
<DTS:ConnectionManager>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:Property DTS:Name="ObjectName">fftest</DTS:Property>
<DTS:Property DTS:Name="DTSID">{9EE16655-EBB1-4EAB-977A-334CBABE5855}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName">FLATFILE</DTS:Property>
<DTS:ObjectData>
<DTS:ConnectionManager>
<DTS:Property DTS:Name="FileUsageType">0</DTS:Property>
<DTS:Property DTS:Name="Format">Delimited</DTS:Property>
<DTS:Property DTS:Name="LocaleID">1033</DTS:Property>
<DTS:Property DTS:Name="Unicode">0</DTS:Property>
<DTS:Property DTS:Name="HeaderRowsToSkip">0</DTS:Property>
<DTS:Property DTS:Name="HeaderRowDelimiter" xml:space="preserve">_x000D__x000A_</DTS:Property>
<DTS:Property DTS:Name="ColumnNamesInFirstDataRow">-1</DTS:Property>
<DTS:Property DTS:Name="RowDelimiter" xml:space="preserve" />
<DTS:Property DTS:Name="DataRowsToSkip">0</DTS:Property>
<DTS:Property DTS:Name="TextQualifier"><none></DTS:Property>
<DTS:Property DTS:Name="CodePage">1252</DTS:Property>
<DTS:FlatFileColumn>
<DTS:Property DTS:Name="ColumnType">Delimited</DTS:Property>
<DTS:Property DTS:Name="ColumnDelimiter" xml:space="preserve">_x0009_</DTS:Property>
<DTS:Property DTS:Name="ColumnWidth">0</DTS:Property>
<DTS:Property DTS:Name="MaximumWidth">50</DTS:Property>
<DTS:Property DTS:Name="DataType">129</DTS:Property>
<DTS:Property DTS:Name="DataPrecision">0</DTS:Property>
<DTS:Property DTS:Name="DataScale">0</DTS:Property>
<DTS:Property DTS:Name="TextQualified">-1</DTS:Property>
<DTS:Property DTS:Name="ObjectName">ID</DTS:Property>
<DTS:Property DTS:Name="DTSID">{D444A9DE-0FFC-47E9-9747-3A481D7DCEAA}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName" />
</DTS:FlatFileColumn>
<DTS:FlatFileColumn>
<DTS:Property DTS:Name="ColumnType">Delimited</DTS:Property>
<DTS:Property DTS:Name="ColumnDelimiter" xml:space="preserve">_x000D__x000A_</DTS:Property>
<DTS:Property DTS:Name="ColumnWidth">0</DTS:Property>
<DTS:Property DTS:Name="MaximumWidth">50</DTS:Property>
<DTS:Property DTS:Name="DataType">129</DTS:Property>
<DTS:Property DTS:Name="DataPrecision">0</DTS:Property>
<DTS:Property DTS:Name="DataScale">0</DTS:Property>
<DTS:Property DTS:Name="TextQualified">-1</DTS:Property>
<DTS:Property DTS:Name="ObjectName">Name</DTS:Property>
<DTS:Property DTS:Name="DTSID">{9BF026D2-6FD7-4038-93A7-25B1AA4DE092}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName" />
</DTS:FlatFileColumn>
<DTS:Property DTS:Name="ConnectionString">D:\XML Test\test.txt</DTS:Property>
</DTS:ConnectionManager>
</DTS:ObjectData>
</DTS:ConnectionManager>
<DTS:ConnectionManager>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:Property DTS:Name="ObjectName">LocalHost.MyPOCs</DTS:Property>
<DTS:Property DTS:Name="DTSID">{DCE78F76-3B49-4318-993E-13FE9B71E2D5}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName">OLEDB</DTS:Property>
<DTS:ObjectData>
<DTS:ConnectionManager>
<DTS:Property DTS:Name="Retain">0</DTS:Property>
<DTS:Property DTS:Name="ConnectionString">Data Source=.;Initial Catalog=MyPOCs;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-Package-{DCE78F76-3B49-4318-993E-13FE9B71E2D5}LocalHost.MyPOCs;</DTS:Property>
</DTS:ConnectionManager>
</DTS:ObjectData>
</DTS:ConnectionManager>
<DTS:Property DTS:Name="LastModifiedProductVersion">10.0.1600.22</DTS:Property>
<DTS:Property DTS:Name="ForceExecValue">0</DTS:Property>
<DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property>
<DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property>
<DTS:Property DTS:Name="Disabled">0</DTS:Property>
<DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property>
<DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property>
<DTS:Property DTS:Name="LocaleID">1033</DTS:Property>
<DTS:Property DTS:Name="TransactionOption">1</DTS:Property>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:Variable>
<DTS:Property DTS:Name="Expression" />
<DTS:Property DTS:Name="EvaluateAsExpression">0</DTS:Property>
<DTS:Property DTS:Name="Namespace">User</DTS:Property>
<DTS:Property DTS:Name="ReadOnly">0</DTS:Property>
<DTS:Property DTS:Name="RaiseChangedEvent">0</DTS:Property>
<DTS:Property DTS:Name="IncludeInDebugDump">2345</DTS:Property>
<DTS:VariableValue DTS:DataType="8" />
<DTS:Property DTS:Name="ObjectName">Error</DTS:Property>
<DTS:Property DTS:Name="DTSID">{F72B40BF-8B93-429B-8035-96AECD3631A3}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName" />
</DTS:Variable>
<DTS:LoggingOptions>
<DTS:Property DTS:Name="LoggingMode">0</DTS:Property>
<DTS:Property DTS:Name="FilterKind">1</DTS:Property>
<DTS:Property DTS:Name="EventFilter" DTS:DataType="8" />
</DTS:LoggingOptions>
<DTS:Executable DTS:ExecutableType="SSIS.Pipeline.2">
<DTS:Property DTS:Name="ExecutionLocation">0</DTS:Property>
<DTS:Property DTS:Name="ExecutionAddress" />
<DTS:Property DTS:Name="TaskContact">Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server v10; (C) 2007 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1</DTS:Property>
<DTS:Property DTS:Name="ForceExecValue">0</DTS:Property>
<DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property>
<DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property>
<DTS:Property DTS:Name="Disabled">0</DTS:Property>
<DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property>
<DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property>
<DTS:Property DTS:Name="LocaleID">-1</DTS:Property>
<DTS:Property DTS:Name="TransactionOption">1</DTS:Property>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:LoggingOptions>
<DTS:Property DTS:Name="LoggingMode">0</DTS:Property>
<DTS:Property DTS:Name="FilterKind">1</DTS:Property>
<DTS:Property DTS:Name="EventFilter" DTS:DataType="8" />
</DTS:LoggingOptions>
<DTS:Property DTS:Name="ObjectName">Data Flow Task</DTS:Property>
<DTS:Property DTS:Name="DTSID">{9D6476B8-543C-488D-96C2-7C787F892763}</DTS:Property>
<DTS:Property DTS:Name="Description">Data Flow Task</DTS:Property>
<DTS:Property DTS:Name="CreationName">SSIS.Pipeline.2</DTS:Property>
<DTS:Property DTS:Name="DisableEventHandlers">0</DTS:Property>
<DTS:EventHandler>
<DTS:Property DTS:Name="EventID">0</DTS:Property>
<DTS:Property DTS:Name="EventName">OnError</DTS:Property>
<DTS:Property DTS:Name="ForceExecValue">0</DTS:Property>
<DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property>
<DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property>
<DTS:Property DTS:Name="Disabled">0</DTS:Property>
<DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property>
<DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property>
<DTS:Property DTS:Name="LocaleID">-1</DTS:Property>
<DTS:Property DTS:Name="TransactionOption">1</DTS:Property>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:Variable>
<DTS:Property DTS:Name="Expression" />
<DTS:Property DTS:Name="EvaluateAsExpression">0</DTS:Property>
<DTS:Property DTS:Name="Namespace">System</DTS:Property>
<DTS:Property DTS:Name="ReadOnly">0</DTS:Property>
<DTS:Property DTS:Name="RaiseChangedEvent">0</DTS:Property>
<DTS:Property DTS:Name="IncludeInDebugDump">6789</DTS:Property>
<DTS:VariableValue DTS:DataType="11">-1</DTS:VariableValue>
<DTS:Property DTS:Name="ObjectName">Propagate</DTS:Property>
<DTS:Property DTS:Name="DTSID">{C0BBF3C9-2116-4152-AB9E-FF436DA214CB}</DTS:Property>
<DTS:Property DTS:Name="Description">The propagate property of the event</DTS:Property>
<DTS:Property DTS:Name="CreationName" />
</DTS:Variable>
<DTS:LoggingOptions>
<DTS:Property DTS:Name="LoggingMode">0</DTS:Property>
<DTS:Property DTS:Name="FilterKind">1</DTS:Property>
<DTS:Property DTS:Name="EventFilter" DTS:DataType="8" />
</DTS:LoggingOptions>
<DTS:Executable DTS:ExecutableType="Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask.ExecuteSQLTask, Microsoft.SqlServer.SQLTask, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91">
<DTS:Property DTS:Name="ExecutionLocation">0</DTS:Property>
<DTS:Property DTS:Name="ExecutionAddress" />
<DTS:Property DTS:Name="TaskContact">Execute SQL Task; Microsoft Corporation; Microsoft SQL Server 2008; © 2007 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1</DTS:Property>
<DTS:Property DTS:Name="ForceExecValue">0</DTS:Property>
<DTS:Property DTS:Name="ExecValue" DTS:DataType="3">0</DTS:Property>
<DTS:Property DTS:Name="ForceExecutionResult">-1</DTS:Property>
<DTS:Property DTS:Name="Disabled">0</DTS:Property>
<DTS:Property DTS:Name="FailPackageOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="FailParentOnFailure">0</DTS:Property>
<DTS:Property DTS:Name="MaxErrorCount">1</DTS:Property>
<DTS:Property DTS:Name="ISOLevel">1048576</DTS:Property>
<DTS:Property DTS:Name="LocaleID">-1</DTS:Property>
<DTS:Property DTS:Name="TransactionOption">1</DTS:Property>
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:LoggingOptions>
<DTS:Property DTS:Name="LoggingMode">0</DTS:Property>
<DTS:Property DTS:Name="FilterKind">1</DTS:Property>
<DTS:Property DTS:Name="EventFilter" DTS:DataType="8" />
</DTS:LoggingOptions>
<DTS:Property DTS:Name="ObjectName">Execute SQL Task</DTS:Property>
<DTS:Property DTS:Name="DTSID">{380C43D8-73EC-40A9-935B-5CA483E12652}</DTS:Property>
<DTS:Property DTS:Name="Description">Execute SQL Task</DTS:Property>
<DTS:Property DTS:Name="CreationName">Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask.ExecuteSQLTask, Microsoft.SqlServer.SQLTask, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91</DTS:Property>
<DTS:Property DTS:Name="DisableEventHandlers">0</DTS:Property>
<DTS:ObjectData>
<SQLTask:SqlTaskData xmlns:SQLTask="www.microsoft.com/sqlserver/dts/tasks/sqltask" SQLTask:Connection="{DCE78F76-3B49-4318-993E-13FE9B71E2D5}" SQLTask:TimeOut="0" SQLTask:IsStoredProc="False" SQLTask:BypassPrepare="True"
SQLTask:SqlStmtSourceType="DirectInput" SQLTask:SqlStatementSource="Declare @Error Varchar(250) = ?
 
Select @Error as Errodesc" SQLTask:CodePage="1252" SQLTask:ResultType="ResultSetType_SingleRow">
<SQLTask:ResultBinding SQLTask:ResultName="Errodesc" SQLTask:DtsVariableName="User::Error" />
<SQLTask:ParameterBinding SQLTask:ParameterName="@Error" SQLTask:DtsVariableName="System::ErrorDescription" SQLTask:ParameterDirection="Input" SQLTask:DataType="129" SQLTask:ParameterSize="-1" />
</SQLTask:SqlTaskData>
</DTS:ObjectData>
</DTS:Executable>
<DTS:Property DTS:Name="DTSID">{9FF1A2A2-474A-4477-BE6A-6CD9AEEDC0D2}</DTS:Property>
<DTS:Property DTS:Name="Description" />
<DTS:Property DTS:Name="CreationName">OnError</DTS:Property>
</DTS:EventHandler>
<DTS:ObjectData>
<pipeline id="0" name="pipelineXml" description="pipelineXml" defaultBufferMaxRows="10000" engineThreads="10" defaultBufferSize="10485760" BLOBTempStoragePath="" bufferTempStoragePath="" runInOptimizedMode="true">
<components>
<component id="18" name="OLE DB Destination" componentClassID="{5A0B62E8-D91D-49F5-94A5-7BE58DE508F0}" description="OLE DB Destination" localeId="-1" usesDispositions="true" validateExternalMetadata="True" version="4" pipelineVersion="0"
contactInfo="OLE DB Destination;Microsoft Corporation; Microsoft SqlServer v10; (C) Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;4">
<properties>
<property id="19" name="CommandTimeout" dataType="System.Int32" state="default" isArray="false" description="The number of seconds before a command times out. A value of 0 indicates an infinite time-out."
typeConverter="" UITypeEditor="" containsID="false" expressionType="None">0</property>
<property id="20" name="OpenRowset" dataType="System.String" state="default" isArray="false" description="Specifies the name of the database object used to open a rowset." typeConverter="" UITypeEditor=""
containsID="false" expressionType="None">[Datacheck]</property>
<property id="21" name="OpenRowsetVariable" dataType="System.String" state="default" isArray="false" description="Specifies the variable that contains the name of the database object used to open a rowset."
typeConverter="" UITypeEditor="" containsID="false" expressionType="None" />
<property id="22" name="SqlCommand" dataType="System.String" state="default" isArray="false" description="The SQL command to be executed." typeConverter="" UITypeEditor="Microsoft.DataTransformationServices.Controls.ModalMultilineStringEditor,
Microsoft.DataTransformationServices.Controls, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" containsID="false" expressionType="None" />
<property id="23" name="DefaultCodePage" dataType="System.Int32" state="default" isArray="false" description="Specifies the column code page to use when code page information is unavailable from the data source."
typeConverter="" UITypeEditor="" containsID="false" expressionType="None">1252</property>
<property id="24" name="AlwaysUseDefaultCodePage" dataType="System.Boolean" state="default" isArray="false" description="Forces the use of the DefaultCodePage property value when describing character data."
typeConverter="" UITypeEditor="" containsID="false" expressionType="None">false</property>
<property id="25" name="AccessMode" dataType="System.Int32" state="default" isArray="false" description="Specifies the mode used to access the database." typeConverter="AccessMode" UITypeEditor="" containsID="false"
expressionType="None">3</property>
<property id="27" name="FastLoadKeepIdentity" dataType="System.Boolean" state="default" isArray="false" description="Indicates whether the values supplied for identity columns will be copied to the destination.
If false, values for identity columns will be auto-generated at the destination. Applies only if fast load is turned on." typeConverter="" UITypeEditor="" containsID="false" expressionType="None">false</property>
<property id="28" name="FastLoadKeepNulls" dataType="System.Boolean" state="default" isArray="false" description="Indicates whether the columns containing null will have null inserted in the destination. If
false, columns containing null will have their default values inserted at the destination. Applies only if fast load is turned on." typeConverter="" UITypeEditor="" containsID="false" expressionType="None">false</property>
<property id="29" name="FastLoadOptions" dataType="System.String" state="default" isArray="false" description="Specifies options to be used with fast load. Applies only if fast load is turned on." typeConverter=""
UITypeEditor="" containsID="false" expressionType="None">TABLOCK,CHECK_CONSTRAINTS</property>
<property id="30" name="FastLoadMaxInsertCommitSize" dataType="System.Int32" state="default" isArray="false" description="Specifies when commits are issued during data insertion. A value of 0 specifies
that one commit will be issued at the end of data insertion. Applies only if fast load is turned on." typeConverter="" UITypeEditor="" containsID="false" expressionType="None">2147483647</property>
</properties>
<connections>
<connection id="26" name="OleDbConnection" description="The OLE DB runtime connection used to access the database." connectionManagerID="{DCE78F76-3B49-4318-993E-13FE9B71E2D5}" />
</connections>
<inputs>
<input id="31" name="OLE DB Destination Input" description="" hasSideEffects="true" dangling="false" errorOrTruncationOperation="Insert" errorRowDisposition="FailComponent" truncationRowDisposition="NotUsed">
<inputColumns>
<inputColumn id="39" name="" description="" lineageId="121" usageType="readOnly" errorOrTruncationOperation="" errorRowDisposition="NotUsed" truncationRowDisposition="NotUsed" externalMetadataColumnId="37"
mappedColumnId="0" />
<inputColumn id="186" name="" description="" lineageId="181" usageType="readOnly" errorOrTruncationOperation="" errorRowDisposition="NotUsed" truncationRowDisposition="NotUsed" externalMetadataColumnId="36"
mappedColumnId="0" />
</inputColumns>

Responding to Xcontrol State Changes

I would like to use an event handler in the VI containing an XControl to respond to a change to that XControl's state. Is there an easy way to do this without continually polling the XControl's state using a property read and a Create/Generate Event approach?
Thank you!
Brian

Yes, that makes perfectly sense!
I think your question was stated wrong.
But the idea is still the same.
Add to you XControl's state a User event Ref with a string datatype.
Create the user event in the owning application and register a event structure to this user event.
With a custom property (set user event ref) you set the User event Ref in the Xcontrol's state.
If the alarm level is passed you generate a user event inside XControl and the owning VI will be triggered.
I you don't succeed please post an example as complete as can be.
Ton (I have done this several times)
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Break on boolean wire state

This seems basic but I can't find any way to set a breakpoint on a wire that carries a boolean state that stops execution when the state goes to FALSE. Is there any way to do that?
Solved!
Go to Solution.

Put a 'Conditional Probe'.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Show T and F boolean text simultaneously?

I would like to show both True and False boolean text values simultaneously at different locations. Is there any way to do this? I want to use a toggle or rocker switch and be able to see both values at all times.
In an old post Ben and TiTou showed methods to move the text around using property nodes and formating the text with spaces or CR. These only show the selected value, not both.
If the Label, Caption, and Boolean text are all made visible, the effect can be produced. However, this does not allow for programmatic change of all the text, as for language changes, because the label cannot be changed.
For buttons (where the boolean text is usually used) it does not matter, but for rocker and toggle switches this would allow a nicer, more professional GUI. I cannot think of a use case for the transitions texts (T>F and F>T) with these switches, but any option to display the boolean texts simultaneously would have to include those for compatibility.
I have attached a VI which shows the look I would like to achieve.
Lynn
Message Edited by johnsold on 07-03-2008 09:52 AM
Attachments:
Show both boolean text.vi ‏9 KB

Hi Lynn,
I would use a simple text indicator (classic look, set to transparent) to immitate that behaviour. Instead of changing the boolean state texts you simply write to that indicator...
Just a thought: you can create an XControl to hide that functionality from your block diagram
Btw.: Where's your vi? Ok, now it's there...
Message Edited by GerdW on 07-03-2008 03:53 PM
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Error while collecting stale stats dbms_stats

SQL> exec dbms_stats.gather_table_stats('CData3','OM_HEAD',cascade=>'TR
UE',options=>'GATHER STALE');
BEGIN dbms_stats.gather_table_stats('CData3','OM_HEAD',cascade=>'TRUE',
options=>'GATHER STALE'); END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'GATHER_TABLE_STATS'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignoredoracle version 9.2
pls suggest me for the same...
Edited by: user00726 on Feb 3, 2009 4:28 AM

there is no such variable options for gather_table_stats:
PROCEDURE GATHER_TABLE_STATS
Argument Name Type In/Out Default?
OWNNAME VARCHAR2 IN
TABNAME VARCHAR2 IN
PARTNAME VARCHAR2 IN DEFAULT
ESTIMATE_PERCENT NUMBER IN DEFAULT
BLOCK_SAMPLE BOOLEAN IN DEFAULT
METHOD_OPT VARCHAR2 IN DEFAULT
DEGREE NUMBER IN DEFAULT
GRANULARITY VARCHAR2 IN DEFAULT
CASCADE BOOLEAN IN DEFAULT
STATTAB VARCHAR2 IN DEFAULT
STATID VARCHAR2 IN DEFAULT
STATOWN VARCHAR2 IN DEFAULT
NO_INVALIDATE BOOLEAN IN DEFAULT
STATTYPE VARCHAR2 IN DEFAULT
FORCE BOOLEAN IN DEFAULT
So you can't use such variable.
Use instead gather_schema_stats with such option, it will automaticaly gather stats for all tables with stale_stats in that schema.
Or You can look into table:
dba_tab_modifications
And from there find which tables are having stale stats and gather with gather_table_stats.
Edited by: Laura Gaigala on Feb 3, 2009 2:53 PM
Edited by: Laura Gaigala on Feb 3, 2009 2:54 PM

Xcontrol: performance question (again)

Hello,
I've got a little performance question regarding xcontrols. I observed rather high cpu-load when using xcontrols. To investigate it further, I built a minimal xcontrol (boolean type) which only writes the received boolean-value to a display-element in it's facade (see attached example). When I use this xcontrol in a test-vi and write to it with a rate of 1000 booleans / second, I get a cpu-load of about 10%. When I write directly to a boolean display element instead of the xcontrol,I have a load of 0 to 1 %. The funny thing is, when I emulate the xcontrol functionality with a subvi, a subpanel and a queue (see example), I only have 0 to 1% cpu-load, too.
Is there a way to reduce the cpu-load when using xcontrols?
If there isn't and if this is not a problem with my installation but a known issue, I think this would be a potential point for NI to fix in a future update of LV.
Regards,
soranito
Message Edited by soranito on 04-04-2010 08:16 PM
Message Edited by soranito on 04-04-2010 08:18 PM
Attachments:
XControl_performance_test.zip ‏60 KB

soranito wrote:
Hello,
I've got a little performance question regarding xcontrols. I observed rather high cpu-load when using xcontrols. To investigate it further, I built a minimal xcontrol (boolean type) which only writes the received boolean-value to a display-element in it's facade (see attached example). When I use this xcontrol in a test-vi and write to it with a rate of 1000 booleans / second, I get a cpu-load of about 10%. When I write directly to a boolean display element instead of the xcontrol,I have a load of 0 to 1 %. The funny thing is, when I emulate the xcontrol functionality with a subvi, a subpanel and a queue (see example), I only have 0 to 1% cpu-load, too.
Okay, I think I understand question now. You want to know why an equivalent xcontrol boolean consumes 10x more CPU resource than the LV base package boolean?
Okay, try opening the project I replied yesterday. I don't have access to LV at my desk so let's try this. Open up your xcontrol facade.vi. Notice how I separated up your data event into two events? Go the data change vi event, when looping back the action, set the isDataChanged (part of the data change cluster) to FALSE. While the data input (the one displayed on your facade.vi front panel), set that isDataChanged to TRUE. This is will limit the number of times facade will be looping. It will not drop your CPU down from 10% to 0% but it should drop a little, just enough to give you a short term solution. If that doesn't work, just play around with the loopback statement. I can't remember the exact method.
Yeah, I agree xcontrol shouldn't be overconsuming system resource. I think xcontrol is still in its primitive form and I'm not sure if NI is planning on investing more times to bug fix or even enhance it. Imo, I don't think xcontrol is quite ready for primetime yet. Just too many issues that need improvement.
Message Edited by lavalava on 04-06-2010 03:34 PM

XControl (question sur l'initialisation)

Bonjour à tous,
Un XControl (indicateur).
Quand je le place sur le FP ... il se positionne comme un "controle" ... et apparait aussi comme tel sur le BD.
Cela fait 2hrs que je retourne ce pb dans tous les sens.
Le VI "init", le "container state", le code dans Facade/display state change ... rien n'y fait.
Existe-t-il un moyen, quand je place mon XControl sur le FP, qu'il se positionne directement en "indicateur" (??)
merci à tous.

Désolé de ne pas avoir répondu plus rapidement. Votre réponse est "dense" et demandait du temps pour y répondre,
ce que je n'avais pas dans l'immédiat.
Bon.
"Ou avez vous lu ça ? Dans les commentaires du VI sur l'évènement dans la structure ?" ... oui.
Quand je crée un nouveau XControl ... New Project / My Computer (clic-droit) / New / XControl
LavVIEW me "donne" un XControl type de "départ".
Première point : Dans le FP de "init", je n'ai pas le "flag" dont vous parlez.
J'ai : Previous Version, Previous State, Current State, Container State, Default Indicator State, Default Control State ... mais aucun "flag".
deuxième point :
voici ce que je lis en commentaires, dans le BD de "facade", pour les events "Display State Change" et "Direction Change"
Moi j'ai ça pour Événement Changement de l'état d'affichage (dans le documentation de LabVIEW) :
"Généré sur le VI Façade si l'état d'affichage de la commandeX change suite à l'invocation par l'utilisateur d'une propriété ou d'une méthode sur la commandeX.."
Changement de l'état d'affichage == Display State Change
et pour "Display State Change", moi j'ai ceci (comme sur l'image ci-dessus)
Display State changed as a result of dropping a new instance of this XControl, copying,
undoing an operation or executing a custom property or method on this XControl. Update the appearance accordingly.
On parle "comme pour vous" de "l'invocation par l'utilisateur d'une propriété ou d'une méthode",
mais, de mon côté, on parle en plus de "a result of dropping a new instance of this XControl".
Pour Événement Changement de direction (dans le documentation de LabVIEW) :
"Généré sur le VI Façade lorsque la direction de la commandeX passe de commande à indicateur ou vice versa."
Changement de direction == Direction Change
et pour "Direction Change", j'ai : "The direction of the XControl changed from a control to an indicator or vice versa."
Ce qui est, dans ce cas, la même chose que pour vous.
Donc, petit bilan ...
Concernant le fait de "placer une instance du XControl" sur le FP,
pour moi : cela est géré par l'event "Display Stage Change" .... (dropping a new instance ...)
pour vous: on n'en parle pas ... ni pour un événement, ni pour l'autre.
pour wiki : wiki parle que le "drop" est géré par l'event "Direction Change" ... (soit l'inverse de chez moi)
               Ceci dit (en passant) ... wiki dit que le "load into memory" est géré aussi bien par l'un et par l'autre (??)
               Oui, cela n'a rien avoir ... juste une incohérence qui me fait douter du reste.
               wiki est aussi le seul a parler du drop initial (le 1er ?)
Et si on plaçait un "Breakpoint" dans chaque Event pour "voir" qui intercepte le drop ?
un seul ? les deux ? ... et si "les deux", dans quel ordre ?
Voici le résultat pour un "drop", les 2 events sont sollicités : (multiple tests, résultats identiques)
1er arrêt : Direction Change
2eme arrêt : Display State Change
Il serait donc possible de "réagir" à un drop aussi bien dans un event que dans l'autre.
Mais j'ai remarqué une grosse différence ... voici le code que j'utilise pour placer mon XControl en Indicateur lors du drop.
(oui, la structure condition est inutile ... petit purisme de ma part)
Si je place ce code dans "Display State Change"
1) mon XControl se positionne bien en Indicateur lors du drop
2) une fois placé comme indicateur, je peux toujours (par la suite) le faire basculer en Controle, et vis versa.
Si je place ce code dans "Direction Change"
1) mon XControl se positionne bien en Indicateur lors du drop
2) il est verouillé ! plus moyen de le changer en Controle (normal, tous changements fait l'objet d'un "reset" en position indicateur)
L'un et l'autre fonctionne, mais le résultat final est différent.
et pour terminer, un dernier mot sur ce "Flag" (inexistant chez moi lors de la création d'un nouveau XControl)
Le sous VI "Led-Ctrl2Ind" met le flag à 1 une fois que le XControl a été déposé sur la face-avant ...
Je ne vois franchement pas à quoi sert cette mise à "1" de ce Flag ... que je n'ai pas chez moi. (LV 2011)
Ceci dit, le canard est toujours vivant, car on ne sait toujours pas entre "Direction Change" et "Display State Change"
lequel des deux est spécialement dédié à la gestion d'un drop.

Xcontrol boolean state default

Similar Messages

Maybe you are looking for