Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI have two threads on the Qt form addressing this issue, the members there say that WinMain is "included" in by linking to Qts DLL similar to the MFC. For example, see the last few posts here, http://developer.qt.nokia.com/forums/viewthread/8908/#51775. I am still a bit confused as I am working through the source. This is my first open source project that I am working on trying to understand. This is my main motive for doing what I am doing.
      singulars
    2. CO@Matthew: Qt works a little differently, as its built for multiplatform UI dev: it uses `main` for the program entry point (which is in your code), but on widows it will create its own pseudo '`WinMain`'(though it in fact it need not, it merely needs to ensure no console is created if none requested)requested)
      singulars
    3. COI now have two conflicting explanations. I know that #/link /SUBSYSTEM:WINDOWS /ENTRY:mainCRTStartup inside nmake Makefile allows you specify the entry point to be main( ) in a non-console application. However when you set up you WndClassEx you need an hInstance which is not provided if you use main. There is no other way to get a Window created. Also if you look through the source at Qt you see that WinMain actually calls your main function. So main is NOT the entry point to the program, it is just a convenince to non Windows Programmers. This is not so in linux which is called as the entry.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload