02-17-2016 01:05 PM
02-17-2016 03:17 PM - edited 02-17-2016 03:24 PM
Wow! Really good.
Didn't know it was possible to dig this deep inside the object.
But then on the other hand, I am wondering, if it has all these properties, including Orientation, then why aren't they simply accessible from the included VIs.
Thanks a lot!
02-17-2016 06:20 PM
Vaibhav a écrit :.
But then on the other hand, I am wondering, if it has all these properties, including Orientation, then why aren't they simply accessible from the included VIs.
There are too many different graph objects and properties. Some of these properties also do not apply to all graph types. But in this case I think axis title orientation would be a grat addition.
Ben64
02-18-2016 04:46 AM
Ok.
Analysing your blockdiagram raised a few questions in my mind.
Why are OLE objects' indices a +1 than the actual index of the object (they start from 1 instead of from 0?).
Why is the index not a number but a variant? Indices are always numbers, no?
And after you have selected the object property, how come it became chart? In the beginning you are just selecting Shapes. And it could be some figures (square, round etc.) and not only a chart.
I don't know if my questions make sense. The usage of application property nodes seems to be very empowering.
02-18-2016 08:24 AM
@Vaibhav wrote:Ok.
Analysing your blockdiagram raised a few questions in my mind.
Why are OLE objects' indices a +1 than the actual index of the object (they start from 1 instead of from 0?).
Yes, they start from 1
Why is the index not a number but a variant? Indices are always numbers, no?
No, for some object, like worksheet, it can be the name of the object.
And after you have selected the object property, how come it became chart? In the beginning you are just selecting Shapes. And it could be some figures (square, round etc.) and not only a chart.
I recreated the input of the RGT vis. If you don't wire the index input it uses the default value of -1. When index is set to -1 the OLEObjects index used is the shape count. Since the graph was just created the shape count is the index of the graph just created.
I don't know if my questions make sense. The usage of application property nodes seems to be very empowering.
Ben64
03-03-2016 01:11 PM
@ben64 wrote:Use this vi. Set the axis type to xlValue and the orientation to xlUpward.
Ben64
Thanks for that VI.
I was able to play with it to change the major unit for the Y scale, but I am trying to change the major unit for the X axis scale. How would I choose the X axis to modify it?
I am guessing it has to do with where you choose the Excel.Axes class. I will look at that more after lunch, but figured I would ask.
03-03-2016 02:02 PM
@_Bryan wrote:
@ben64 wrote:Use this vi. Set the axis type to xlValue and the orientation to xlUpward.
Ben64
Thanks for that VI.
I was able to play with it to change the major unit for the Y scale, but I am trying to change the major unit for the X axis scale. How would I choose the X axis to modify it?
I am guessing it has to do with where you choose the Excel.Axes class. I will look at that more after lunch, but figured I would ask.
Set Axis type to xlCategory to change the x-axis
Ben64
03-03-2016 02:40 PM
@ben64 wrote:Set Axis type to xlCategory to change the x-axis
Ben64
I tried that before and I get an unknown error. In this snippet if you set the axis to XlValue it will modify the Y major value, but the xlCategory throws an unknown error. I have noticed that if I even look at the screen wrong the report generation toolkit will throw an unknown error. So I assume it wants another piece of info somewhere.
03-03-2016 02:49 PM
03-03-2016 02:54 PM
Sorry. Here you go.