Yes, too bad no others share and participate, I am not suprised
. It might also be as you say nobody else is digging into these things or using mobile much.
Regarding both of these issues, they are solvable via CSS and as both of these are no "just do this" problems and also I think depends a bit on app layout and theme used, I have no "formula" but here are some tidbits from my head and notes on these things if it helps:
- The first one is something I struggled a lot with and is a combination of many different things, adjustments in CSS etc. and the main thing that got me on the path to finding a solution was doing changes to the CSS overflow properties for the entire body + for the layout where I use a form + adding some small CSS adjustments here and there. Try doing the following:
1. Override the overflow set for html/body by Aware to (do the override ONLY for mobile VP´s as it messes up things in the desktop VP so have the override for example in a HTML content panel at the top of your mobile VP using a <style></style> tag):
Code: Select all
2. Create a custom class in your custom CSS file for the app where you add:
Code: Select all
overflow: visible !important;
3. Add the new custom class as a class used by the content panel (i.e set "CSS class" in the VP configuration for the content panel) that displays your form in your mobile VP.
4. Add the following CSS style override to your mobile form. I use it with a <style></style> tag in the form header:
Code: Select all
overflow: auto !important;
5. Test form on a mobile, the keyboard problem etc. and make small adjustments to margins etc. if needed. The form height and content panel height has to be UNSET i.e not set if I remember correctly.
I am not sure if I have made other changes via custom CSS files, startup.html or forms that contributes to it being solved for me (I also have various other configuration parts related to this to enable my mobile/tablet uniform design which may contribute) but try it (I THINK it will work for you) and report back if it does and if so, we can maybe report to Vlad and he can look at a real fix for this for core Aware IM.
- The second one (if I understand you correctly) is also a bit tricky. I have no horisontal scroll issues at all (after tinkering) so is entirely solvable via CSS as well. In Aware mobile the setup of the different divs etc. and it´s CSS creates some inconsistencies (mostly related to CSS margins + Aware having many many container divs. If you look at the DOM of an Aware form for example you see a very long tree of things that affect the actual form end result) and there and a 2 parts of this particular problem I have changed via CSS: Manipulate overflow-x (hide if in most cases if horisontal scroll is not needed) + change margin for rows (.row classes) where Aware adds a margin of 13px I think it is in different places (or if it is Bootstrap that messes it up with the row CSS, I can´t remember which). Aware also adds 20px to some left side margins and 10px to others and this also creates problems.
Regarding the custom HTML forms, I have actually not used these and great as they are, I was concerned about performance and also to some extent with security. I am not sure how Awaresoft solved it and if they hacked up some solution to make it work (no offense Awaresoft
) so felt a bit icky to me
+ I have managed (via a lot of tinkering) to do what I want with the existing Aware forms. I also use forms in many places instead of queries to deliver a uniform UI/UX (form with references thing I wrote about in my last post). I might look into it some more in the future though and what you did looks really nice so I understand it is a powerful/nice feature and might be the easier path compared to how I do it BUT it has it´s limitations so isn´t fix all solution to form problems either.
Henrik (V8 Developer Ed. - Windows)