Digital Workshop

I seem to have difficult getting a variable to display in a text box. I create the box, then insert the variable---no problem doing this. I do the right click, then insert variable, so I'm not just typing it in. I use it to debug the program without using Debug.trace. I have all my variables on a master page, which I can select to activate or not.
I have always had this problem with this---sometimes the variable displays, sometimes not. Once I have it working, it works reliably, so it seems to be linked to inserting it.
The way I get round the problem is to delete the variable and insert it again. I just wondered if there was way of getting it to work in the first place? It takes too much time to mess about with it.
Has anyone seen this problem? or know how to get it working reliably.

I have not seen anything like this before and I create 100's of such debug variables every day to check customer’s code.

Things to watch for:

Make sure the text colour of your text box is not set to white text on a white background.

Opus will only display variables declared in the Publication Properties variable tab.
If you create a new variable in script it can't be displayed in a text object.

Regards

Brenden Knifton

How do you "select to activate"? I think that's the problem. Copy & Paste your Text Object with all your listed Variables from your Master Page to a specific Page which you are testing. See if it works. If it does, then I'm correct and your problem is how you've triggered your Text Object to Show, if it doesn't work, then we'll have to try another idea for identifying the problem.

the problem has no pattern to it, so it's difficult to demonstrate, but at it's simplest level, I will insert a variable in a text box the variable is global and selected from the pull down selection, so it's not a script variable.
I can insert it twice on the page, run the program and one will display correctly, the other will not, so my normal way round it is to delete the non working one and insert it again and it may work. It's no great problem to work around. It seems that no one else has seen this problem. I see a lot of 'quirky behaviour with my program--regular crashes, perhaps 10 -15 in a day. Pull down menus in opus stop working, just really odd crashes--the No RTTI Data being one of them. I'm convinced it's something to do with Text Aloud running in the background. I just make very regular backups!!!
Thanks for the help

Sandy --

Can you make a copy of your files and try editing this Publication on another computer, preferrably a desktop model rather than a laptop?

OPUS is such a solid product, and I can't remember anyone describing what you are experiencing, so I'm going to suggest your problem will disappear on another CPU. My old HP laptop gets so hot when I'm showing samples to prospects, I can see why the transitors and circuit boards may go "crazy" when doing serious processing.

It's certainly worth a try. I still need to do the bulk of the development on the laptop, but it will be interesting to see if the crashes still happen on the desktop.
Thanks