access = ReadAndWrite

[ColonelSandersLite 0]

Before I go experimenting with it the hard way, does anybody know what *exactly* access = ReadAndWrite does as it pertains to dialogs?

The only instance of ReadAndWrite on the biki is in the page titled "CfgVehicles Config Reference" and has this to say:

0 ReadAndWrite additional values can be added

1 ReadAndCreate only adding new class members is allowed

2 ReadOnly no modifications enabled

3 ReadOnlyVerified no modifications enabled, CRC test applied

By the way, there's likely to be a few of these type questions poping up from me over the next little while, so stay tuned .

[ColonelSandersLite 0]

This question has been answered by GefrManny who contacted Andrej Boleslavsky who was involved in ArmA's UI development.

(paraphrased for clarity)

Quote[/b] ]That's a good question - it's not very important for mission dialogs IDC, it's relevant for program IDCs , programmers decide about that attribute. It doesn't really have impact or any kind of influence concerning behavior, interpretation/compilation. In user mission dialogs I always use access = ReadAndWrite;

More detailed information may be forthcoming.

[dr_eyeball 16]

GefrManny who contacted Andrej Boleslavsky who was involved in ArmA's UI development.

Nice to know the dev's are contactable for low level queries.

A few of us have been wondering how to get those multi-column lists up (as seen in the MP server list).

Checking the MP UI reveals a ListBox <span style='color:blue'>columns[]</span> attribute, which looks very interesting (and is listed as a parameter in your other post).

addons\ui\config.cpp:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">class RscDisplayMultiplayer : RscStandardDisplay

{

...

class CA_ValueSessions : RscListBox

{

...

columns[] = {0.345, 0.1, 0.26, 0.102, 0.125, 0.068};

Not sure how to use it yet or whether it's even allowed outside via scripting. No luck so far. I've noticed adding a 3rd parameter to lbAdd or altering it's parameters has some effect (or side effect?)

Knowing how that works (if scriptable) would be great to know.

--------------------

Also been planning a dialog which was a grid/spreadsheet, which allowed scrolling and user definable columns, etc. If the above "columns[]" property wasn't availble, then scrollbars would do instead.

Not sure how <span style='color:blue'>scrollbars</span> work yet. Anyone got any starting tips? Are they available? Sliders are probably not suitable, since they don't quite look suitable.

Initially I thought it must relate to perhaps using:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">class RscControlsGroup

{

type = CT_CONTROLS_GROUP;

...

class VScrollbar { ... };

class HScrollbar { ... };

class Controls { ... };

};

but can't figure that one out yet. Again, is it scriptable? If not, might be able to simulate it.

Knowing how that works (if scriptable) would be great to know too.

[ColonelSandersLite 0]

Just looking at the colums[] parameter, I can tell you that those are 90% likely to be width values. Notice they add up to 1 perfectly.

To assign values to it is another question entirely.

Since it's derived from listbox, I have to ask if you've tried passing an array through lbAdd?

Maybe something like this:

_index = lbAdd [idc, ["Text0", "Text1", "Text2", "Text3", "Text4", "Text5"]]

As for a scrollable dialog, I have no idea right now. I would start by looking at the built in dialog that lets you assign controls in the options menu (I can't remember what it's called in the configs right now).