Page 2 of 2

Re: Profound UI Mobile Client

Posted: Mon Oct 22, 2018 3:20 pm
by Scott Klement
Yes, that is what I meant, but perhaps it does not work. I think for client-side timeout, it needs to be set up very early in the session, and perhaps "external javascript" isn't early enough.

I can tell you for certain that changing the start.html in the IFS and/or putting the file in userdata/custom isn't going to help with a mobile app, as these are not used unless you are running it in the browser.

But, if "external javascript" isn't working, then the only thing I can think to do is to either (1) create your own app with PhoneGap, or (2) create a support issue with Profound Logic asking for them to determine why its not working and/or possibly add a feature to solve the problem.

Re: Profound UI Mobile Client

Posted: Tue Oct 23, 2018 3:13 am
by JPG
Thanks Scott.
For our part we prefer to maintain this development whenever there is a solution that makes it operational.
At this time we do not have trained personnel for Phonegap and make possible changes.
If you see that there may be a solution maybe it would be the best solution.

Re: Profound UI Mobile Client

Posted: Fri Oct 26, 2018 3:43 am
by JPG
Hello Scott,

We've been doing some tests and we've found out that our application works well if the phone is plugged in. In other words, no timeout message is shown when charging.
However, when the phone is not charging, after a period of inactivity ( between 10 or 15 minutes), the timeout message pops up.
We've changed some battery and data setting in our phone, but without any success.
Any suggestions would be appreciated.

Thanks in advance.

Re: Profound UI Mobile Client

Posted: Mon Oct 29, 2018 12:01 pm
by Scott Klement
Your phone is trying to conserve battery life by disabiling the keep-alives. There's nothing we can do about that.

Perhaps an "offline" mobile app would be a better decision for you? So that you don't need a constantly active network connection?

Re: Profound UI Mobile Client

Posted: Fri Nov 02, 2018 9:39 am
by JPG
Thanks, Scott.

This program must constantly receive requests that must be made at that time and notify its completion. It is not a batch process.
It is done interactively, without thinking about the problem of a mobile.
According to this, we must know with certainty which solutions are the most appropriate.
Another problem is the profile needed to convert what has been done (ile-rpg) to this other system.