Your comments

Ok, something like this?


The trick I have used for this is to build it up with two bargraphs, one for the positive direction, and one for the negagative direction. Here, the range of each bargraph is positive or negative, and the colors are inverted.



Here is an example file for this:
MD4 joystick XY bargraph.ids3


About the MD4 demo pages in the previous post, they install with IQANdesign. I just posted a news topic on them, here:
http://forum.iqan.se/topic/759905-new-iqan-md4-demo-pages/
Hi Zach,

What do you mean by bilinear bars? Is it the image bar-graph from MDL2/MD3 you mean?



With the MD4 supporting PNG transparancy, the best way to implement this on an MD4 is to use a bar graph in combination with a PNG image of the frame, that is transparent where the bar graph is showing.


A really nice example of how this is in the example files, where an entire background page with transparent cutouts is placed in front of the bargraphs.


With background hidden:




I must admit that I have never used the feature to be able to change the background color in IQANrun.
But there seems to be a problem with it, just as you describe.

I can get it to work if I have the measurement running while changing the background color, and just press Apply. But as soon as OK is pressed, the line and grid colors change.

It works differently on MD4 compared to the DCC channels for MD3/MDL2.
On the MD4, there is one property in the display page properties for controlling the backlight.



Your question came in as a helpdesk case. Do you mind if I publish this in the public section for questions?
Hi Nick,

For the font, what you can do today is to change the font in the language settings. (not sure the example I show here makes it more readable though.. )

Changing this font property affects the entire project file, both menu system and display pages.

For the font size and theme colors, the properties for this currently only affect the display pages, and not the built-in menu system.


If you send out TSC1 with the same priority and source address, you will undoubtedly get a CAN arbitration error. One of the CAN controllers will quickly go into bus-off, and that MD3 will show a CAN error.

If you send TSC1 with different priority and same source address, then CAN in itself will not be the reason for failure. But the engine would receive conflicting messages from what it would believe is the same controller.

If you send TSC1 from different source addresses, then it depends on the engine which source address it is that will win, if it does not see this as an error. Most engines only accept TSC1 from a few limited source addresses.

Obviously, if your add-on goes in and overrides the original system, then the machine may not work as designed.
What I suggest you do is to speak to the OEM about this modification, we should be able to provide you with a contact person.
Hi Zach,

I am not sure that I understand what the error is?
I made a quick test with four text labels, the top one at 100 pixels from top, and the bottom one at 400 pixels from the top.

Before pressing Distribute controls vertically:



Just after pressing Distribute controls vertically:

The Distribute controls vertically has moved the middle objects, they are now at 200 and 300 pixels from the top.

Only the middle objects are highlighted after the operation, these are the ones that are moved.


Thanks for pointing this out, I checked and the same problem exists in 3.17.