 reviewers

- [ ] @github_username

### Second Level Review

- [ ] @github_username

## Summary of issue

ToDo

## Summary of change

ToDo

## Testing approach

ToDo

## CHECK LIST
- [ ]  СI passed
- [ ]  Сode coverage >=95%
- [ ]  PR is reviewed manually again (to make sure you have 100% ready code)
- [ ]  All reviewers agreed to merge the PR
- [ ]  I've checked new feature as logged in and logged out user if needed
- [ ]  PR meets all conventionsAs wonderful a handicapping extravaganza as the Breeders’ Cup is, it was is and probably always will be a strange, dichotomous event. With multi-race wagers and tourneys now representing such an important piece of the average player’s puzzle, one often finds himself bouncing back and forth between races in which he is familiar with the entire field, and others in which several runners exist solely as past performance lines on the printed page. For every California Chrome or Beholder or Syndergaard — horses for which we can almost close our eyes and picture with great accuracy the events before, during and subsequent to each of their races — there are horses like Home of the Brave, Intricately and Queen’s Trust for whom a closing of the eyes will show us little more than the inside of our eyelids.
And yet it is how we perform on these races with Europeans that will, in many cases, determine how we do in our tournament play and cash wagers this Friday and Saturday. The problem for me isn’t that I can’t handicap a European past performance line, it’s that those PP lines have no context to me. I don’t know instinctively who the conditions favored on a certain day, who was using the race as a prep for something else, etc.
The good news is that many Americans betting the Breeders’ Cup are in the same position. And that can lead to opportunity if you can smoke out a nugget here or there that can help you zero in on an overlaid horse that others will only use defensively (perhaps a spread of all the Europeans in a given race, for example) if at all.
There are two sources I have found particularly helpful thus far in trying to size up this year’s European contingent.
One is the commentary of British racing expert Nick Luck, who will again be part of the NBC telecast. But time is precious on TV, and it’s hard for anyone to go to far in depth on that medium. Here, though, is an hour-long interview that Steve Byk did with Luck last week:
I listened to it a couple of times just to sort of let everything sink in. I want it as “internal background” in my head as I go about tackling the actual PPs once post positions are drawn. And I believe Byk will be having another sit-down with Luck this week. I’ll certainly be tuned in to that as well.
Another person whose work I have found interesting (and I confess to not having heard of her before) is Kellie Reilly, whose horse-by-horse profiles of the international runners are now starting to appear on the Twin Spires blog page. She does a very nice job of taking you step-by-step through a horse’s 2016 campaign to date, plus there is plenty of high-quality embedded video of key races along with an occasional workout. I’m planning to read all of her available features before I handicap, and then re-read those of horses I am at least somewhat interested in after my first pass-through of the PPs. Her profiles are available through the Twin Spires twitter feed (@TwinSpires) and also on this page:
As tough as the Breeders’ Cup is to handicap with so many horses in each race “having a shot”, one race really can make your weekend. I hope you find some of the above helpful in your BC preparations. Happy Handicapping.18/6/14
izzy
when he woke, there were fronds on the pillow
he thought she had brought them in for him
a gift from the garden
but when he sat up to take them in his hands
to examine them, to marvel at the tiny leaves
in delicate strings like jewels
the fronds moved too
he put a hand to his face in confusion
and was met with a rustling mass of leaves
that seemed to be attached
he stood by the window in horror
looking to the mirror
and back out at the lush garden
he held his arms out and tried to pose
as he thought a tree would
little salty droplets running down
dropping from the ends of his fronds
when he heard her come in behind him
he was ready to turn and let his rustle
terrify her
but she came up behind him
and her fronds tickled the back of his neck
*
sarah
It was at the peak of the fever that she came to feel that English words were too harsh, too clunky to describe the jumble of belongings in the room. ‘Les petite noisettes’, she muttered quietly, unsure whether these were real words, but sure that French was the tongue to which she could turn in this time of need. ‘Les chansons per bon les mesdames’, she added, rolling the twittering syllables around in her head. She could taste the sweet thrill of good icing sugar, the brittle snap of toffee, the heady oil of hot butter. ‘Per favor dans le coterie’ dripped from her mouth and dribbled down her chin, and it was then that she gave up English altogether.
*Located on the first floor of Burdick Hall, near the northeast corner of campus, the IT Help Desk at UCA exists to respond to your technology issues and requests, as well as schedule necessary service.
To submit a request, click the button below.
Help Desk services are available to all current UCA students, faculty, and staff. We cannot assist the general public with technical support issues. If you call the Help Desk, please be prepared to supply your full name and UCA ID number (listed on your UCA BearCard). If you visit us in person at Burdick Hall 101, please be prepared to show us your UCA BearCard.
Your UCA password must be changed every 90 days or it will expire. You will receive warnings via your UCA email account every day beginning 14 days in advance of your password expiring.
Change your password anytime by visiting password.uca.edu.
During business hours, visit the IT Help Desk in person with your UCA BearCard.
For security reasons, any issues regarding passwords are treated differently than normal technical support issues and require additional layers of identity verification. The Help Desk will not reset or supply passwords via email.
Our services are limited to university-owned technology. Therefore, we are prohibited from working on personally-owned computers and devices. However, we are more than willing to answer questions and recommend solutions for any problems you may have.
#include "GameWindow.h"

Tameran::GameWindow::GameWindow(HINSTANCE hInst, char* pArgs)
	: GameWindow(hInst, pArgs, "DirectX Window", 1024, 768, false, false)
{}

Tameran::GameWindow::GameWindow(HINSTANCE hInst, char* pArgs, const std::string title)
	: GameWindow(hInst, pArgs, title, 1024, 768, false, false)
{}

Tameran::GameWindow::GameWindow(HINSTANCE hInst, char* pArgs, const unsigned int screenWidth, const unsigned int screenHeight)
	: GameWindow(hInst, pArgs, "DirectX Window", screenWidth, screenHeight, false, false)
{}

Tameran::GameWindow::GameWindow(HINSTANCE hInst, char* pArgs, const std::string title, const unsigned int screenWidth, const unsigned int screenHeight)
	: GameWindow(hInst, pArgs, title, screenWidth, screenHeight, false, false)
{}

Tameran::GameWindow::GameWindow(HINSTANCE hInst, char * pArgs, const std::string title, const unsigned int screenWidth, const unsigned int screenHeight, bool fullscreen, bool vsync)
	: IGameWindow(hInst, pArgs, title, screenWidth, screenHeight, fullscreen, vsync),
	direct3D(this), shaderManager(direct3D.GetDevice(), hWnd), camera(), input(screenWidth, screenHeight, hInst, hWnd), gameStateManager(), titleScreen(this, &direct3D, &shaderManager, &camera, &input),
	menuScreen(this, &direct3D, &shaderManager, &camera, &input), loadingScreen(this, &direct3D, &shaderManager, &camera, &input), gameScreen(this, &direct3D, &shaderManager, &camera, &input)
{
	//Set the initial position of the camera and build the matrices needed for rendering
	camera.SetPosition(DirectX::XMFLOAT3(0.0f, 1.0f, -10.0f));
	camera.Render(true);

	//add the title screen to the gamest