If I had one probably, Though I can't use a controller anymore haha
I used one a couple of months after I went to PC and stopped going on my console and you know when you see an older person using a controller and they turn, stop, then aim. I was like that haha
Do we have a policy regarding "Honourable mentions" on Id Qs? I've seen a few recently where an answer was already accepted and someone came along and said" although this isn't it it matches mostly..."
Adding objectively wrong answers should not be left
@Skooba Putting "I'm aware you've found the answer, but this book also sound similar" is different to some guy coming along hitting the answer button and then just typing away some random mumbo jumbo
For example, here: Do (weaponized) lasers exist in the Star Wars universe?
@Zato posted a what-seemed-at-the-moment-correct answer, which generated tons of upvotes (10) stating "no such examples exist" - he did the research, but the only actual reference he had was Wikia (lack of references is ...
There are some answers on this site that are just plain out 100% wrong (explained why wrong in the comments, and usually downvoted).
We can't flag them for moderators to delete (that usually gets declined), since the answer is simply wrong and not spam/etc... leaving aside other consideration, ...
If you guys like DailyWTF, I've just found this code in a project of ours
if (File.Exists(strSrcImageFilePathFront))
{
if (File.Exists(strSrcImageFilePathRear))
{
}
else
log.Error(string.Format("Unable to find the Rear Image[{0}].", strSrcImageFilePathRear));
}
else
{
log.Error(string.Format("Unable to find the Front Image[{0}].", strSrcImageFilePathFront));
if (File.Exists(strSrcImageFilePathRear))
{
}
else
log.Error(string.Format("Unable to find the Rear Image[{0}].", strSrcImageFilePathRear));
}
if (!File.Exists(strSrcImageFilePathFront))
{
log.Error(string.Format("Unable to find the Front Image[{0}].", strSrcImageFilePathFront));
}
if (!File.Exists(strSrcImageFilePathRear))
{
log.Error(string.Format("Unable to find the Rear Image[{0}].", strSrcImageFilePathRear));
}
It also doesn't make sense that source has been shortened to src but then the rest is ImageFilePathFront when it could easily be frontImagePath or something
I like that it checks if the rear image exists in two places depending on if the front image exists or not even though they are completely unrelated to each other
What's better is it then processes the images regardless of if they exist or not too
Well instead of using our own viewer (which is actually the change I'm doing) at the moment it calls a Process.Start on the file so it'll open in Windows Photo Viewer or whatever the default it so that might error I'm not sure
Basically no
I'm essentially re-writing the whole method
What's annoying though is this is an app that I'm 99% sure the user is never going to use
Well we upgraded a system for a new customer but they wanted to still be able to see all the old data from the system that did their work before so this app is for them to view that old data. I just can't see them wanting to view the old data though
@Kepotx They didn't want the new and old data mixing together and to be honest looking at the way the old system (not by our company) stored the data I'm fine with that haha
@JAD Ah right yeah we build the path from a few variables like doc Id and what not
if it were a simple file select thing, you might be able to remove it, but you still would want to check if anything was entered, so if you're at it, why not check it completely.
The Quill and Tankard
The Quill and Tankard