BUG: OSX Swipe Gestures after "Update Now"
At least two other users have reported similar issues (see HERE and HERE) as early as December of last year. I have not experienced this until today...
This afternoon when I used the command update now, the 3 finger swipe gesture to move between desktops stopped working. I was able to use mission control to switch between desktops. After 5-10 minutes, without any action on my part, the gestures began working again (I was letting the app finish indexing). This behavior repeated after using update now again. Closing the app did not fix the problem for me. I enabled logging and tried to replicate the behavior, but everything worked as expected. If I experience this again, I will post logs.
I am currently using 4.5c beta3.
Comments
-
I remembered that my download had not yet happened on my second install, so I enabled logging and tested the update now command. The issue DID happen to me on the second install, but it only lasted for a couple of minutes.
I am waiting for the app to finish indexing. I have to run out, but I will try to post logs when I get back.
EDIT: While it was indexing, I tried update now again. At first, the problem did not occur. Once I clicked on the "no updates" box, however, the issue returned. This is consistent with my other install.
EDIT 2: I just want to remind myself to create another post... The indexer did NOT require a restart before it began after download. This was a 24 MB download (Anabaptist).
EDIT 3: While indexing, the 3 finger swipe did not return (going on 5 minutes)
0 -
My logs are posted below. When I returned home, the indexing had finished, 3 finger swipe still did not work. I closed the app, got the logs. It took about 5 minutes, but the 3 finger swipe did return.
0 -
I am able to replicate this behavior more consistently on my MacBook Pro than I am on my iMac. When I run the command update now, everything is fine until the point where I try to close the "No Updates Available" box (shown below). The problem will persist until 5-10 minutes after Logos has closed.
0 -
I discovered another interesting thing...
When you click on the header (not the tabs or any other graphical area) of Logos or any other app (i.e. finder; iCal; Word; Safari, etc.), the gesture will begin to work again. Tommy wrote earlier today that this was an Apple problem and not a Logos one. It seems to me that it might be a little bit of both. However Logos is creating the floating window for the "No Updates Available" is clearly causing problems under certain circumstances with the multi-touch gestures in OSX Lion. Tommy's statement seems right to me that what is happening when you click on the box is outside of Logos' control… but perhaps how you create the box is not out of your control (and hence a bug)?
Again, I am now able to replicate this constantly on my MacBook Pro, but not my iMac, although I have experienced this on that machine as well.
0 -
Hi Alabama
I agree with all that you have posted above, they match my experiences.
Thanks for the effort that you have put into this one (and many many other issues as well).
The discovery of the click in a 'non-graphical' area solution is interesting ...
I concur that, in my experience, there is only one application that regularly triggers this behaviour ... L4Mac. That the issue occurs may be an apple API issue ... but how L4Mac has used that API, or whatever else is going on under the hood with L4Mac, something is different to every other app ...
Currently, I have stopped using even the stable version of L4Mac completely. The issue above is an annoyance. The constant indexing crashes and regular app crashes is more than that. Coupled with the low speed and lack of features relating to notes/highlighting means that I am forced to use the windows version under parallels, (Same hardware, snappy performance, stable program). It really feels like the mac version was dropped whilst carrying it across the workshop, they have sort of put it back together, but they have some pieces left over!
2017 15" MBP, iPad Pro
0 -
-
This response from Tommy in one of the other threads you referenced is the only answer I've ever received from a developer when asked about this issue (more or less) and I've asked several different people on a few occasions. So, just so you know, Tommy's answer, in essence, is coming from development.
That being said, I am creating a case for this issue as one more 'Are you sure?' checks with development. Too much more of that and I'm going to start feeling like Denholm Reynholm. (<- IT Crowd reference) [;)]
0 -
-
-
-
This issue should be fixed in the next program update.
Are you sure? Are you sure? Are you sure? Are you sure?
Don't you people know that swiping is strictly forbidden (Ephesians 4:28)?
0 -
