QuickLook Preview fails since 1.2.9

Create issue
Issue #72 resolved
Alex Chandel created an issue

Ever since I updated to 1.2.9, Gapplin always displays a blank white rectangle in previews. I also notice I can't choose 1.2.9 in the Version dropdown.

Comments (11)

  1. Former user Account Deleted

    I have the same problem. It has been fixed but is back again. Unit tests missing?

  2. 1024 repo owner

    Hmm, thanks for the feedback and sorry for the problem.

    It seems I need to release 1.2.10. It will take a while.

  3. Former user Account Deleted

    Thanks. Any way to download 1.2.8 that first fix this issue before 1.2.9 re-introduces it?

  4. F1LT3R

    I am also seeing this same issue since updating Gapplin.

    While this is being fixed, could we add preferences options to change quicklook/finder-preview background?:

    • Color
    • Transparency
    • Background Image

    This would make scanning through SVGs in Finder/Cover-Flow a very nice user experience.

    At present, when there is a white SVG on a white background, nothing is seen in Finder. I encounter this a lot when making white icons that are placed on darker buttons to build scalable user-interfaces.

    It would be nice if we could set a semi-transparent background with a repeating image like this:

    Screen Shot 2016-02-08 at 5.13.49 PM.png

  5. 1024 repo owner

    Yesterday, I submitted a new Gapplin, v1.2.10, including this fix.

    @fdelage Sorry, but currently, I won't distribute Gapplin outside the MAS because of the limitation of my development time. The fix will be applied soon. Please wait for it.

    @F1LT3R That sounds interesting. Thank you for the suggestion. However, in order to apply this fix quickly, I didn't implement it on 1.2.10. I'm still not sure, what is the proper way to provide options for a quick look. It needs to be examined. So, I'll create a new issue for this feature later.

  6. Anbiniyar Muniandy

    I just noticed that the quick look is not working on El Capitan. Seems like you have fixed the bug and the next release should have it.

    Thank you very much!

  7. Log in to comment