Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have done something like this, so I can offer a few bits of advice.</p> <ul> <li><p>While it would be okay to call your Window classes MSWindow, OSXWindow, etc., this is really not handy, since every part of the code that ever needs to interact with the Window will need to know which one to use. You should call these classes just Window. Since you will only be compiling one of these in a given platform there is no collision.</p></li> <li><p>The macros to check for a given OS:</p> <ul> <li><code>_WIN32</code> for Windows</li> <li><code>__APPLE__</code> for OSX and iOS (I set my own constant to tell these two apart in the pch file )</li> <li><code>__linux__</code> for Linux</li> </ul></li> <li><p>I recommend that you do not add <code>#define</code> with the above all over the place. You'll have more portable code if you put the cross-platform specific code in as few places as possible.</p></li> <li><p>You will have different main functions on each platform. <code>WinMain()</code> on Windows, <code>main()</code> on others. I recommend that you put these on different files, and you only reference the file that corresponds to correct platform in your makefile or project file.</p></li> <li><p>The HINSTANCE problem that you asked is easily solved. In your WinMain() function you will give the HINSTACE to your Window class. The Window class on Windows will have a static method, let's say <code>setHinstance()</code>, that will store the HINSTACE away in a class variable. Then when a Window instance is created, the HINSTACE will be available without having to change the common methods of this class.</p></li> <li><p>As a final comment, you should keep in mind that there are several GUI frameworks that are cross-platform that may work for you. If you want a full featured one, then look at <a href="http://qt.nokia.com/products/" rel="nofollow">Qt</a>. If you want one that is very simple to use (with some nice features, but not as many as Qt) then have a look at <a href="http://www.fltk.org/" rel="nofollow">FLTK</a>. Both Qt and FLTK are open source.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POPlatform Independence with C++. Detection and Compilation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMiguel
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTo elaborate - your platform-specific code should be segregated into as as few platform-specific source files as possible, and those files should each be in their own platform-specific subfolder. You'll also have a platform-specific "Makefile" (or equivalent, depending on your build tools) for each.
      singulars
      1. PO
      1. USpaulsm4
    2. CO@Miguel & paulsm4 Ok so just to be clear, are you saying I should have one class called Window and the #ifdefs are peppered in that one class to handle the differing functionality? To the outside application, it always interacts with a Window class using the common non-platform interface. And inside a single function may have three separate implementations guarded by the #ifdef blocks. Any platform specific types would be set on the class previously so as not to have any platform specific types in the function signatures?
      singulars
      1. PO
      1. USJon
    3. CO@Jon: if you have two or more implementations of the Window class for different platforms, then each individual implementation does not need any #ifdefs. As long as you have a set of common platform agnostic methods implemented in all your Window classes that are public and available to the application you won't need any #defines at all! Using #defines makes code difficult to read and maintain, you may not be able to avoid it completely, but as paulsm4 said, keep it to a minimum.
      singulars
      1. PO
      1. USMiguel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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