Open GoogleCodeExporter opened 9 years ago
Same thing here, 0.7.0 on Leopard, powerpc.
Original comment by olof.joh...@gmail.com
on 27 Apr 2008 at 9:03
Same issue here 0.7.0 10.5.3 intel
Original comment by mikea...@gmail.com
on 14 Jun 2008 at 2:15
Same Issue here 0.7.0 OSX 10.5.3 Intel occurs after resizing of screen
Original comment by Mackenzi...@gmail.com
on 16 Jun 2008 at 9:26
try removing prefs and turning off toolbar, to see if it helps bring buttons
back. I
have reproduced that error message here. I'll see what I can do.
Original comment by johnsolo...@gmail.com
on 18 Jun 2008 at 10:44
0.7.0 and 10.5.3 .... stopped app removed
$home/Library/Preferences/tivotool.conf and
started it up and it remembered all my details, and problem still occured. is
this
the correct file?
Original comment by grantfstreet@gmail.com
on 3 Jul 2008 at 3:26
I continue to have this problem as well. I've deleted and reinstalled Tivotool
and
the prefs file. Is there a configuration we can manually adjust in a file
somewhere
to keep the show listing from extending down over the buttons? I think the
problem
occured when I expanded the list to fill the height of my screen - it doesn't
seem to
readjust when you shrink the window back down to show the buttons.
Original comment by andrew.e...@gmail.com
on 9 Jul 2008 at 2:36
I get the same every time.
Simply delete
home/Library/Caches/listings (i think its just a text file)
before next time you oven TT and menu bar (and scroll bar) will be back
Original comment by sam.marc...@gmail.com
on 26 Jul 2008 at 1:38
WORKAROUND
doing a
rm ~/Library/Caches/listings
gets the display working again for me ..... Thank you!!!
Original comment by grantfstreet@gmail.com
on 5 Aug 2008 at 12:57
Just upgraded to Snow Leopard. Installed Rosetta, but TivoTool crashes shortly
after it launches. No windows
open, so nothing to show. Worked OK (with bugs listed above ) under Leopard.
Anyone know of other software that does the same thing?
Thanks
Original comment by breaba...@gmail.com
on 8 Sep 2009 at 4:14
Original issue reported on code.google.com by
pinhe...@gmail.com
on 24 Feb 2008 at 10:56Attachments: