Apologies for the duplicate. I just submitted this but do not see it so re-submitting.
LBV forms will put a textbox on the next line if there is not enough room given the window size. The issue I have is that the label for that textbox is left on the previous line and it is very unintuitive to figure out which label connects to which text box. Can I make the label “stick” to a textbox?
Also, is there a way to top-justify the label for a text-area? right now, labels are bottom-justified.
Actually… about to give up and hire someone to create HTML forms from scratch. I’ve never been quite so frustrated trying to figure out how to control layout. You have 2 controls to play with (Label and Data Cols)… and I cannot see any obvious rhyme or reason for what they do.
Ed, visualize the layout as a table with 4 columns. Each entry you create takes slots from label and data numbers. After 4 slots are filled, new row is automatically started. That leads to ‘interesting’ display and update layouts. Typical layout will be 2 label/data pairs on 1 displayed row. But you can have 1 label column and 3 data items on a single row or 2 label columns and 2 data items or any such combination. Key number is 4.
LBFs are not flexible or appealing as a design choice but you can make it work with lots of trials. Just treat LBF developer’s reasoning as a rhyme and you will learn the tricks.
When you make your layout work, consider donating part of developer budget you saved to MU2 updates…
It’s a bit harsh to characterize the documentation as “poor”. (We don’t want to bruise Wiki contributors’ feelings.)
Sometimes it’s a matter of knowing where to look. Directions are given here.
To spare you from having to go through the lengthy article, do the following:
enter a label for the first field, use 1,0 for Label Cols and Data Cols.
enter subsequent labels, use 0,0 for Label Cols and Data Cols.
It’s not likely one can squeeze 12 fields into 1 line because labels are rarely 1 character long. See attachments 1 & 2. The form, Test, is in the 4.1.2 Demo.
If the form disappears by the time you get to it, use the attached .sql file for experimentation in the Demo 4.1.1.
In addition to Label/Data Cols, control of the layout is achieved through the size of the Data Type.
If you are eternally grateful (tongue-in-cheek), consider this (not tongue-in-cheek).
Thanks for the encouragment folks. I’m trying again. But this makes no sense.
I have enclosed 3 screenshots. #1 is how I configred the layout. #2 is the result. #3 is the result of ONLY changing the first field (Complaint) DataCols to 4.
Can someone explain? I though that by using 1/4 (label / data), I’d get it to be on its own line and have the smaller ones on a line of their own.
It took me a while, since I thought I could do without the manual. But all changes have effect on all. Is this image what yo want to achieve?
Then go to Demo version 4.1.1 and copy the Lay-out. If you take some extra time it can be even better with the correct fields. (be there before the system resets. I did not make a copy!)
My way of working is as follows:
Make a LBVForm just as the best you can achieve and start making modifications.
Click between encounter of a patient and Lay-outs in administration. Step by step you gain more experience and see how different field will interact.
And here is the copy of my Lay-out changes. Just they wont get lost. Not a wonder of creation, but just my solution to try to make it as close as you might want to have your Form. (BTW it was a great experience to get this form with all kind of different options during the creation encountered, I could not find a calculations field)
Als list and Add should work great for prevention.
A great alternative for history, allergies and Family History are Nation Notes.
The 4.1.1 Demo reset today causing Pimm’s “Ed Laudau Form” to be lost.
Attached are the .sql files for the list and the layout for the GYN History Form, which should come very close to that requested by Ed. If the files are imported into their respective tables, the form should pop up.
if the SQL files are the thing Ed needed for his OpenEMR set of forms and it works as you say, don’t forget to include the files in the Wiki Lay-out based Forms additional options.
Because it has been awhile since creating the Eye forms, some of the tricks had to be relearned.
Helpful hints:
Start each new line with 1,3 for the Cols for the first field of that line.
Use 0,0 for subsequent fields of that line.
Keeping the Data Type uniform facilitates form creation. Once the layout is nearly satisfactory, then experiment with different Data Types.
Fields of the same Size will align more readily.
It’s counter-intuitive but Textbox will allow more characters than Textarea (experience with Eye Forms).
Because Ed had different Data Types and different Sizes (Age, Gravida, etc.), it was more of a challenge than a form with uniform Data Types and Sizes.
No Static Text was included because there were none in Ed’s form.
To export .sql files, go to the specific table’s last page, check the rows of the form and use the export tab. This method obviates the problem of duplicate rows causing import failure. There is no reason to import the entire table for this exercise.
All the Demo’s export, but only the current 4.1.1 Demo will import. Brady’s new Ubuntu Demo’s should make importing easier because they will have updated versions of PHP. Should the old Demo’s die, there will be replacements.