March 11, 2009

• Optimization demonstration code sample and timing routine
• Thread test demonstration files
  
• Threads (why is my interface freezing?)

• Custom Qt Dialog "template" files and Qt MenuDialogDemo Sample Files
• Assignment 10 is now available, and for those of you working ahead, it contains additional details concerning the computational work.
  

March 2, 2009

• DLL's What, Why, How
• DLL sample
• Today's (Monday) office hour has been moved from 3-4PM to 2-3PM.

February 24, 2009

• Pre-processor Directives

February 24, 2009

• There are two bugs in CAMsymfun. One is a a bug that may cause an application to crash if initialize(..) is called repeatedly and the other a bug causes an application to crash if an expression ending in an operator is used to construct or initialize an CAMsymfun instance. Both bugs have been fixed and the repository has been updated. You'll need to pull a new version from the class repository followed by an update (e.g. cd to the CAMsymfun directory and execute hg pull followed by hg update) and then rebuild the library. Thanks again to Michael Gray for catching and correcting the repeated initialize(..) bug.

February 18, 2009

• Creating Qt GUI applications (.pdf)
  

February 12, 2009

• If you are getting Linker errors or warnings with Visual Studio because of library conflicts, this is probably occurring because you have built some of your program components (e.g. support libraries and Qt) with different project settings. This usually occurs when mixing libraries built using Release and Debug settings. To avoid this problem you can follow the suggestion specified on the linker error or warning line and tell it to ignore certain libraries. Do this by typing in the name of the offending library (for example MSVCRT) in the Properties/Linker/Inputs/Ignore Specific Library field. Alternately, you can try building all components with the same settings. Since you don't want to rebuild the whole Qt library, or can't rebuild it because you are using the PIC machines, this will typically mean using the Debug specification for your projects. You can set the type of the QtConsoleGraphics library by specifying CONFIG += debug (or if you happen to want release, use specify CONFIG += release).

Midterm on Friday, February 6, 2009. Closed books, closed notes.

February 4, 2009

• About Graphics (pdf)

January 31, 2009

• For the adventurous "Installing Qt for use with Visual Studio 2005"
• For those using Ubuntu, notes on the installation and configuration of Qt4.

January 30, 2009

• The QtConsoleGraphics codes and the QtConsoleGraphicsTest.cpp file have been updated (4:45PM, 1/30/09). They have been made "const" correct. If you downloaded the files before this time, you should download them again as the header files have changed. Visual Studio will see warnings concerning "strcpy", ignore these.

January 22, 2009

• The CAMsymfun code that induces a compilation error with g++ 4.3.X versions has been fixed. Thanks to Michael Gray for noticing this and taking the time to make the code "const correct". A revised version is available from the math 157 support repository.
  
  
• g++ users should ignore the remaining deprecation warning. The offending code is on the "to do" list to fix, but the code won't be used for any Math 157 assigments and so the warning can be ignored.
  
  
• gcc users shouldn't use gcc, use g++.

January 21, 2009

Creating and using a CAMsymfun library

On header (.h), source (.cpp) and library (.lib) files.

January 7, 2009

Link to the ODE Applet Page. You'll need to first specify a problem (select Problem®Differential Equation) in order for the "Run" button to function.