![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
As it turned out...
Jul. 19th, 2011 10:42 pmNo work came in this morning, and after a "microburst" of getting a number of small tasks done, things started to settle into a mood of quiet marching-in-place, as the handymen in our phone list turn out to be either jammed with work or otherwise not available. Finally, in the early afternoon, Galina suggested we go to Pearland, to look up an old contact there.
I decided to stick around the house and finish off some tasks, and it was a good thing, too, because a few minutes after Galina left, enough rush work came in to make the day look, well, at least semi-reasonable in terms of billing. I then "turned to" on my other tasks.
One of them involved vetting a list of words for Memrise, a site I have high hopes for. To do this, I had both Multitran open on my PC and Lingvo open on the iPad. Everything went well until something happened to cause my iPad's "home" button to change its behavior, and rather erratically, at that.
Up to this change, a momentary press of this button was all that was necessary to get a response. Now, I had to press the button for some period of time to get the same response, and nothing I could do would mimic the double-press behavior that pulls up what is effectively a list of active background applications. At first, I thought it might have to do with too many such background applications being open, but the only way I knew of to get at them was the double-press trick. Eventually, I managed to cause the background applications to display. I closed a bunch of them, but that didn't help.
So I went online and I did everything suggested in the Apple forums, but nothing worked. I even upgraded to the latest version of firmware, but that didn't help, either.
Finally, I coaxed the background applications to show up again, but this time, I relentlessly terminated all of them, including Lingvo (which I hadn't killed the first time because I still needed to use it).
And the problem went away.
I don't know if it was Lingvo, per se, or whether it was a combination of Lingvo and trying to persuade the Bluetooth keyboard to type in Cyrillic—or perhaps it was something else entirely—but the problem appears to have gone away. I am not complaining.
Cheers...
I decided to stick around the house and finish off some tasks, and it was a good thing, too, because a few minutes after Galina left, enough rush work came in to make the day look, well, at least semi-reasonable in terms of billing. I then "turned to" on my other tasks.
One of them involved vetting a list of words for Memrise, a site I have high hopes for. To do this, I had both Multitran open on my PC and Lingvo open on the iPad. Everything went well until something happened to cause my iPad's "home" button to change its behavior, and rather erratically, at that.
Up to this change, a momentary press of this button was all that was necessary to get a response. Now, I had to press the button for some period of time to get the same response, and nothing I could do would mimic the double-press behavior that pulls up what is effectively a list of active background applications. At first, I thought it might have to do with too many such background applications being open, but the only way I knew of to get at them was the double-press trick. Eventually, I managed to cause the background applications to display. I closed a bunch of them, but that didn't help.
So I went online and I did everything suggested in the Apple forums, but nothing worked. I even upgraded to the latest version of firmware, but that didn't help, either.
Finally, I coaxed the background applications to show up again, but this time, I relentlessly terminated all of them, including Lingvo (which I hadn't killed the first time because I still needed to use it).
And the problem went away.
I don't know if it was Lingvo, per se, or whether it was a combination of Lingvo and trying to persuade the Bluetooth keyboard to type in Cyrillic—or perhaps it was something else entirely—but the problem appears to have gone away. I am not complaining.
Cheers...
