Skip to content

v83.0.7649.30836 (**unpublished**)

Pre-release
Pre-release
Compare
Choose a tag to compare
@GerHobbelt GerHobbelt released this 13 Jan 01:10
· 664 commits to master since this release
v83.0.7649.30836
179476c

Qiqqa release specifically targetting the issues jimmejardine#288 & jimmejardine#283 :

New

  • option to point Qiqqa at a different base directory (where all libraries are stored) in the startup dialog screen. This change will be persisted: when you quit Qiqqa and restart it later, it will have remembered the directory you pointed it at the last time around. (Technically: path is written to Windows registry)

  • extra logging to help diagnose some particular issues.

  • unrelated: work done the sync dialog: all libraries (except imported 'Qiqqa Bundles' -- which are zipped archives, really) are now fully syncable.

    • new is the [browse] button for each library in the sync dialog, where you can pick a new directory (anywhere on any disk your machine can access; doesn't have to be a Google Drive or DropBox or other cloud storage directory, it can also be another local disk or USB bay) to sync to/from.

    Known issues

    • hand-editing the path is not working in UI; changing the sync path is only doable via the [browse] button next to it.
    • while all libraries (including detected Qiqqa Cloud and other ex-v79 Commercial Qiqqa library types) are now re-dubbed "Intranet Libraries", the checkboxes 'autofill' for full and partial ssync are still a little crazy, flagging only very particular libraries instead of being sensible and only flagging the ones which HAVE a target directory.
    • you CANNOT reset the sync directory to NOTHING ('(null)') yet. (Largely because hand-editing that path doesn't work in the UI)

Who may benefit from this test release too?

Anyone who wants their libraries to be syncable/sharable in the new 'open source' world of Qiqqa where the old commercial cloud access is not available any more. Note the Known Issues above: usability is not top notch, but at least you now have the chance to do this and use the sync facility, instead of having to wait until the UI has been cleaned up.

What if I don't like this release's behaviour?

Step 1

Please report an issue, be prepared to send me the zipped logfiles (so that I can have a look at what happened under the hood and get a hopefully better idea about what went wrong and thus help us all to get the software to behave properly. Often ZIPping the logfiles still produces a rather large ZIP file, which is too large for email. Please consider sending me a link to Google Drive or similar web storage where I can download your ZIP file when you've sent me a link to the one. Please DO mention Qiqqa and the issie number (plus issue titlee) in your email subject line so my gmail spam filters will consider your mail as probably okay and thus less risk of 'loss in transmission'.

Also be sure to write a comment in your github issue that you have sent me an email for the case where it does end up in the spambox: if I read you have seent me something, I can specifically search for it and dig through both spambox and busy email folders. Sometimes gmail drops qiqqa stuff in the oddest places, despite me filtering on qiqqa.... Weird but it happens. Thanks for your cooperation and I hope you will get a gradually improving experience with the application.

Step 2

Download the installer for another version of Qiqqa (at the time of writing the preferred one would be: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v82.0.7568-29227 as also mentioned/explained here: jimmejardine#282

Assets 3
Loading