nanogallery2 v0.9.2a (31 January 2017) bug with glass - nanogallery

I use nanogallery2 (v0.9.2a - 31 January 2017).
There seems to be a bug.
When you click (quickly) 5 or more times on the magnifying glass "+", it is impossible to retrieve the basic image using the magnifying glass "-".
Same when zooming on a smartphone screen...
Can you help me to fix this bug please?
Is this a bug in the version?
Help me please.
Thank you in advance

When you click/tap quickly on the zoom in/out buttons, the lightbox interprets this as a double-tap.
Double-tap enables/disables zooming on the image. So the weird effect.
This issue is fixed in nanogallery2 v0.9.3 v1.0.0
[EDIT]
Zooming is not working in v0.9.3 in case of self hosted images.

Related

Lighting doesnt show in blender 2.8 render tab

I cant seem to get my lighting to work in the render tab.
I have lights in it and they have a high strenght yet it doesnt show anything.
Im kinda new to blender so apologize in advance if the answer is obvious
Image
Bro do this open viewport shading in the top right corner beside of solid, preview, rendered and turn on scene light

Strange drawing on iOS map when working with MKPolyline

In our app we are connecting GPS coordinates from the position of a user. When we are connecting the lines, it sometimes appears that there is a strange drawing happening. I mean the blurry red color thing on the right of the picture below. Did anyone experience this problem before? Might that be an iOS bug? By the way: It disappears when I reload the map. Management is asking me to fix it but I guess I have no influence here. Any thoughts?

PHPStorm presentation mode left margin

Any idea how I can customise the size of the left hand margin when in presentation mode?
On a 27" monitor this is absolutely huge!
I've had a look through the settings and couldn't find anything, any ideas?
Thanks for your time.
Known issue -- please vote/star/comment to get notified on progress (hopefully will be fixed for v8):
http://youtrack.jetbrains.com/issue/IDEA-126090

WinRT Surface DirectX Black Screen

I'm having a strange and irritating problem on WinRT Surface tablet when using DirectX (hosted in BackgroundSwapChainPanel). Basically once in a while (like once a day, or few times a week / while testing for few hours every day), half of my 3D scene goes black, like on the picture below (cut vertically or sometimes horizontally):
http://www.zurawcli.vot.pl/dxProblem.JPG
While this happens, the DirectX is still rensponsive and i have full control of the app.
I don't think posting code makes any sense ( i'm simply using standard SwapChain and resizing viewport and back texture whenever screen size changes - actually getting screen size from Core Window). This only happens once in a while : ( when i try to explicitly force this - like by splitting screen between two / switching between apps / and so on, I CANNOT repeat this error - viewport always resizes correctly. Then sometimes just using the app, this will happen.
Did anybody had any experience similliar to this ? Any ideas what is causing this ?
Thanks in advance,
cheers

chrome, cy.js 2.1.0: nodes disappear with mouse motion

macos 10.7.5
chrome Version 32.0.1700.107
Version 32.0.1700.107
and the simple "single.html" helpfully provided by gcpdev:
live code examples: cytoscape.js initialization -- incomplete?
Any movement by the mouse in the canvas makes the nodes disappear. zooming and and out (with middle mouse roller button, for instance) makes them visible.
This problem is only on Chrome. Firefox and Safari work fine.
Any suggestions?
Thanks!
Paul Shannon
I can't reproduce this on Mac OS 10.9 with Chrome 32, which probably indicates this is a problem with Chrome rendering canvas on that version of Mac OS.
I notice that the linked demo is using v2.0.2. Have you tried an updated v2.0.x release or v2.1.0?
Try using pinch-zoom to set the zoom level for the webpage (not for the Cytoscape canvas element, which has its own separate zooming operated by scrolling with two fingers on the trackpad) to 100%. This fixed it for me, based on this question and this github issue, both about an almost identical issue in Firefox.