Digital Workshop

Hi

I am trying to create a bar graph for a publication to display 6 score results
(5 items plus their overall average) using vertical color bars.

The actual score results are in percents to several decimal points and would be rounded to the nearest whole percent. The bars, in order to accurately display results, need to be in 1% increments, 1-100.

Any ideas would be appreciated.

Kind Regards,

Stephen,

Take a look at the attached it is not pixel perfect just a quick mock up of one way this could be done.

Enter a % result between 0 and 100
Opus then multiplies the result by 5, as the frame is 500 pixels.
Opus doubles the result as I have used the scale option which scales in both ways, you only see scale one way as the frame covers half of it.

Hope this helps

Brenden Knifton

Thanks Brenden

This looks quite promising!

I appreciate your help.

Kind Regards,

Stephen,

I did something similar a few years ago, but used a slightly different method. I created a frame that was a little longer than the graph's maximum. I put that frame inside of another and set its initial position at the edge of the outer frame. As a variable changed, the inner frame moved accordingly. I looked like it was growing out of the side of the outer frame.

Sorry for the sketchy description, but it has been awhile since i did this and the exact details are a bit fuzzy.

Good luck.

Thanks Tom for the additional ideas.

Kind Regards,

Hi

I wonder if someone else can take a look at the bar graph sample file that Brenden attached above as a download.

Since the sample file worked fine in the Opus editor preview mode, I never thought to try publishing it to see if it also worked in runtime.

So, instead, I began adapting the bar graph to a project I am working on. When I published the new project including the adapted bar graph, this bar graph which displayed perfectly in editor preview, would not display in runtime.

So, I went back to the original sample (downloaded from the zip attachment above). Publishing it, it also failed to display in runtime. Even re-downloaded the original with no better success in runtime.

I would appreciate if someone can take a look at the original sample above and see if this display problem happens for them or it's something else. I checked my drivers, which are up to date, did a diagnostic on DirectX, which is OK, cleared the Opus registry in case keys were corrupted (ctrl + alt upon booting up the program), even did a repair in the add/remove. My version, XE 5.5, is up to date, including service releases.

I can't figure it out, having spent many hours adapting the bar graph which won't display in either an .exe version or web version when published.

Any help would be appreciated.

Kind Regards,

Hi Steven,
it doesn't appear to do anything at first sight.

However -- after being published the vector is growing DOWN instead of expanding both up and down.

See attached pub -- I've moved the vector up so you can see what it is doing after you publish it.

Hopefully DW can comment on this interesting issue.

cheers
Paul

This is strange, but true. Brenden's sample works fine in Preview, but when Published it didn't work. So I played with it. For some strange reason, the Vector will only expand downward, so it didn't appear to be doing anything because it was inside a cover Frame.

I've moved the Vector to the top of the Frame, and made a couple of adjustments to the Button's Action (so IF you press the "Set" Button a second time, it resets everything).

Brenden, please add this to the "list" of things to look at. In Preview the Vector expands in two directions (up and down) but in Pub it only expands in one direction (down).

Take a look at the new attached example, this uses a different method.
A 500 pixel bar is pushed up the screen, this works much better.
The problem with the original is a possible maths or rounding issue, the vector was small and scaling it so much was not probably a good idea. We will look into it.

Regards

Brenden Knifton

Thanks Paul and Fred for your help and support.

Again, thanks Brenden for this new solution.

I hope DW can sort out what happened in the first sample.

Kind Regards,