1
Feature Request / Re: BasicLabel Blink
« on: March 19, 2019, 02:38:34 PM »
I understand completely. Thanks for the response.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Feature Request / Re: BasicLabel Blink
« on: March 19, 2019, 02:06:41 PM »
I think you misunderstood Enable/Disable. I was talking about the text that is displayed when the value is Boolean (like On/Off, True/False, Yes/No, etc.)
I have modified the BasicLabel to meet the request. I was hoping that the modifications would become part of the standard build so that I would not have to replace the standard with my modified one each time a new version is released.
I have attached my version here.
Side Note: The "Blink" is not controlled by a PLC address. I set the Highlight character to nothing to start the blinking and then use the PLCAddressVisible to show/hide text that needs to catch the operator's eye. Also, I'm not 100% sure about the new PLCAddressValueToSubtractFrom property. I do not currently have a PLC that is not in production to test it with.
I have modified the BasicLabel to meet the request. I was hoping that the modifications would become part of the standard build so that I would not have to replace the standard with my modified one each time a new version is released.
I have attached my version here.
Side Note: The "Blink" is not controlled by a PLC address. I set the Highlight character to nothing to start the blinking and then use the PLCAddressVisible to show/hide text that needs to catch the operator's eye. Also, I'm not 100% sure about the new PLCAddressValueToSubtractFrom property. I do not currently have a PLC that is not in production to test it with.
3
Feature Request / BasicLabel Blink
« on: March 18, 2019, 11:53:13 AM »
I have three suggestions for the basic label.
1. It would be nice if the label "Blinked" between the highlighted color and the normal color by setting a blink rate. If the "Blink" rate was set to 0 then blinking would be disabled.
2. Have the "ValueToSubtractFrom" property be a value that can be read from the PLC. This would allow you to display a time remaining (Timer.PRE - Timer.ACC). You would also need to have the "ValueScaleFactor" affect the "ValueToSubtractFrom".
3. Add Auto/Manual and Enabled/Disabled to the Boolean text choices.
1. It would be nice if the label "Blinked" between the highlighted color and the normal color by setting a blink rate. If the "Blink" rate was set to 0 then blinking would be disabled.
2. Have the "ValueToSubtractFrom" property be a value that can be read from the PLC. This would allow you to display a time remaining (Timer.PRE - Timer.ACC). You would also need to have the "ValueScaleFactor" affect the "ValueToSubtractFrom".
3. Add Auto/Manual and Enabled/Disabled to the Boolean text choices.
4
Support Questions / BasicLabel Keypad Show Value
« on: August 24, 2016, 12:22:03 PM »
I am using the BasicLabel to allow the operator to change timer values. The scale factor is set to .001 in order to display the timer value in seconds. If I set the property "KeypadShowCurrentValue" to true, the value that is read from the PLC and displayed on the keypad is not scaled.
For example: If the timer is set for 10 seconds the value displayed on the keypad will be 10000. Changing it to 10 and saving the result works correctly; the value saved back to the PLC is 10000.
I am currently looking at version 3.99n but I checked an older version (3.99d) and it does the same thing.
For example: If the timer is set for 10 seconds the value displayed on the keypad will be 10000. Changing it to 10 and saving the result works correctly; the value saved back to the PLC is 10000.
I am currently looking at version 3.99n but I checked an older version (3.99d) and it does the same thing.
5
Open Discussion / EthernetIPforCLXCom1.ComError
« on: August 22, 2016, 09:56:06 AM »
When EthernetIPforCLXCom1.ComError is triggered does EthernetIPforCLXCom1.ConnectionEstablished trigger when communication is reestablished?
6
Open Discussion / Trailing space in PLC address
« on: August 16, 2016, 04:21:30 PM »
I discovered a problem, created by the developer, which is caused an invalid tag error.
During the process of building the HMI screens, I was copying the tag names from an old system and pasting them into the new. Some of the tags ended up with a trailing space. This caused a failure to read tag error. I did a quick fix by modifying the controls I was using (modified control's properties by adding X = Value.Trim). This was faster than going through each screen control and looking for and removing the trailing space.
It would be a nice addition if this fix was added to future releases to prevent development error caused by unawareness.
During the process of building the HMI screens, I was copying the tag names from an old system and pasting them into the new. Some of the tags ended up with a trailing space. This caused a failure to read tag error. I did a quick fix by modifying the controls I was using (modified control's properties by adding X = Value.Trim). This was faster than going through each screen control and looking for and removing the trailing space.
It would be a nice addition if this fix was added to future releases to prevent development error caused by unawareness.
7
Additional Components / Re: Alphanumeric Keypad
« on: August 16, 2016, 12:40:54 PM »
I like your on screen keyboard, although I am not sure why you added the Public Event ButtonClick. I added upper/lower characters and special characters so that I could use it for passwords.
8
Support Questions / Re: Main container and sub-forms
« on: July 20, 2016, 04:15:40 PM »
You can create a MDI form by creating a Form (in this example named MDIForm1) and setting it's IsMdiContainer property to true
You can make child forms by:
1.) Setting the ControlBox property of the Form to false
2.) Adding the following into the "Child form's" designer.vb
<System.Diagnostics.DebuggerNonUserCode()> Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'This form is an MDI child.
'This code simulates the VB6 functionality of automatically
'loading and showing an MDI child's parent.
Me.MdiParent = MDIForm1
End Sub
3.) Add the following to the Form's Load event
Me.Visible = True
Me.Opacity = 0
Me.WindowState = FormWindowState.Maximized
Me.Opacity = 1
Sample project attached.
You can make child forms by:
1.) Setting the ControlBox property of the Form to false
2.) Adding the following into the "Child form's" designer.vb
<System.Diagnostics.DebuggerNonUserCode()> Public Sub New()
MyBase.New()
'This call is required by the Windows Form Designer.
InitializeComponent()
'This form is an MDI child.
'This code simulates the VB6 functionality of automatically
'loading and showing an MDI child's parent.
Me.MdiParent = MDIForm1
End Sub
3.) Add the following to the Form's Load event
Me.Visible = True
Me.Opacity = 0
Me.WindowState = FormWindowState.Maximized
Me.Opacity = 1
Sample project attached.
9
Support Questions / Re: MessageDisplayByValue Returned Value
« on: June 30, 2016, 04:00:20 PM »
Sorry, I never thought about using the ValueChangedEventArgs in the ValueChanged event to get the value.
10
Support Questions / Re: MultiStateSelector V3.99j
« on: June 30, 2016, 01:46:34 PM »
It was my problem. I restarted the application and the problem went away.
11
Support Questions / MessageDisplayByValue Returned Value
« on: June 30, 2016, 01:25:26 PM »
This maybe by design but is was unexpected.
If you read the returned value (MessageDisplayByValue.Value) from ValueChanged event, the value that is returned is the value you are changing from (old value).
If you read the returned value from TextChanged event, the value that is returned is the value you are changing to (new value).
If you read the returned value (MessageDisplayByValue.Value) from ValueChanged event, the value that is returned is the value you are changing from (old value).
If you read the returned value from TextChanged event, the value that is returned is the value you are changing to (new value).
12
Feature Request / Re: BasicLabel Highlight forecolor
« on: June 21, 2016, 11:38:01 AM »
Thanks for the quick update.
Two minor observations:
1. The Prefix/Suffix do not work when "Display as time" is selected.
2. Format(Math.Floor(Minutes), "00")) would have been better as Math.Floor(Minutes).ToString("00"). This eliminates the need for the Microsoft.Visualbasic reference.
Two minor observations:
1. The Prefix/Suffix do not work when "Display as time" is selected.
2. Format(Math.Floor(Minutes), "00")) would have been better as Math.Floor(Minutes).ToString("00"). This eliminates the need for the Microsoft.Visualbasic reference.
13
Feature Request / BasicLabel Highlight forecolor
« on: June 20, 2016, 09:36:43 AM »
In future releases to would be nice if a Highlight forecolor property were included. Also, it would be nice if the Highlighting worked for boolean values also.
14
Support Questions / MultiStateSelector V3.99j
« on: June 17, 2016, 03:09:23 PM »
The MultiStateSelector control has a bug.
When you click on the "States" property to add to the collection the control displays an error "Parameter not valid".
When you click on the "States" property to add to the collection the control displays an error "Parameter not valid".
15
Feature Request / Re: GraphicIndicator image rotation
« on: June 15, 2016, 09:09:00 AM »
The GraphicIndicatorRotate control was not created for animation (see the first post). There already is a standard control that does animation (AnimatingPictureBox) although I have not used it.