We have implemented a tablet-based application using Oracle MAF. The application runs on Windows UWP. When it was rolled out last year, it has been working fine until the customers upgraded Windows UWP on their laptops to Windows Anniversary edition. After some investigation, We found the following issues:
When user clicks on input text fields in a popup dialogue, the
application randomly crashes (not always but frequently).
When user clicks on input text fields in a normal window (i.e. not in a popup dialogue), and if the screen resolution is scaled (e.g. 150%), the
application also randomly crashes.
When screen resolution is not scaled (i.e. 100%), clicking on input text fields in a normal window
does not seem to cause crash. However, clicking on input text fields
in a popup dialogue can still cause crash.
We could not find any useful/relevant info in Windows log or in our application log.
We have also tested our application with the latest Windows Creator Edition and MAF 2.4.1, we found that the chances of random crashing seemed to have decreased, but crashing could still happen.
We have checked the Oracle MAF certification information at http://www.oracle.com/technetwork/developer-tools/maf/documentation/maf241certmatrix-3746359.html.
It states that "Any tablet or desktop running Windows 10 with Intel processor" are supported. Our customers' laptop specs are:
Lenovo Yoga with Intel Core i5 processor;
Windows 10 Anniversary Edition;
Full High Resolution screen (1920x1080)
Therefore, we believe the customer laptops provide certified runtime environment for MAF applications.
We have researched various technical forums. There seems to be little information about using MAF under Windows UWP environment.
Because our application has been used in production, and the customer corporate mandate is to use Windows 10 Anniversary edition, the customer expressed grave concerns to us for choosing MAF as the mobile platform technology, and we are now under enormous pressure to fix this issue. Any suggestions and pointers will be highly appreciated.
If you can create a reusable test case, my recommendation to you is to lodge a Service Request with Oracle Support so Oracle's development teams can look at this.
We have done further investigation on the issue "input text field causing crash on Windows 10 Anniversary Edition". This time we used the demo CompGallery application from Oracle. We navigated to the "text box" tab, clicked on the text box in "outside a form", entered some text, then clicked on "inside a form" text box. The application crashed (or repeat the above sequence a couple of times on Windows Creator Edition, the application would crash). Note by using "tab" key or screen tapping to navigate between input text fields, we can avoid crashing. With extra clicks on different input text fields before entering text, we can avoid crashing as well.
The CompGallery screen is shown below:
We then looked at the Windows log, not much details were revealed. It contains an event related to the failure of edgethtml.dll, as shown in the screenshot below.
I have a problem with the Input Simulator in the microsoft surface SDK 2.0.
Whenever I try to simulate a finger or a blob click, the first click stays pressed (like when you put it as placeholder with right click+left click).
I don't know the reason of this behaviour since on other computers it work without problem.
Can it be because of I'm using windows in a virtual machine? If yes, is there any workaround?
I fixed this by disabling touch pen utilities which was automatically installed with surface SDK.
I am using Tooltipster to show popup on my website. I do not want this tooltip to show on touch devices, so i use the option - touchDevices: false. It is working fine on all other touch devices except Windows Phone. Any suggestions, how can I resolve this.
Thanks
i'm working on a Windows 8 Store App and i am trying to use different icon resolutions for different screen sizes.
But somehow
ResolutionScale resolutionScale = Windows.Graphics.Display.DisplayProperties.ResolutionScale;
always returns Scale100Percent. I tried it on my Desktop PC, which runs at 1080p and i also tried it with the simulator in all different resolutions it offers but the ResolutionScale Property stays 100%.
Using DisplayInformation instead of DisplayProperties is not an option because i still want to support Windows 8.0.
Does anyone know if there is another way to get the current resolution scale in Windows 8.0 or if i am doing something wrong?
Thanks in advance
Khrimm
Edit: Using the actual screen resolution to determine the scale factor seems to be another possibility.
I trying to build a Windows Phone 8 Application which is able to sync data from a webservice.
While I'm syncing the data I want to display a little Popup / overlay / flyout but I still want to be able to navigate between my pages while my overlay persists between this pages.
I did this successfully with a Windows RT App: I simply added a Frame-Control on a RootPage which also display the flyout. I navigated then within this frame and the flyout was always there.
How can I achieve this goal within a Windows Phone 8 Application?
You can do it as you did on Windows8 which is to restyle the ``RootApplicationFrame to add your indicator. For an example see http://www.jeff.wilcox.name/2011/07/creating-a-global-progressindicator-experience-using-the-windows-phone-7-1-sdk-beta-2/
Or you could just use the progress indicator in the system tray of the page to add indication there. This is probably the most common approach taken in apps. See how at http://blog.duc.as/2011/10/08/using-the-system-tray-to-show-progress-in-windows-phone-7-mango/