|
You may be right! 
Get me coffee and no one gets hurt!
|
|
|
|
|
I might be, and then I might not.
That's the thing about beating a race condition - today. 
|
|
|
|
|
never tried MVVM but my best guess is similar thing is happening to winforms when adjusting controls within a control's event handler (i.e. esp. set focus),
introducing the delay may have a side effect similar to queuing changes by way of begininvoke. (i.e. lets the current event complete before controls' changes happen).
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
Quote: lets the current event complete before controls' changes happen
You may have something there! Microsoft must have had a reason to introduce delay as new binding parameter!
Get me coffee and no one gets hurt!
modified 16-Feb-17 10:48am.
|
|
|
|
|
Cornelius Henning wrote: Microsoft must have had a reason to introduce delay as new binding parameter!
Yeah, it's called taking the lazy way out and not fixing the core async / initialization problem.
Marc
|
|
|
|
|
I bind in a tab inside the VisibilityChanged event handler.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Thanks. It's worth a try!
Get me coffee and no one gets hurt!
|
|
|
|
|
EDI can be daunting sometimes. I want to find out what frustrates EDI developers on a daily basis?
Relativity
|
|
|
|
|
Reading cross postings for example.
|
|
|
|
|
Or people who want to have a chat about EDI, especially after having banned and almost forgotten EDI.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
What frustrates me the most is that I don't know what "EDI" stands for. There are too many TLAs in computing.
|
|
|
|
|
Pretty sure it's "Erectile Dysfunction Interface".
Not that I have any direct experience mind you... it's just what I heard... from a friend... not really a friend, an acquaintance... actually an acquaintance of an acquaintance of a one time friend. Long ago...
In this present crisis, government is not the solution to our problem; government is the problem. ~ Ronald Reagan
|
|
|
|
|
OMG - WTF! IMHO, LOL.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: WTFE
FTFY 
... such stuff as dreams are made on
|
|
|
|
|
FYI, TMI. BFN!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The continued existence of EDI is appalling to me; it was the reason XML was invented, and was rendered obsolete 20 years ago.
Will Rogers never met me.
|
|
|
|
|
I respectfully disagree.
EDI is a much more concise format than XML. When human readability doesn't matter, then EDI is fantastic. When human readability does matter (by which I mean standard humans, not us large brained developer types that can actually read the crap,) XML only gets you part of the way there... XLST that doc into HTML and now you have something worth using.
XML has too much faff for my tastes. I don't need a named node or an attribute to tell me what every little piece of data represents. That's what software is for. Taking data in format X that humans can't easily read, and transforming it into format Y which humans can easily read. XML straddles the line of machine and human readability, in my opinion, needlessly.
Also, with enough experience, EDI becomes more readable than XML, due to not having to skip over all of the non-informational formatting that exists in XML. After working with 837/835 files for several years, I can now read one of those nearly as well as I read English (opinions on my English skills vary  )
I'll admit that there's a (sometimes rather steep) learning curve with EDI (since you need documentation to make heads or tails of anything in them...) but it absolutely still has its uses.
|
|
|
|
|
For a while now, I've been noticing that the left-right cursor key navigation of menus on my C# apps that use MenuStrip is backwards -- I press the right arrow at the top level menu, and the menu to the left is selected, and vice versa.
So after appropriate google-fu (which was a bit difficult because the search terms hit all sorts of irrelevant results for what I was looking for) I found this helpful SO:
This is a bug/misfeature in MenuStrip.
Looking at the ToolStripDropDown.ProcessArrowKey implementation with Reflector shows that the arrow keys get reversed depending on SystemInformation.RightAlignedMenus. That's not right. It should depend on the right-to-left mode of the menu strip itself, which may sometimes (usually?) match SystemInformation.RightAlignedMenus, but not always, and not on my system.
SystemInformation.RightAlignedMenus is user-configurable via Control Panel, Tablet PC Settings, Other, Handedness, and indeed if I change that to Left-handed, I get the menus to behave correctly.
So, sure enough, on my laptop, the "handedness" was set to "right-handed." Setting it to "left-handed" fixes my menu problem.
WTF Microsoft?
Now, what I really love is the accompanying description in the Tablet PC Settings dialog:
Right-handed: Menus appear to the left of your hand.
Left-handed: Menus appear to the right of your hand.
Uh, no. When I change the setting to "left-handed", the menus still are on the left, thankfully.
What an elephanting mess.
Marc
|
|
|
|
|
|
I thought the handedness thing was a ridiculous feature, anyway.
My laptop has a touch screen, and I foolishly set it to right-handed, so when I click with a mouse, the menu comes out the wrong side, and setting it to left-handed, as you say, doesn't do anything.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It's not a bug! It's a feature! 
I don't find this surprising considering the bass ackwardness of M$ thinking patterns.
It was broke, so I fixed it.
|
|
|
|
|
Unfortunately, in the past they have made a mistake like this and then people get used to it so it is adopted as standard behavior and they never correct it.
|
|
|
|
|
ahso ...
The rise of the anti-Pavlovian Skinnerian paradigm dying in the arms of a Humanistic psychology.
This could be a noise of the day!
|
|
|
|
|
I didn't need a password to log into the WookieTab, and I skip it on the desktop.
Not any more ... WookieTab is now asking for my password and won't accept blank any more. At a guess it's my MS ID password it wants. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Run it as a local user -- bearing in mind that winio will often "forget" that you want to run it as a local user, and fire it up with your MS ID.
When I rebuilt my laptop, I didn't even give it my MS ID, so it can't fark me around like that, any more.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
