Sorry for not noticing your previous reply. If I had been a bit more observant I could have avoided that. Adding the + to both paddles placed them in the center of the screen as well as allowing them to move smoothly back and forth. Now the issue I am having is that the ball hits the paddle, but does not bounce back towards the other side. Alls it does is sit in the position where it hit the paddle. I am assuming this is some issue in the two elsif statements that check for collision with the paddles. Or possibly something wrong inside the subroutine definition? I fixed the 'return if' statement so that's not it. UPDATE...It was in the $player1 elsif statement. the two lines needed to be switched to match $player2 elsif statement.

In reply to Re^2: Movement handlers in SDL by drose2211
in thread Movement handlers in SDL by drose2211

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.