Journal files and screen size/resolution

[Danny Polkinhorn]

I was talking with Steve Burri yesterday about a journal file that wasn't restoring a model. Basically the journal file records the location of the cursor as you're working. The cursor location is based on the screen image and not on real coordinates in the model. Therefore, if you change your screen resolution or maximize/restore the Revit application during your session, you could cause the journal file to not work. So if you rely on your journal files, make sure you leave your screen as is during the session. Steve, correct me if I'm wrong, but Revit does track changes to individual views, maximize, tile, etc.

Hope that helps,

[LRaiz]

This is not accurate; journal files were designed to be re-playable even if screen resolution is changed. I may shed some more light on it.

Journal file mouse xy information is indeed recorded in terms of pixel coordinates (resolution dependent). However journals also record viewing matrices and during replay Revit never uses pixel information directly. It first transforms pixels into model coordinates using recorded viewing matrices. This approach allows to avoid dependency on either size/position of overall Revit window or screen resolution. Factory takes advantage of this design by being able to reproduce bugs and run automated regression tests regardless of screen resolution on a machine that was used for journal recording.

If you run into an example when screen resolution is the definitive reason for journals becoming non-replayable then you probably encountered some bug but not an overall design limitation.

HTH,

[Danny Polkinhorn]

Leonid,

Thanks for the response and clarification.

The journal file in question would move around the screen (after opening the file) start the dimension command, and on the first click, it missed an object and failed. We assumed that it may have been because of a change in the screen status. Of course, we all know what happens when we assume.

Thanks again for clarifying.

[FK]

Either you upgraded to another build or the file the journal's working on is not identical to the file the journal was recorded on.