| Issue 200: | UI issues in Lion | |
| 2 people starred this issue and may be notified of changes. | Back to list |
What Version of iTiVo? Version 1.7.7b3 (1.7.7b3) What Version of MacOS X? 10.7.4 OSX Server What download format did you select? DMG What steps will reproduce the problem? 1. Use iTivo on OSX Lion 2. Select an item from the list 3. Select another item and UI doesn't update selection Please provide any additional information below. Basically I am seeing lots of UI related issues, on two machines (a macbookPro, and a mac mini server, both running OSX Lion Server). I select a list entry, and the subscribe/queue/download buttons won't get enabled until I click on it again. The entry would not get selected until I click on it a second time. Sometimes these app would just not respond to clicks for a long time, then suddenly process those clicks in one go, as if they were queued. In all these cases, the processor is not being taxed at all, its always running at under 20%, and the iTivo process is not taking up any unusual amounts of memory or cpu cycles. The machine is connected through ethernet cables to a router which is again connected through ethernet cables to the Tivo (premiere) box. This kind of UI response really frustrates me, and makes the app completely unusable. Being a Mac developer myself, I downloaded the source but xcode4 cannot open the mainmenu.nib, and the UI interactions are written in apple script so I can't debug this issue using native debugging of the app myself.
Jun 6, 2012
Project Member
#1
tony1ath...@gmail.com
Owner:
tony1ath...@gmail.com
Jun 7, 2012
It looked quite complex!! I wish I had time outside work to help out. Maybe I will try playing around with a objC version in my free time and see how far I can get. I hope if you do find somebody else to do it, it will get posted to the svn repository that I could grab too :) Is the real exact cause known as well? Maybe there is a simpler fix? Any plans to upgrade the project to Xcode 4?
Jun 7, 2012
Yes, the full app is complex, but I'd be happy to start small and get that part right first. I'm very happy to collaborate. No, I don't know why the applescript is behaving badly. I tried debugging it, but was unable to make sense of it. Yes, if I do the Objective-C version, it would be with current Xcode and probably a 10.6 requirement. |