Right, I’ve looked into this. Different programs take a different approach to full screen - generally, there are two different ways of doing it:
You can hide the menu and dock and then create a normal borderless window that fills the screen.
You can create a borderless window that fills the screen and assign it a window level of screensaver+1 - this will force the full screen window to cover the dock and the menu bar, which are still there underneath.
Scrivener, WriteRoom and Jer’s take the first approach; Ulysses and MacJournal take the second (as far as I can see).
Each approach has advantages and disadvantages. You have found the main disadvantage with 1) - it doesn’t play so well with Expose and the dock will remain hidden when hitting F9 or F10.
However, I believe that the advantages of 1) outweight the disadvantages - I find the behaviour of 2) much more “buggy”. For a start, using 1) you can have the menu bar pop down when you place the cursor at the top of the screen - you can’t do that with the second method. But the main problem with 2) is that because the window is set over the top of all others, panels will get hidden - they cannot pop up over the top of the full screen window unless they are assigned a higher window level. For instance, in MacJournal, whilst in full screen, hit Cmd-2 to show the calendar - it won’t show up. If you exit full screen, however, you will see that it was called up, but it just couldn’t be shown over the top of the full screen window. Or, in Ulysses, hit Cmd-F to do a find in full screen - the Find panel will not appear. If you exit full screen, you will see that the find panel was, again, called up, but it couldn’t show itself above the full screen because of the window level setting - in other words, in Ulysses, you can’t actually do a Find in full screen mode (in MacJournal, I see they have tried to get around this by implementing a different, “full screen”, find, which is much more basic than a normal find). Now consider how many panels Scrivener can display in full screen - you can see the find panel, you have the HUD panels, the snapshots panel and so on and so forth - all of these would get obfuscated by the full screen window if I took the approach of MacJournal and Ulysses.
So, this is a “swings and roundabouts” one, but the benefits of the current implementation outweigh its problems. Given that full screen modes are becoming more and more standard on the Mac, it would be nice if Leopard made their implementation easier and standardises behaviour, allowing some way of defining Expose behaviour etc… We’ll just have to see.
Anyway, I hope this explains why the current behaviour will remain, warts and all, and why there is not much I can do at this time.
Thanks and all the best,