Hi again!

> I'm creating a job configuration (an *_config_*.m file) for a new
> toolbox I'm developing. I already know I have to put my file in the
> toolbox folder, don't worry. I have basically three questions about
> the manager:
>
> - when will you change the help-listbox-structure to a thing that can
> use (La)TeX? I suspect you had it at one point, because I see such
> code commented in your source.
>
>
>
> There are no plans for this, as ListBoxes can't (yet) use a LaTeX
> interpreter. The parts that appear to be commented out are actually used in
> the manual. Much of the manual is automatically generated from the online
> help, but because I wanted to include extra bits of LaTeX in the manual
> (which would not make sense in the online help), there were some
> modifications made in order to do this.
>

Ok I can live with it, it would just have been a nice addition ;-)
I'm thinking of writing on a figure with text( ):

fh = figure('Position', [400, 10, 500, 80], 'MenuBar', 'none',
'Color', [1 1 1], 'name', 'Current step', 'NumberTitle', 'off');
set(gca, 'Visible', 'off')

th = text(0.5, 0.5, ['This is text.' 10 'And a new line has
started.'], 'Color', [0 0 1], 'FontSize', 18, 'Interpreter', 'tex',
'Margin', 10, 'HorizontalAlignment', 'center');

(and delete(th) to clear the text)

But I can't implement that due to lack of expertise, also it's just an
extra feature.

> - can I (I think I currently can't) present the user a list of
> options, where she can select multiple things (for example with the
> ctrl key), but not the same thing twice? I have a hack at the moment
> with a repeat and .num set to the maximum of the options, but doubles
> are still possible. I'd like to avoid this, because it's not
> userfriendly.
>
> There's no elegant way of doing this as the code currently stands. One
> thing you could do though is to use a check field.

Yes I could do this, but it would require that users read. In my
problem I could actually avoid the list by forcing everything
selected. (It let the user select what output variables they wanted,
now I'm defaulting to 'all', so they can delete what they don't want
afterwards.)

I have another problem with 'check' though. Well not problem, but
design issue. If you want to check an element in the tree, you have to
put the .check one branch higher instead of on the element itself. I
find it a bit annoying, because that branch contains other things that
need to be completed before the check function is called.
My example:
Main
 |- Subjects (repeat)
 | |- subject <
 | |- subject <
 |- General settings (files)

I want to check the general settings files leaf, but I have to put the
'.check' on Main, so it won't be called unless all subject data is
entered correctly.


> - how does the num field work with string entry? I have to use [1 1]
> or something equally weird for it not to crash, but I don't understand
> what the difference is between [inf 1], [10 1], [1 10] or just [1 1].
>
> It specifies the size of thing you want to enter. You would use [1 1] for
> entering a scalar.

So what should I choose for a string (char array, or is it cell)? All
of them seem to work.

Cheers,
  Tom

BTW reading your code is fun!