There sure is a way. The approach would depend on how you structured the journal.
For the most basic of setups, you could have an int variable indicating which page the drawing is on (Page with Drawing). A *Branch *in the *onPaint *checks whether we’re on page 3 or not (Current Page We are On). Something along the lines (ehm) of:
[HR][/HR]
If there is more than 1 page with a drawing, one could create a dictionary map that holds [page number | array of lines]. As in:
You can write to this map and store it easily in a save game. And the struct the map holds (here, sLines) can store more stuff - like EVERYTHING that’s on that page, for example 
[HR][/HR]
If the journal is a more complex beast, perhaps the pages should be separate widgets that live inside a widget switcher (so when the player flips through them, you do not need to recreate every page from scratch every time). In a case like this, you could check if the array of point the page stores is larger than zero.
Essentially, every page widget can be painted on (which can also be a controlled with variable the page holds) but only shows the lines if there are any to show. [HR][/HR]
For even more advanced stuff there are lists- for when you must have a *Skyrim *number of fancy books with dozens of pages each but do worry about performance / memory footprint.
Do tell if this makes sense.