Hi all,

(Using WebDev 19.)

I am facing a challenge as I am creating a WebDev variant of an existing
WinDev application. In WinDev manipulation of Check boxes with multiple
options is a piece of cake: you can hide/unhide, gray out,
enable/disable one or more options of a check box at will during
runtime. In the project I am working on the availability of certain
check box options depends on choices made within other check boxes
and/or the values selected in combo boxes.

So far so good but it seems that simulating this behavior in WebDev is
virtually impossible. There are almost no check box properties available
in browsercode, which is the only way to go to have fast screen updates.
As an alternative I tried using servercode with AJAX enabled, which
works fine as long as there are no commands in the server procedure that
conflict with AJAX. And there's the catch: many commands do conflict and
I cannot isolate them in separate procedures. I can fiddle with the
check box item caption using AJAX enabled server code, but this leaves
me with quite a bit of serverprocedures not able to run under AJAX and
thus not updating the screen. Due to the nature of the application a
full refresh of the screen simply takes too long.

I am stuck with a trade off: - either the application is too slow but
correctly displays the option availability
- or either the application is smooth and fast but the available options
are not correctly updated for the user

So the questions is: does anyone have any tricks in manipulating Option
fields (and also Combo boxes for that matter because the issue is
similar there).

Thanks

Hi Fabrice,

This does shed light on the issue, however there was one more thing to
be kept in mind before this actually worked:
At first, I set the info line (which was the only code line in the
servercode part) to comment using // and then ran the test... still
nothing.
So even a server procedure with only comment lines (and for that matter
even one with nothing in it except for an empty line) will be sent to
the server who does absolutely nothing with it but still refreshes the
page.

But after all your suggestion does works, thank you for your effort !

I am still faced with a huge limitation though. This does imply I cannot
afford to run any servercode (or at least no code that does not support
AJAX) after I changed the available options using the JSProperty command.
Which is virtually unfeasible because lots of other controls on the same
page have to be manipulated, changed,... and a lot of them simply
requiere the server to recalculate and transmit updated information.

But nevertheless, thank you, this was really educational.

Kind regards
Stefan