OS X Swipe Gestures broken

I have Logos set to notify me when updates are ready to download.

90% of the time, when I click on the 'download now' link that appears in a window to the bottom right of L4Mac, the window disappears, the download starts, and my 'four finger' gestures stop working. I can no longer switch between desktops. Two finger gestures (such as back a page in Chrome) are working fine.

This only seems to happen when using this one link in this one app ... and may happen as much as 100% of the time (I am just not sure).

I am using the latest RC, but this fault existed in the previous version at least (with a vague recollection of the one before that as well).

To clear it ... well I cannot!, other than restarting the computer. It does clear itself after 5-15 minutes but that seems to be related to some other program doing something that 're-initialises' the swipe. I have not worked out which app or what yet.

It has the feel of an event being claimed but not released, except that I cannot see why!

Has anybody else experienced this?

[edit] I can still switch between apps/spaces using the tab key and the dock. It seems to only be the gestures that are broken.

Find more posts tagged with

Comments

JT (alabama24)

Martin - I am sorry, but I am not following you. Can you be more specific? Can you provide a screen shot so that I can see what you are talking about? I would like to try to reproduce this, but I am at a loss.

Martin Folley

On a Mac track pad you can use gestures to switch between spaces/desktops.

This functionality stops completely after using the 'download now' link.

JT (alabama24)

On a Mac track pad you can use gestures to switch between spaces/desktops.

This functionality stops completely after using the 'download now' link.

I understand gestures. I dont understand the rest. To what "download now" link are you referring?

Thomas Ball

This functionality stops completely after using the 'download now' link.

The above is true after you run an automatically downloaded update, and until you reboot the machine (at which point the issue is resolved)?

Does this happen for resource updates or only version updates? Can you log the instance, and perhaps include the Console Log as well? http://www.logos.com/support/mac/L4/Logging

I've never noticed this on my personal machine, but I don't use the gesture in question very often. The next time there is an update, I'll try the gesture.

Martin Folley

To what "download now" link are you referring?

The download link appears in a small window in the bottom RHS of the screen when an update (code or resource) is detected. I cannot show it until I get an update but with the month starting tomorrow I am sure Vyrso will throw something my way [:)]

Martin Folley

To what "download now" link are you referring?

Martin Folley

Does this happen for resource updates or only version updates? Can you log the instance, and perhaps include the Console Log as well? http://www.logos.com/support/mac/L4/Logging

It just happened again ... resource only download, although I think that it happens with version updates as well.

I have attached my logs but am not sure if they include the 'console log'.

0385.Logging.zip

BTW. A separate incident that I mention because my logs are inbound ... since the Classic Corinthians earlier this week, my indexer seems to crash ... it starts and then after a few minutes disappears, only to restart when I next start Logos.

Thanks

Martin.

JT (alabama24)

Martin - Could you take a look at THIS THREAD and see if my results are the same as yours?

Martin Folley

Martin - Could you take a look at THIS THREAD and see if my results are the same as yours?

Done ... and posted there ...

Thanks.

Fr. Charles R. Matheny

Dear Tommy: Are you sure about that statement . Apple gives developers a lot of access to gestures and how they are applied.

If everything works "except" when logos is loaded, it's not a "OS" Problem but and interaction problem between Logos and the OS that is caused by something in Logos.

If the problem goes away when Logos is then closed, again we know it is logos specific. If it takes a few min. for the problem to clear, it may be something Logos is doing in memory and after memory is cleared, the problem is cleared.

Has anyone looked at memory usage when Logos is open and they try to use gestures, see if something spikes and stays?