Results 1 to 6 of 6

Thread: WindowProc & Windows Apps

  1. #1
    denniswrenn
    Guest

    Question

    About a month or two ago, I was talking to a friend, who happened to be a very good C++ programmer. And he said that use of a Window Procedure can make your application very slow if you use a lot of controls, and most commercial apps don't use it, and my question is, if they don't use the window procedure method, then what do they use?


    Thanks,
    Dennis

  2. #2
    Guest
    No, I'm pretty sure he said apps that use a message loop and window procedure will get very slow if too many controls are added, and I think he was talking about dialogs as well as windows made with createwindowex.

  3. #3
    Monday Morning Lunatic parksie's Avatar
    Join Date
    Mar 2000
    Location
    Mashin' on the motorway
    Posts
    8,169
    I'm not overly sure about that either

    Maybe event handles play a part? As far as I can see, in every system I've programmed for (X, Win32, RISC OS), you always need a message loop to prevent the program from exiting.
    I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
    -- Linus Torvalds

  4. #4
    Guest
    well, the guy told me they may use their own framework.... whatever the hell that is..

  5. #5
    Monday Morning Lunatic parksie's Avatar
    Join Date
    Mar 2000
    Location
    Mashin' on the motorway
    Posts
    8,169
    I expect their framework is like MFC - keeps it's own internal message loop, and delegates the events to specific handlers.
    I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
    -- Linus Torvalds

  6. #6
    Guest
    huh?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width