Update XDialog Listview

[David Martin]

I want to have a status update while a script is running. My thinking was to use an ui_modeless_dlg_box() with a ListView in it and then just add an item to the bottom of the ListView as the script progresses. There are only going to be 5 or 6 steps in the script but some take a few seconds to run and I want to make sure end users know something is going on.

Is this the correct way to do this in XBasic/XDialog or should I be looking at something else? If so, then how do I update the ListView as a stop completes?

Thanks,

David

[David Martin]

Re: Update XDialog Listview

Well, I gave up on the ListView idea and just use a multi-line textbox and modified version of what is in this post:

http://msgboard.alphasoftware.com/al...ghlight=selwyn

[Clunes]

Re: Update XDialog Listview

I do updates to listviews contents all the time. If you create a simple listview using the xdialog genie and then look at the code it produces, you will see a refresh code. Usually runs the getcontents() function. All you need to do is run the get contents function when you make any changes. If you make a change to the table it is based on then , the listview will be refreshed with the changes. If you are adding static text then you may need to do edits to the getcontents() itself. The trick to accuracy is to understand how the list view manages its ID for the row

[David Martin]

Re: Update XDialog Listview

Thanks for the tip. I must have missed it, will take another look.

[Clunes]

Re: Update XDialog Listview

demo.zip

Attached is zip with a demo movie. It shows the use of an xdialog with a listview. Items are added to the listview using another xdialog. Nothing in the xdialog is connected (bound) to any table until the user selects save. It shows how the xdialog is updated

[CALocklin]

Re: Update XDialog Listview

Here's another alternative. Why not use a WaitDialog and just change the text? The one down side to this is that you can't keep much of a running list of what has already happened because there is a limit of three lines. On the other hand, do they really need a continuous list or do they just need to know that something is still happening? Another advantage of the WaitDialog is that you can have a progress bar along with the text. And, unlike the "statusbar" methods, the WaitDialog shows in the middle of the screen where people can't miss it.

There is also a PleaseWait function in the Code Archive. This can be used/modified to show different text as the script progresses. That function was created before the WaitDialog was available, I still use it (with some significant modifications of my own) for some situations because its a one-line command whereas the WaitDialog takes a few lines to set up. (I put the command itself into my Code Library so I can quickly add it to any application.)

If you want a progress bar, I highly recommend the WaitDialog instead of the statusbar simply because it's amazing how many users never see the statusbar until after they call you and you tell them to look at the lower left corner! (Are there really that many blind people using computers?)