I thought I could leave it by my last comment here, but I am a bit annoyed of some things, Jim:
1. You always start unnecessarily long discussions and you mix several topics into one thread. 2. You ignore what we tell you. (In this thread you said trying on your "new" profile didn't fix the issues. Now you reset your profile and the bugs are suddenly gone. You created <http://code.google.com/p/fbug/issues/detail?id=6261> issues<http://code.google.com/p/fbug/issues/detail?id=6262>for things that are already reported after you where told<https://groups.google.com/d/msg/firebug/ANP6CjNiDGE/CAbhnPuwta8J>that they are already there.) 3. You never create reproducible test cases. (see e.g. issue 5616<http://code.google.com/p/fbug/issues/detail?id=5616> ) I'm tired to repeat myself again and again. So here's the info the last time: If you experience bugs in the future or have a feature suggestion, read and follow the related instructions what to do in these cases first: https://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug! https://getfirebug.com/wiki/index.php/I_am_missing_a_feature_in_Firebug! https://getfirebug.com/wiki/index.php/Creating_a_Test_Case https://getfirebug.com/wiki/index.php/Rules_for_the_issue_tracker If you post your issues then and you don't provide the necessary info to reproduce your issues, I'll just ignore them from now on. Sebastian On Monday, February 11, 2013 8:46:22 AM UTC+1, Sebastian Zartner wrote: > > Sounds like everything is working now. Congratulations! > > Sebastian > > On Monday, February 11, 2013 12:47:39 AM UTC+1, Jim Michaels wrote: >> >> the "cache" problem was me not ftp'ing my code like I should. :-/ agh. >> the error lines was really weird. >> got my group calendar working now. >> >> On Sunday, February 10, 2013 2:13:04 PM UTC-8, Jim Michaels wrote: >>> >>> some of the problems with scrolling seemed to go away when I reset my >>> profile using about:support. but all the rest of the problems (caching, >>> error lines consistently reported wrong, etc) aree still there. >>> interesting. basically, I got tired of the issues, and just decided to >>> scrap everything and start over after backing up my bookmarks. >>> I lost my plugins, and everything. so it's like starting over from >>> scratch with fresh new firefox. >>> >>> On Tuesday, February 5, 2013 2:43:38 PM UTC-8, Sebastian Zartner wrote: >>>> >>>> I tried to reproduce your steps on FF 18.0.1 + FB 1.11.1 on Win8 and I >>>> still can't reproduce your issue. >>>> >>>> 6.go to function NamedTimeStringToDTime and put breakpoints on every >>>>> instance of GetIntegerKeywordPair() and StringDateTimeToDTime(). 174, >>>>> 978, >>>>> 1850,1851,1882,1883, 1937,1945,1949,1956,1958,1967,1975,1979,1989,1997, >>>>> 2012,2020,2024,2043, >>>> >>>> I assume these numbers should be the line numbers of the calls to >>>> GetIntegerKeywordPair() and StringDateTimeToDTime(). Though the only >>>> calls to these functions are in line 1920, 1940, 1970, 1992 and 2015. >>>> >>>> Anyway, I assume your problem doesn't lie in the slowness of your PC >>>> but may be caused by problems related to your graphics card. So please >>>> turn >>>> off hardware acceleration by unchecking *Tools > Options > Advanced > >>>> General > Use hardware acceleration when available*. Does the problem >>>> go away? If not, please update your graphics card driver and try it again >>>> with and without that option being checked. >>>> >>>> Sebastian >>>> >>> -- -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at https://groups.google.com/forum/#!forum/firebug --- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
