SledgeHammer01 wrote: She was investigated over the email server and it was determined that there was nothing prosecutable. Case closed. She's "innocent". Again, incorrect. The FBI stated there was evidence that the law was probably broken, however the decision was taken not to prosecute. That's the reality...the FBI think "She's guilty but we'll never get a conviction so won't waste our time". The way you are framing it (that she was "cleared" and "innocent") is that she was charged, went to court and successfully argued she was not guilty. If the police see you going 5mph over the limit but decide to not pull you over and ticket you, does that mean you have not broken the law? No, it means you were let off.

I know I am late to the party, but my first question to these requests is always "What are you REALLY trying to do?". Most people come at you with a problem to their solution instead of asking you for a solution to their problem. Once I sit someone down and have them tell me exactly what their problem is there is always a much simpler path to take instead of the putting the square peg in the round hole. In this situation you are describing I would be asking them what are you going to use this for? Are you expecting a handful of engineers on the enterprise hitting it? Or are you going for a web facing portal audience. How you plan to implement a SQL database really starts there.

That he is still batshit crazy. What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???

Don't forget that the keyboard isn't the only way that Aero-snap can be invoked. Dragging the window to the edge of the screen will also invoke it. :) "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Modern 2) ? 3) It was once called the Outlook Bar, but now it's the Navigation Bar. 4) The same as Outlook now, I suppose.

Actually, from watching Air Crash Investigation :), lots of things can cause the auto pilot to turn itself off: certain input to the controls, faulty sensors, etc. Basically, when the auto-pilot doesn't know what to do, or is confused by the information it gets, it turns off automatically.

The other side has 3 or 4 lanes and the intersecting road has 2 or 3. They did all these upgrades and expansions because this is a street that runs next to a former, rather large marine corp base that has been abandoned. They're now building it out with homes. I wouldn't be surprised if they can fit a couple of thousand.

It's data for the emergency services. Typically, we could see about 40 to 50K messages every 10 seconds. Different parts of the application suite need different parts of these messages.

Tried moving it to SourceInitialized and get the same result. 4.5.1 works perfectly and 4.5.2 has the 1 - 2 second start up lag. This isn't even a question of framework targeting, just if you have > 4.5.1 installed on the machine, it happens.

The problem seems to be that DrawingBrush has round-off errors internally or it doesn't work the same way as the LinearGradientBrush in terms of origin / relative ratios. Like I said, LinearGradientBrush hits the line consistently with my "math". DrawingBrush isn't even consistent at 50% which should not even be suspectible to round-off errors since its a whole pixel. Sometimes its 1 pixel too high, sometimes its 1 pixel too low. Also tried TransformToVisual to go from the line to the path, but TransformToVisual considers both shapes to be the same height (as the height of the control), so it just maps the points 1 to 1. Tried Math.Round() and Math.Ceiling(), etc. LOL. The line itself certainly doesn't move around, its always at the exact correct location. Tried get the rendered bounds of the path and calculating it from that, but same thing... +/- 1 issues. Also tried setting everything to absolute mode and setting the rectangles identically, nope... Maybe the LinearGradientBrush only *appears* to be working and is hiding the +/- 1 issues with the gradiented color switch.

It's not the "math"; it's the UseLayoutRounding setting (or lack thereof).

Okay, well I understood your question more than I thought I did :) Given the presence of a "last close" line in some color other than red or green, and assuming there's always at least one pixel of "open space" both below and above the integer value of the height of the close line: I'd simply draw the red line up to close line height minus one, and draw the green line beginning vertically at close line height plus one. So I'd be validating the last vertical position of the red line, and the first vertical position of the green line and "doing the right thing." I'd also draw the close line last ... as an overlay ... to hide any mistakes that were made. Am I on your frequency yet ? «OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. »  Alan Kay's clarification on what he meant by the term "Object" in "Object-Oriented Programming."

I've had many mornings like that.

Hmm... I found some Petzold code that creates a canonical spline in WPF, seems like its working (doing what I want) unless I don't know what I'm talking about which is entirely possible since I don't know the diffs between all those splines haha. All I know is that it looks like a wave interpertation of my zig-zag line. Thanks!

SledgeHammer01 wrote: I don't know if you read every post in this thread Yup. SledgeHammer01 wrote: Says right here that as soon as all foreground threads are finished, the process exits. Background threads are terminated on the spot. The proces is considered terminated if all foreground threads are terminated, true; I do not see a specific guarantee that the background-threads keep running if you kill the mainthread. I can only confirm that the behaviour is not directly what I expected, as the documentation still does not explain why the first codedump behaves as it does :) Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

jschell wrote: Never understood that need. That can only apply if getting the item requires acquiring other resources and in that case, especially given 5, then either make the caller responsible for that or wrap it is a proxy and that does it. I have a worker thread that monitors the queue. There is not always something in the queue. In fact, most of the time, it will be empty or close to it. Clearly, I should not spin the CPU when the queue is empty. As for being able to cancel the blocking operation, well... if you wait on a syncronization object indefinitely (the blocking part), it keeps the thread alive (which will keep the process alive) [EDIT: unless the thread is a background thread]. Not a desirable behavior when you, say, want to be able to shut down your app :). Using a timeout is also not a solution, as if you set your timeout too low, you'll spin the CPU, and if you set it too high, you'll have that annoying behavior of your app taking a long time to shut down. jschell wrote: Its a generic class/API which means if there is a failure mode then it must throw exceptions. I wouldn't consider cancelling a blocking operation to be a failure if the cancellation was intended. But some would... jschell wrote: Not that hard and I suspect there are a vast number of examples on the internet. You'd be surprised ;).