Hi Tony,

Are you on a data plan or WiFi? When you normally open tiddlywiki.com/empty 
in your browser, how long does it take?

I'm wondering if some combination of a data plan and/or your remoteness 
from the main TW site may slow things down enough that the items don't 
immediately appear on your list. Unfortunately, if you navigated away from 
Q in the mean time, then it may not know how to add the download to the 
main list. I might have to prioritized persistence of the download manager.

empty-20190218014-17-29.html and empty-20190218014-17-18.html would have 
been the items downloaded. When you view them in your browser, are they OK?

TIDDLYWIKISTUB7383952824269779 is a stub file typically created when you 
navigated via the System explorer. I don't think it's the empty file unless 
it was created when you navigated with the system explorer. In general, you 
shouldn't be seeing the stub file. The stub files are temporary and get 
erased when the app reboots. Too hard to diagnose at a distance ;-(

Just to confirm, you say the two empties downloaded to your *internal* 
download directory? Do you have a SD card, and is it formatted as external 
or internal memory (Starting 7 (?) you have to tell Android whether you 
want your card to be formatted as though internal space -- giving more 
space for apps -- or as external space -- giving more space for shared 
MP3s, photos, etc.).

I might be able to manage swipe left to leave some day, but swiping from 
the list into the browser would be much more challenging.

Thanks!
-- Mark


On Sunday, February 17, 2019 at 7:41:39 PM UTC-8, TonyM wrote:
>
> Mark,
>
> Reviewing now quinoid-v0-0-6-190217a on Android 8.0.0
>
> Selecting Download tesat had no feedback so I soon had 2 downloading in 
> the background. Canceled one in the download manager, it is slow (but thats 
> ok).
>
> Found in the internal memory Download TW-files two empty files
> empty-20190218014-17-29.html
> empty-20190218014-17-18.html
>
> of 2.17MB in size
>
> Oddly I went to use back to close quinoid and I had to press three times 
> before it exited.
>
>
>    - No change to the wiki list, + and browsed to Internal > Downloads 
>    and TW-Files and opened one of the empty files, 
>    - Tap to open from list opens my two existing items and a blank 
>    screen, 
>    - swipe left to open one of my existing wikis, has a 1-3sec display or 
>    white, before it displays (unlike previously) - I think this is an 
> artifact 
>    of the mobile view, material theme, sidebar open.
>    - Empty wiki not appearing after time, but is now in list as 
>    TIDDLYWIKISTUB738395282426977923.html
>    - New download test whilst staying on wiki list screen (will report 
>    later)
>    - Will try geo-location soon
>
>
> *Question*
>
> Is there any reason we can't swipe left back to the Quinoid list, and 
> arguably swipe right to load/(re)view the open wikis? It may be a little 
> more intuitive.
>
> Regards
> Tony
>
>
> On Monday, 18 February 2019 13:46:00 UTC+11, Mark S. wrote:
>>
>>
>> Probably quinoid-v0-0-6-190217a.apk deserves to be in it's own release, 
>> but there's a lot that isn't settled yet. It has a new look, with "System 
>> Explorer" now activated through the "+" icon and "File Explorer" activated 
>> though the overflow menu. On the new overflow menu is also a download 
>> option, that is meant to download an empty TW from tiddlywiki.com. This 
>> is in preparation for offering users the chance to quickly load up on 
>> well-known and crafted TW files.
>>
>> It's testing on the download functionality that interests me. I'm only 
>> able to test through emulators at the moment, and they give me inconsistent 
>> information on multiple levels. One emulator works great. Another gives the 
>> "OK", but then says there's something wrong with the file system, and then 
>> chooses to put the file somewhere else and with a nonsensical name.
>>
>> What I'm trying to do is to save to a sub-directory of the user's *external 
>> *download directory. This way the user can be in charge of deleting and 
>> cleaning up. If people are willing to test, they should have an android 
>> with an external card, preferably with an existing "Download" directory. 
>> After running the download menu option, the new item should appear in your 
>> browse list. Unfortunately, at least on one emulator, it's possible that it 
>> will instead write to the download directory of the internal card, using a 
>> name that won't even look like a standard html file name. I don't know if 
>> this is for real, or just an anomaly of the emulator. 
>>
>> If you have a slow connection and have to log out of quinoid before the 
>> download is complete, then it's possible that the download will complete 
>> later but not appear in your list. In my tests, with WiFi, this wasn't a 
>> problem as the download was almost instantaneous. There's a bunch more 
>> coding I would have to do to prevent the non-listed download situation. But 
>> first I want to know how well the downloading works at all. It's another 
>> question whether I should prevent downloads except when connected to WiFi. 
>> Possibly a user configuration.
>>
>> @Tony  -- I added some additional geo permissions to the v0.0.6 update. 
>> Curious if that made your geo-json file work any better. These additional 
>> permissions may be why TT was getting additional quizzing by the 
>> PlayProtect system.
>>
>> Thanks everyone -- be sure to backup and take precautions if you try the 
>> release!
>>
>> -- Mark
>>
>>
>>
>>
>>
>>
>> https://github.com/Marxsal/Quinoid01/releases/tag/v0.0.6alpha
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0625dd51-48f2-44a6-a8dc-682d734ab8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to