I also have a HUNCH that it may have to do with going from dual screen to single screen and back to dual screen mode while Skim is up and running (and perhaps bridging the gap between the two monitors).
Again, I haven't been able to reproduce the error after the one time I've seen it, but I know it happens on my officemate's computer pretty frequently. --Ted Ted Pavlic wrote: > (I have sent a screen grab over direct e-mail) > > Additionally, I notice today that *I'VE* started to have a similar > problem. I go full screen (or presentation) on my secondary monitor, and > the full screen seems to be SHIFTED up about 1/4 of the screen. That is, > even when I've "zoomed" Skim to fill the screen and only the screen, > when I go "full screen" the bottom of Skim shows up about 1/4 up from > the bottom of the screen and the top of Skim isn't visible. That is, the > rounded eges of the bottom of the side panel drawers can be seen, but > not the top. > > If I go back to normal mode and then drag the window into the primary > display, do a full screen, go back to normal and drag it back to the > secondary display, things work fine. > > I've tried restarting Skim so I could duplicate the error and send a > screen grab, but I cannot duplicate it at the moment. If I do, I'll send > something along (over direct e-mail). > > --Ted > > Christiaan Hofman wrote: >> BTW, would it be possible to make a screenshot of the screen when it >> goes wrong, and send it to the list or to me? >> >> Christiaan >> >> On 8/9/07, *Christiaan Hofman * <[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> Very strange, if anything I would have expected the opposite ( i.e. it >> going right the first time, and wrong when you move to another >> screen). I can't see anything possibly wrong with the code, we even >> seem to be doing more fixing of the screen rect than we actually >> should be doing. If I can understand more of what's going wrong I >> could file a bug report with Apple, because I can't imagine it's >> going wrong on our end. >> >> Christiaan >> >> On 9 Aug 2007, at 9:50 PM, Ted Pavlic wrote: >> >> > Additionally, moving the document from the secondary display to the >> > primary display, THEN going full screen, THEN moving the document >> back >> > to the secondary display and going full screen will make things work. >> > >> > So, there appears to be some strange bug under certain resolutions.. >> > >> > --Ted >> > >> > Ted Pavlic wrote: >> >> UPDATE: >> >> >> >> His (and my) primary resolution: 1440x900 >> >> >> >> His secondary resolution: 1600x1200 >> >> >> >> WHEN HE CHANGED his secondary resolution to 1400x1050, things >> started >> >> working. IN FACT, changing things BACK to 1600x1200 made things >> start >> >> working again at THAT resolution (however, the left and right bars >> >> only >> >> spanned about 3/4 of the screen rather than the full screen). >> >> >> >> NOTE: My secondary resolution is 1280x1024. I've never had any >> >> problems. >> >> >> >> NOTE: We have not played around with changing the relative virtual >> >> position of his two monitors. >> >> >> >> --Ted >> >> >> >> Ted Pavlic wrote: >> >>> I don't have this problem, but my officemate does, and he's >> >>> running a >> >>> nearly identical setup as me. >> >>> >> >>> Both of us have Powerbook G4's connected to external monitors >> >>> (mine is >> >>> LCD; his is CRT). We are both stretching our desktop across each >> >>> monitor >> >>> and keeping the main desktop on the Powerbook's screen. We both >> >>> edit our >> >>> LaTeX on our PowerBook and display our PDF with Skim in the >> external >> >>> monitor. >> >>> >> >>> On my machine, full screen and presentation mode both work. >> >>> >> >>> On his machine, both modes produce a grey rectangle stretching >> >>> 3/4 up >> >>> the screen and 1/10 across the screen starting in the lower-right- >> >>> hand >> >>> corner. In full screen mode, his sidebars properly show up on the >> >>> left >> >>> and right. >> >>> >> >>> Has anyone else had a similar problem? >> >>> >> >>> On top of this, things worked fine when he first started using Skim >> >>> (which he thinks was Skim 0.5.1). However, at that time he was >> >>> using a >> >>> different monitor (an ancient HP CRT). >> >>> >> >>> Thoughts? -- >> >>> Ted >> >>> >> >> >> > >> > -- >> > Ted Pavlic <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> >> > >> > >> ---------------------------------------------------------------------- >> > --- >> > This SF.net email is sponsored by: Splunk Inc. >> > Still grepping through log files to find problems? Stop. >> > Now Search log events and configuration files using AJAX and a >> > browser. >> > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > _______________________________________________ >> > Skim-app-users mailing list >> > [email protected] >> <mailto:[email protected]> >> > https://lists.sourceforge.net/lists/listinfo/skim-app-users >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Skim-app-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/skim-app-users > -- Ted Pavlic <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
