birt upc-a

birt upc-a

birt upc-a

birt upc-a

birt upc-a,

birt upc-a,

birt upc-a,
birt upc-a,

birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,

birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,

birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,
birt upc-a,

For auditing purposes, the optimum log location is the database. This makes audit reporting much easier, since a query can be run against the database. The database trace listener provides a quick way of setting up a database logging scenario. This listener has a databaseInstanceName attribute, which for this example should hold the connection string name for the database you created earlier in this chapter by running the CreateLoggingDb.cmd file. Two properties for this trace listener specify stored procedures that must exist in the logging database: AddCategoryStoredProcedure and WriteLogStoredProcedureName. These default to AddCategory and WriteLog, respectively. Listing 9-13 shows an example of a database trace listener configuration in the app.config file, and Figure 9-8 shows the configuration data in the Configuration Console. Listing 9-13. Database Trace Listener Configuration <listeners> <add databaseInstanceName="Connection String" writeLogStoredProcName="WriteLog" addCategoryStoredProcName="AddCategory" formatter="Text Formatter"

would leave traces of their previous positions on the stage, as shown in Figure 6-18. (This effect might actually be useful at some point, for a drawing application, for example, so keep it in mind.)

join(); } catch (InterruptedException e) {} } } } The SynchronousParent class has only one data member, _results, which is used to store the results generated by the Command interface instances The method addResult is synchronized, allowing only a single thread to access the method and allowing only a single thread to add a result to the results list..

listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Database. Configuration.FormattedDatabaseTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging.Database, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null" traceOutputOptions="None" type="Microsoft.Practices.EnterpriseLibrary.Logging.Database. FormattedDatabaseTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging.Database, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null" name="Database Trace Listener" /> </listeners>

Figure 6-18. Objects wil leave traces of their previous positions if you forget to clear the stage bitmap each frame. The enterFrameHandler loops through all the tile models in the _tiles array. It does two important things: Updates the models: It moves the tile models based on their velocities. It also checks stage boundaries. Updates the view: It checks each model and finds its corresponding tile in the tile sheet. It copies those pixels from the tile sheet and displays them on the stage bitmap at the same position as the model. As you can see from the following code, the procedures for moving the objects around the stage and checking stage boundaries are identical to how you work with Sprite and MovieClip objects. for(var j:int = 0; j < _tiles.length; j++) { //Update the models //Update the position and velocity of the tileModels _tiles[j].x += _tiles[j].vx; _tiles[j].y += _tiles[j].vy;

Look at the implementation of the method processRequest The first call is to call the method superprocessRequest, which translates to calling the ParentBaseprocessRequest method The base class method implementation will start all the threads Then, when the base class returns, SynchronousParent retrieves the Iterator instance to the currently executing threads The method processRequest will use the iterator to iterate each thread ID and call the method thrdjoin Calling thrdjoin will call the calling thread to wait until the thread referenced by the variable thrd has finished executing The idea is to call the join method on each of the executing threads, and if all have been called, then no thread will be executing Relating this back to the addResult method, what happens is that a caller of SynchronousParent will expect to execute all the Command interface instances Let s call that the main thread.

//Check stage boundaries //Check left and right if(_tiles[j].x + _tileSize > _stageBitmapData.width || _tiles[j].x < 0) { _tiles[j].vx = -_tiles[j].vx; } //Check top and bottom if(_tiles[j].y + _tileSize > _stageBitmapData.height || _tiles[j].y < 0) { _tiles[j].vy = -_tiles[j].vy; } // } The only indication that we re working in a slightly different universe is that the width and height of the _stageBitmapData are checked, rather than the width and height of the stage. The really interesting part of all this is how the tiles are displayed on the stage. It s done with just three directives. for(var j:int = 0; j < _tiles.length; j++) { // //1. Create the views: display the tiles on the stage bitmap. //Create a Rectangle object that's aligned to the correct spot on the tile //sheet. var sourceRectangle:Rectangle = new Rectangle ( _tiles[j].tileSheet_X, _tiles[j].tileSheet_Y, _tileSize, _tileSize ); //2. Create a Point object that defines the new position on the stage //bitmap var destinationPoint:Point = new Point(_tiles[j].x, _tiles[j].y); //3. Copy the tile from the original tile sheet and project it onto the //correct new place on the stage bitmap _stageBitmapData.copyPixels ( _tileBitmapData, sourceRectangle,