msgbox() vs. ui_msg_box()

[enstorms]

I am basically lazy and have gotten into the habit of using msgbox() instead of the ui_msg_box() function because it's easier and faster to type. I would like to know if there is any difference and make sure I am not digging myself a hole I won't be able to get out of down the road. In looking at the syntax that pops up when typing msgbox(), only one parameter is required, the title/message. IF that is all that is put in, then it appears as the message with no title on the dialog box. Am I missing some important information here?
Thanks.
Ernie

[Keith Hubert]

Re: msgbox() vs. ui_msg_box()

Hi Ernie,

Looks like you pays your money and makes the choice.

You have the tools to use as you wish. I cant see a deep dark hole here.

[Tbaker]

Re: msgbox() vs. ui_msg_box()

Ernie

Msgbox's syntax is Msgbox(title as c, message as c, box style as n)

See attached thumbnail.

This is a down and dirty form of ui_msg_box().

As Keith said basically - It can't hurt.


Tom B

[MikeC]

Re: msgbox() vs. ui_msg_box()

Tom,
I think Ernie is asking whether one is better than the other....The main difference is that msg_box() only has one required argument with the others being optional ---which basically says that it is a higher lever wrapper for the older ui_msg_box() which required 2 arguments with one optional. Using lower level functions can result sometimes in faster speeds or even more control in how a function acts/reacts. In this case I don't believe there is enough significance to sway one way or another in this regard.

[enstorms]

Re: msgbox() vs. ui_msg_box()

Appreciate the replies. Mike, I had assumed that msgbox() was the older since there are so many ui_...... dialog boxes.

....a higher lever wrapper for the older ui_msg_box()......

So my thinking was, it may not be supported down the line and I'd have to go back and change all "msgbox()" to "ui_msg_box()". I guess this probably won't be a problem.
Thanks again.
Ernie

[csda1]

Re: msgbox() vs. ui_msg_box()

Hi Ernie, Mike et al,

Msgbox() is definitely a wrapper for ui_msg_box(), and thus is slower. But as Mike said, it doesn't really matter. However, if you use a variable for the message 2nd argument and it just happens to be blank, then the title parameter is assumed to be the message to display, which is wrong.

Try it with the following code in the interactive window;

msgbox("abc")

msgbox("abc","")

msgbox("abc","def")

message="def"
msgbox("abc",message)

message=""
msgbox("abc",message)

For constants it works as expected, but if a variable is used for the 2nd argument, it depends whether it is blank or not. This could cause unexpected displayed results in this case depending on the variable value.

I think conceptually the idea for the msgbox() was good, to allow quick displays, but not for regular code. If I had written it, I would have interpreted the parameters depending upon which were given as such

msgbox(message)
msgbox(message,boxstyle)
msgbox(title, message,boxstyle)

This would not have yielded the same problem.

[enstorms]

Re: msgbox() vs. ui_msg_box()

Ira,
Thanks for taking the time to further explain the msgbox() function. As I have stated earlier, I am basically lazy. I haven't taken the time to figure out how to code xdialog boxes, so I have used AS to design a couple of boxes with color and Ok, Cancel, or just Ok, or Yes No. Then copy the code into a script. Then copy whichever code suites the situation and go in and manually change the message and message box size. Was thinking yesterday how to get variables to display within my messages. Had forgotten about the use of a message variable where it could be built into that. Will look into doing that.
Thanks again for your help. And, FWIW, I have been looking at your code utility, since I seem to be doing more and more xbasic coding/testing.
Ernie

[Mike Wilson]

Re: msgbox() vs. ui_msg_box()

I, on the other hand, have gone the other direction and use neither ui_msg_box() or msgbox() within final code, but instaed use p_msg_box() kindly provided by Bill Parker:

http://msgboard.alphasoftware.com/al..._msg_box%28%29

I use msgbox() to display and check values within code as I am writing code because it is simple to type, and remove them at completion, but use a customized version of p_msg_box() for permanent code.

[csda1]

Re: msgbox() vs. ui_msg_box()

Hi Mike,

I, on the other hand, have gone the other direction and use neither ui_msg_box() or msgbox() within final code, but instaed use p_msg_box() kindly provided by Bill Parker:

http://msgboard.alphasoftware.com/al..._msg_box%28%29

I use msgbox() to display and check values within code as I am writing code because it is simple to type, and remove them at completion, but use a customized version of p_msg_box() for permanent code.

That's a good thing to do.

Since about September 2008 , I have had my own full replacement for ui_msg_box(), that incorporates ideas from both Cal's and Bill's similar routines, as well as my own enhancements. Some of my own improvements include modeless operation, timeout closing of the box, HTML support, flashing text etc., while maintaining backward compatibility to the standard ui_msg_box().

But my main reason for replacing ui_msg_box() (see this thread) is that the timing events of dialog boxes (but not forms) are shut down while the ui_msg_box() is opened. This is really bad, as that means that while the box is opened, any XDialog boxes are totally shut down. Imagine you had an auto-save routine (part of my CSDA code utility as an example). Nothing happens until you close the ui_msg_box(). There are a few other low-level ui built-in functions that act like this as well. I steer clear of any of these.

[Mike Wilson]

Re: msgbox() vs. ui_msg_box()

Ira,
timed modeless dialogs as apposed to modal dialogs. Sounds intriguing. I seemed to remember another thread a while back in the same vain as the one you referenced with same type of problem where there was something about an administrator of an Alpha application on a network having a heck of a time as there constantly were dialog boxes left open on users machines behind screensavers that locked up the system from being closed down appropriately for updates and maintenance. I'm thinking timed modeless dialogs as you pointed out as potential solution to these types of issues. Yhanks for the reference. A good topic to ponder.

This being said... what add_in utility has the capabilities of searching all the applications code for every instance of ui_msg_box() in order to replace with an xdialog variant?.......

[csda1]

Re: msgbox() vs. ui_msg_box()

Hi Mike,

timed modeless dialogs as apposed to modal dialogs. Sounds intriguing..... I'm thinking timed modeless dialogs as you pointed out as potential solution to these types of issues.

It's not just modeless dialog boxes, modal dialog boxes can have timers too (and are actually more usefult too)!

For those dialog boxes operated in modal modes that return data, like ui_get_list2(), in my enhanced versions, the default value (if any) or the current selection is returned if the box times out, or for those like ui_msg_box(), it returns the default button. I typically show in the status bar the time and a countdown in seconds left, so users have an idea of how long they have to decide. I think I'll add an optional additional time button to allow users who need more time, but eventually it will timeout, which is what is needed in many cases.