About comment#1/2:
We have created http://bugzilla.recordsforliving.com/show_bug.cgi?id=1034 to track this issue. But this is minor, as I believe it has a simple workaround. Just don't select 'same as ordered' or 'during visit' - but specify the details. The reason you are right this is a bug - is because you might want to also note that it was during the visit, and you cannot do both.
This is a flaw in our data model, and as such, cannot be easily fixed until HealtHFrame v4 (so probably years away).
Comment #3: This appeared to work as expected when I tried it, so perhaps I need some clarification. Maybe this issue is just related to #1/2?
Comment #4: I am able to attach files to expenses (see attached image). Perhaps the confusion is that you must click "details..." to add an attachment. You cannot add it directly in the expense register. AH! Nevermind - I see. This is a serious bug! Adding MULTIPLE relationships to an expense appears to be what is broken. it even crashes sometimes. This is very important, and I'll get to this promptly. Sorry. (reference http://bugzilla.recordsforliving.com/show_bug.cgi?id=1035)
Comment #5: I cannot reproduce this issue. Changing the copay amount appears to work fine for me. However, this could easily have todo (as you suggested) with the other bug - #4 - so I will address that first. After you recieve the fixed verison of HealthFrame that addresses http://bugzilla.recordsforliving.com/show_bug.cgi?id=1035 - please see if this issue still exists.
Comment #6: added http://bugzilla.recordsforliving.com/show_bug.cgi?id=1036 - you are obviously correct. This is a major flaw with the healthFrame UI. This UI was written at a time doing what is now called responsive design was extremely difficult. Now its only difficult ;-).
But fixing this in HealthFrame requires nearly rewrtiing the HTML portion of the app (a fair bit). That is actaulyl something we plan to do, but it probably wont be soon. Note - the place this is MOST important is probably with reports. Sorry. You must take the good with the bad. As is - much of the layout would break if we allowed elements to be resized.
Comment #7: this (as you probably guessed) is closely related to #6. The way the text control handles embeddings (like the excel one) - is that they are a single 'row' of text. If the last 'row' of text cannot be displayed, its 'wrapped' to the next page. The only way around this is to 'scroll' so the excel table is in the top row.
This is a defect (a small one) with the underlying text edit control I use (https://github.com/SophistSolutions/Stroika/tree/V2-Release/Samples/ActiveLedIt). This is an open source project ;-). If anyone wishes to fix the control, that would be great ;-). But beware - most text controls have similar or worse defects.
really - the fix in #6 would help the most.
Comment #8: I was under alot of pressure from existing customers to release HealthFrame as soon as possible. Those who've used HealthFrame v2 and v3 know its been very late, and now know we've improved alot in HealthFrame v3.
I had a choice - release HealthFrame v3 without fixing the external help. I KNOW it looks TERRIBLE. But most people dont read/look at online help even if its great. I think I made the right trade-off. Still - the online help unquestionablly looks horrible, and I will make an effort in the next month or two to shore it up a bit. i wont perfect it in that timeframe, but make it less of an eyesore.
Sorry - and thanks for your feedback and understanding.
