Page 1 of 1
Unwanted Error Msg box
Posted: Mon Jan 05, 2015 4:47 pm
by drp2thehill
Having this box popping up when an error conditioning indicator is set *on.
I've attached a file with screen captures of the unwanted message and the result that comes afterward. the red box with
Updated! in it is the only box I want displayed. Thanks
Re: Unwanted Error Msg box
Posted: Mon Jan 05, 2015 4:56 pm
by Scott Klement
That's weird, I have never seen it display both the "tool tip" (red box) and the alert box (pop up) at the same time.
Can you please provide a json dump of your screen so I can try this on my own machine, and troubleshoot it? You can do that by (1) reproducing the problem, and (2) pressing Ctrl-F9 (after anwering the pop-up if necessary). The browser should ask you to download a file named json.txt -- please post that file here, or e-mail to
support@profoundlogic.com
Thanks!
Re: Unwanted Error Msg box
Posted: Mon Jan 05, 2015 5:12 pm
by drp2thehill
Scott, the pop-up box occurs first, then when 'ok' is clicked the red text over box appears.
Re: Unwanted Error Msg box
Posted: Mon Jan 05, 2015 6:34 pm
by Scott Klement
The issue is that you are sending the message twice. Once is at the screen-level (which is producting the pop-up), and one is at the widget level (which is providing the tool tip.)
If you look at 'error messages' at the screen level, you'll see that you have a message with the text 'Updating!' that is conditioned on the ArrDtUpd indicator, which is turned on. Whenever you define a message at the screen level (as opposed to a widget) it will always display as a pop-up, since there isn't a specific widget to put the tooltip on.
Probably the one defined at the screen-level was an accident. (I know I've done that before... I go to define an 'error message', and forget to select the widget first... easy mistake to make... then it ends up defined at the screen level.)
Anyway, if you only want the one in the tooltip, remove it from the screen level (but keep it at the widget level) and you should be all set.
Re: Unwanted Error Msg box
Posted: Mon Jan 05, 2015 6:51 pm
by drp2thehill
Sorry, I'm not following. Can you send an example of what you mean?
Not following 'screen level' and 'widget level'. Thanks
Re: Unwanted Error Msg box
Posted: Mon Jan 05, 2015 7:14 pm
by Scott Klement
I think you already know that when you click on a widget, the "properties" box shows (and lets you change) the properties for that widget.
- widget-level.png (24.18 KiB) Viewed 490 times
You have the error messages defined there... that's all done as expected.
But, you can also set properties that do not refer to a specific widget, but instead refer to the screen as a whole. You can do that by clicking on the canvas (the 'graph paper' that you design your screens on) or by clicking on the record format in the record format dialog (which I find easier). So click on the record format, and you'll see the properties dialog changes to show the properties for the "screen"
- screen-level.png (27.19 KiB) Viewed 490 times
The problem is that you have the message defined in both places. You are both showing a message saying 'Updated!' on the widget itself, and you are also showing a messasge saying 'Updated!' on the screen. So the message is appearing twice, once as a pop-up (that's the screen one) and again as a "tool-tip" (the red box -- that's the widget one.)
Does that help?
Re: Unwanted Error Msg box
Posted: Tue Jan 06, 2015 10:43 am
by drp2thehill
OK, I found it. On the Screen Level, when I scrolled to the 'error message' screen property, the face of it was blank. Yet, when I clicked on the '...' to the right, the messages were there.
i.e.: Messages
Error Messages
As in the Screen Properties attachment. I had no clue the messages were there , and what's more, I NEVER added them there.
Anyway, thanks for your help, Scott.
Re: Unwanted Error Msg box
Posted: Tue Jan 06, 2015 1:31 pm
by Scott Klement
Great! Glad you figured it out.
It sounds like something got messed up in the JSON code for that display file, and that's why it showed up as blank. If this keeps happening (and, especially, if you know how to reproduce it) please file a support request with Profound Logic so we can take a look and get it fixed.
But, if this is the only time it happens, I'd just call it a fluke...