Should I be annoyed by the following behaviour of HTML Composer:

You add a bunch of different types of controls to the page. You set up default values, add multiple static values to drop-down boxes etc.

Then you point the Submit button to report, assigning parameters to the existing controls. All the defaults and static values that you previously added are thrown away - you end up with empty controls.

Should I be annoyed by this behaviour? Because I am.

This message has been edited. Last edited by: Francis Mariani,

You have to think "backwards" ... first create the report code, add it to the page and let the GUI create the all controls for each &variable in finds.

Then you style, assign defaults, list values and what not ...

The suffering does not end there of course as you've already found out

What I find amazing and disappointing is that you really have only one shot at making your form work - the first time when you build it. Afterwards, changes are extremely difficult to do. Change parameter names, add new parameters, change the design - all these actions can be very hit and miss.

Here's another one. I like naming my controls and parameters the same so that they're easier to pair up. This seems to work without issues for all the control types I've used so far - except sliders.

Sliders are made up of 5 components, though only one is bound to a parameter - the others are there for the mechanics of a slider.

main control id: slider1
left arrow id: slider1_downarrow
etc.

I tried changing the id of the main control to the parameter it is bound to, and the screen stopped working. It appears that you must change the names of all 5 components if you want the screen to work.

Oh brother!

An intelligent GUI would change the prefix of these components that make up the control.

ARGH!

quote:

What I find amazing and disappointing is that you really have only one shot at making your form work - the first time when you build it.

When Francis said that - all of a sudden I feel a bit better! I have never gotten a form to work, because I always try to tweek it later, and can't make it do what I want it to. I was wondering how everyone else is able to use this tool, and I can't.

I spent hours today in HTML Composer redoing a pile of work because I *may* have inadvertently pointed the submit button to the wrong report. While re-pointing the submit button to a fex, when the parameters are assigned to existing controls - all the characteristics disappear - static values added to drop-down lists gone; dynamic external fexes assigned to load drop-down lists gone; radio button values gone...

As Waz wisely said ... HTML Composter!