Browser widget android local file problem

[Alan]

Hi Jacque, Jonathan

Thanks for the replies and questions and sorry for the slow reply!. They did lead me to question whether my file was being created correctly - it wasn't. There also seems to be a difference in the way html files are loaded. Anyway, it works now.

Thanks for the info about the documents folder. That prompted me to look into the Android system structure so all a learning experience. Now getting up to speed with monitoring + debugging on the device + simulators. Whew.


Now I just came across another interesting problem - after bringing up the running apps on Android and swiping to remove one from memory, now when I go to run the same app again, it comes up with a black (blank) screen but "appears" to be running. Looking at logcat, I see that there's been an error with navbar.lcb, log as follows:


09-04 16:55:53.623: I/LiveCode(25535): errorDialog 863,0,0,runtime
09-04 16:55:53.623: I/LiveCode(25535): 864,0,0,error exporting foreign '<type: __builtin__.int>' value: numeric overflow
09-04 16:55:53.623: I/LiveCode(25535): 865,0,0,navbar.lcb
09-04 16:55:53.623: I/LiveCode(25535): 866,0,0,812
09-04 16:55:53.623: I/LiveCode(25535): Error: An error occurred on line: 0
09-04 16:55:53.623: I/LiveCode(25535): 863,0,0,runtime
09-04 16:55:53.623: I/LiveCode(25535): 864,0,0,error exporting foreign '<type: __builtin__.int>' value: numeric overflow
09-04 16:55:53.623: I/LiveCode(25535): 865,0,0,navbar.lcb
09-04 16:55:53.623: I/LiveCode(25535): 866,0,0,812

Wonder if anyone else has seen this and presumably it should be reported as a bug?

So many device differences are such a PITA.

Thanks again for your help!

cheers

Alan


> On 25 Aug 2017, at 12:27 am, <jonathandlynch at gmail.com>  wrote:
> 
> 
> Hi Alan - setting the htmltext of the widget works fine for me. My map data comes from Bing. What is going wrong when you do that?



> On 25 Aug 2017, at 6:52 am, "J. Landman Gay" wrote:
> 
> 
> Like on a desktop machine, the folders are located in different places 
> in the file hierarchy. These are actually virtual folders; they don't 
> really exist since the whole thing is done in memory.
> 
> If you aren't able to get results from the documents folder, I'd have 
> the script check first to make sure the file is really there.
> 
>