|
The bug I make very clear with my code is when one undo a couple of times then redo once, they cant redo no more.... Kind of easy to overlook...
In fact it seems since I am here this kind of bug comes up every now and then in a never ending episodic fashion... Each of them being hard to track. My code make it easier to uncover them.
|
|
|
|
|
What you are probably saying is that the path to failure to keep over patching an old codebase to keep it 'alive'. But that`s a guess, you`re using impossible English for me so I`m not 100% sure about the meaning of your expression of thoughts.
modified 20-Aug-22 16:30pm.
|
|
|
|
|
So you create a redo2 with the correction. Port all of your dependent code to redo2.
Deprecate redo.
They will have to fix their own code as it creates new warnings.
|
|
|
|
|
Have a really great day @Marc-Clifton
![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) ![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif) ![Badger | [badger,badger,badger,badger...]](https://www.codeproject.com/script/Forums/Images/badger.gif)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
|
Happy birthday.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
(chiming in) Happy birthday Marc!! Have plenty more, they are good for you.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Thank you, and yes they are!
|
|
|
|
|
|
|
Happy birthday young man!
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
Thank you! 60 years young!
|
|
|
|
|
|
Sound like you have a good day! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Should WaitOne have been named WaitOn?
Gus Gustafson
|
|
|
|
|
Hmmm,
I think the One in the name is referring to the number of objects you are waiting on. The Windows API equivalent would probably be WaitForSingleObject[^].
|
|
|
|
|
+5 Good thought.
Gus Gustafson
|
|
|
|
|
Of course, I'm assuming that you were referring to WaitOne[^]. 
|
|
|
|
|
I think so too
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
Maybe, if "wait one" implies a time limit, but "wait on" does not.
|
|
|
|
|
WaitADaGumMinute?
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
"Wait One" referring to waiting a minute is US dialect / jargon. We should have "WaitOneSecond", "WaitOneMinute", ...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Nope. WaitOne means you're waiting on a single signal as opposed to WaitAny and WaitAll. The term "WaitOn" could mean "wait on one signal" or "wait on any signal" or "wait on all", all of which are very ambiguous with the adjective "on". When dealing with threads and signaling, being very clear is critical for successful task/thread management.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
whichever you prefer 
