When you backed your workspace up to baseline two, you no longer have the most recent change to rtc_demo.vcproj in your workspace, which is why it is now showing as an incoming change (baseline 3 contains the change set with this latest change to rtc_demo.vcproj).   When you made additional changes in your workspace, one of the files you changed was rtc_demo.vcproj.   This means that you have effectively branched rtc_demo.vcproj ... which means that you cannot deliver your branched version of rtc_demo.vcproj into the stream until you have merged the changes to rtc_demo.vcproj that you made in your workspace with the latest changes that are in the stream.   That is why RTC is telling you that you have to first accept the latest changes from the stream before you can deliver your changes.  Now that you have accepted the changes, you have to resolve the conflicts (i.e. the conflicts that RTC is showing you with the double-sided orange arrow).  Once you have merged that conflict, you will be able to deliver.

Note: To give you more guidance, you'll have to explain why you were backing up to baseline 2 in your workspace.   Were you trying to "undo" the change that was in baseline 3?  In order to do that, you would either need to do a "replace" on the component in the stream to back it up to baseline 2 (backing up your workspace isn't the way to back up the stream), or keep baseline 3 in your workspace, and use the "reverse" operation to create a patch that effectively undoes the change in baseline 3.