We're getting there... at the moment, I need to move the keyboard handling code. Windows won't dispatch messages to the window proc of a window that isn't shown (or it could just be another bug in fractint I've introduced somewhere). I had designed the text/graphics switch to work like this: frame window + | +--- text window | +--- plot window The intention was to have all the text I/O code localized to the text window and the graphics I/O localized to the plot window. Switching between text and graphics modes amounts to showing and hiding child windows. The frame window would ultimately contain things like a menu. The plot window would ultimately contain scroll bars, but the first cut was just to have it fixed at the video resolution size. So I had all the keyboard code working in the text window and then when I hide it and display the plot window, my keyboard input stopped working. So I'll move the keyboard code from the text window over to the frame window. That will divide the handling this way: keyboard input, mouse input: - frame window text output - text window graphic output - plot window We might have GDI output going next weekend, we'll see how it goes. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
Rich wrote:
We're getting there... at the moment, I need to move the keyboard handling code.
Hmm, I wonder how did Bert's Winfract (not to mention Xfractint) solve this? They both had separate text and graphics windows. You've certainly been productive, I've been following along via CVS <g!> Tim
In article <45A41022.26461.11FB1C7@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:
We're getting there... at the moment, I need to move the keyboard handling code.
Hmm, I wonder how did Bert's Winfract (not to mention Xfractint) solve this?
I can look at the WinFract code, but at the moment, I'm sharing more code with fractint than with winfract. WinFract, IIRC, modified the entire main loop. Xfractint has a different event model in that you subscribe to events and they are sent to you as long as they are generated. Windows has a "here's every event, tell me if you processed it" model. Its not a big deal, really, just something I need to spend a little time on working out.
You've certainly been productive, I've been following along via CVS <g!>
:-) -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
participants (2)
-
Richard -
Tim Wegner