Geoffrey Akien

I've been using this for a while now and its great but...one of the tests for changing numbers into text needs adjusting for logicals...

I change:
if isnumeric(contents)

into

if isnumeric(contents) || islogical(contents)

Because the logical class is not including in isnumeric (helpfully). It may add a small speed hit, but it increases the robustness a little.

Thanks for the program though!

"split" is a subfunction within tempobjcomm for converting 16 bit integers into 8 bit integers in the right format for modbus communication. I wasn't aware that it was also the name for a FileExchange submission (searching for "split" turns up 96 results), and this is only a subfunction, which means that only tempobjcomm can see that it exists, and if split exists as an M-file or whatever in your own path, subfunctions take precedence (within tempobjcomm.m) so that it will not interfere with its operation ( http://www.mathworks.com/help/techdoc/matlab_prog/f4-70666.html ).

I like it better now: it works correctly if you don't abuse the syntax too much, and provides explanatory error messages if you do; The code is well documented and indented, enabling a very easy reading.

I like the implementation use of three overlapping empty-text uicontrols with different background - an innovative alternative to what would normally be done with axes and a patch object (which are admittedly more cumbersome/heavy).

I think this utility, although useful as-is, could be improved further. Here are a few ideas:

1. Enable the context-menu by default (currently off by default - why?)
2. Provide sample usages in the main help comment (for example, modification of the progress bar color, addition of percentage labels etc.)
3. Combine the 3 sub-functions into a single m-file with a single interface. For example: calling tooltipwaitbar with a negative progress to delete the waitbar; calling tooltipwaitbar with its own handle to update the progress value.
4. Accept percentage progress values (between 0-100), not just 0-1 values
5. The main function is fairly large (>200 lines) - I would break it into sub-functions for readability.
6. enable accepting a context-menu handle (not just a true/false flag).
7. There are quite a few other waitbar implementations on the FEX - if you take a look you might get some other interesting ideas.

But as I said above, this utility is already useful as-is. An innovative idea and a good implementation. Good work!

While not a 5-star utility in my eyes, it does merit an A+ for innovation and the author's quick response to early feedback; I also wish to offset my original rating.