PDA

View Full Version : Change in functionality

zaccari
05-10-2009, 06:09 PM
I upgraded to 2.4.43 a few days ago and I just noticed a change in functionality from previous betas. I don't really know where it happened but I do know I hadn't upgraded in a while. A Field Text widget without a %(f) is not showing the value of the assigned variable instead of the text in the Text tab. Is this and intended functionality change? Is it possible to use a field text widget and not put the value of the assigned variable in it?

Russ...
Dean Roddey
05-10-2009, 06:23 PM
That's not the way it's supposed to work, so I may have broken something. It's supposed to just show the raw text if there's no replacement value. I made a fix wrt to the Xlats stuff lately and that probably is where it happened. Doh! I'll get it fixed for the next one. Sorry.
zaccari
05-10-2009, 06:30 PM
Not a problem. Since it's not intended, I'm glad I upgraded.

Russ...
Dean Roddey
05-11-2009, 04:49 PM
So wait, maybe I'm misunderstanding... You are saying you are putting in some caption text and it doesn't have a replacement token? If so, then no, it shouldn't show the field value, it should show the caption text, so it doesn't make a lot of sense to ever use the caption text without any replacement token.
zaccari
05-11-2009, 05:56 PM
The value in text is "Timeouts:" with no %(f). The displayed value in the field is 15 (the number of timeouts). It used to put Timeouts: with no value.

Russ...
Dean Roddey
05-11-2009, 06:13 PM
Oh. Why wouldn't you just use a static text widget for that? That would be infinitely more efficient.
zaccari
05-11-2009, 06:50 PM
It's an overlay I use to diagnose problems and I change things. If there was a way to change widget types, I certainly would use that. Actually, it would be really nice if a static and field were one field type and the text tab decided what happens.

Russ...
Dean Roddey
05-11-2009, 07:39 PM
These days of course you can reassociate a widget with a different field at any time. So you could always point them at some variable driver field that has default text in it, and reassign them as desired to a specific field.
Dean Roddey
05-12-2009, 05:03 PM
I just put it back the way it was. That's the most consistent scheme and doesn't change functionality on people.