|
premature emojiculation?
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
You live in a different timezone to the rest of the world.
|
|
|
|
|
Yeah, but so does Bob ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Nope. I live in a different world!
|
|
|
|
|
I know that, I've been there. 
|
|
|
|
|
|
|
Maybe sidetracking, maybe not ...
These aliens bringing explosives. Our local discussion about a million martians turned into the question: Titan (the largest moon of Saturn) may be a more viable candidate for human settlement, because we can find lots of fuel there. Except we can't find oxygen to make it burn. It is useless to us.
Some of our explosives work because they carry their own oxygen in their chemical compounds. Those are "detonating", as opposed to exploding, devices. In an environment like that of Titan, with very little oxygen available, you would have to work hard to create detonating devices.
Black powder firecrackers depend on oxygen being available. We can probably conclude that Bob came neither from Mars nor Titan.
Any alien trying to attack / scare / impress us with explosives requriring oxygen should be met with enthusiasm: His world provides something essential to us! In fact, even detonators, carrying their own oxygen, show that there is oxygen available in the home environment of the alies, so we shouldn't reject them.
|
|
|
|
|
Way too long I've been chasing this, and the answer was right there in front of me. I've been overthinking this for years
foreach (var input in inputs)
{
var acc = new List<int>();
var ns = new List<FA>();
foreach (var state in mapKey)
{
FA dst = null;
if (state.InputTransitions.TryGetValue(input, out dst))
{
foreach (var d in dst.FillEpsilonClosure())
{
if (d.IsAccepting)
if (!acc.Contains(d.AcceptSymbol))
acc.Add(d.AcceptSymbol);
if (!ns.Contains(d))
ns.Add(d);
}
}
}
...
I didn't realize I could just make input a range. I thought I'd have to crack it apart into individual characters (kills perf on Unicode)
Pretty much all the lexer code I've written since rolex is now obsolete.
Real programmers use butterflies
|
|
|
|
|
This is totally lost on me unless you show us what's different.
|
|
|
|
|
Some of us will be lost regardless. 
|
|
|
|
|
Nothing about that particular code that is shown is different.
I changed the type of input
From char (one UTF-16 character)
to
KeyValuePair<int,int> (a range of UTF-32 characters)
Changing from UTF-16 to UTF-32 isn't the important bit though.
Changing from a single character to a range was.
Thing is, I thought I couldn't get away with it.
I thought I'd have to enumerate each value in the range and add each state on each value individually.
For reasons that would bore you and are wrong anyway. 
Edit: 
My reasons were right. This doesn't work. I was right the first time
Real programmers use butterflies
modified 24-Jan-20 10:51am.
|
|
|
|
|
It started this year (as I recollect). I lock my (work) computer when I am away from it. Then next morning when I unlock it, all the open windows have changed size to ~4"X4.5" and are 100% overlapping in the top left hand corner of my left screen. This is fairly consistent.
Has anyone encountered this anomaly?
i7-8559U 64bit Windows 10 Pro
But I never wave bye bye
|
|
|
|
|
The office cleaners have the master key to your desktop and are pranking you.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That must be it. I have had the system for about a year. The only changes that happened are the ones graciously donated by Windows Update.
[made me smile - uptick]
But I never wave bye bye
|
|
|
|
|
One of the new icons must have a bug in it.
It can't be anything else, because all they do these days is make icons.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Sounds like the standard behavior you get when you change your resolution to something small and all windows resize/reposition themselves so they remain visible. When the resolution is set back, everything remains in that corner.
I very, very vaguely remember seeing something similar from decades ago - the lock screen, for some reason, switched the resolution to something extremely low; when I logged back in, resolution was restored to what it was. But that was in...Server 2003 (?) days? Does your lock screen look like it's running at a low resolution?
My only suggestion...look for newer video drivers. You might want to check the event log, even if only to confirm there was a resolution change (not sure if that would get logged...or at least, if something thinks the resolution needs to be changed, that might get logged). I don't know. Just throwing s*** at the wall to see what sticks...
|
|
|
|
|
dandy72 wrote: I very, very vaguely remember seeing something similar from decades ago - the lock screen, for some reason, switched the resolution to something extremely low; when I logged back in, resolution was restored to what it was. But that was in...Server 2003 (?) days? Does your lock screen look like it's running at a low resolution?
That's an excellent point. Have any games or graphic apps been installed lately, that might have "helpers" set to run at boot?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: "helpers"
You're correct in placing that word between quotes.
"Helpers" generally aren't.
|
|
|
|
|
I have had the same kind of behaviour if I unplug my screen and plug it back in. It was so in Win7 as well, long before Win10. We spent considerable efforts in finding the reason - colleagues of mine had the same PC model, the same Dell screen driver, the OS was deployed from the company server the same way. Yet I was the only one expriencing this whenever I had to unplug my screen.
So I try to avoid unplugging my screen. The triggering event is different from what you report, but the effect is identical. So I suspect that the root cause is the same, even if triggered by different events.
|
|
|
|
|
What is this bloody fixation of browser makers with putting the page tabs above the address bar and toolbar, so that you can't tell which one the page associated with?
I couldn't count the times I've closed the wrong tabs because it's far from obvious which is which!
The tabs should be attached to the pages, for Crom's sake! That way, because the bottom of the active tab is open, it is patently obvious which one the page is attached to -- but when it's above the address bar, it doesn't indicate anything, and gets muddled up with the other lines.
What do they do with filing cabinets? Cut all the tabs off and glue them to the frame above the drawer?
+ Menu bar
+ Toobar/address bar
+ Tab bar
+ Tabs
In! That! Order!
Great UX. Firefox just lost a customer.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Why? It wastes the "title bar space" that tabs occupy, and - certainly on my system (Win10 + Chrome) - the "active page" tab is highlighted: White instead of a Blue background.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: It wastes the "title bar space" that tabs occupy
Tabs should absolutely not be in the "title-bar space"; that leaves you with nowhere to grab the window to move it, or even to click it to bring it to the front.OriginalGriff wrote: Win10 + Chrome
That's a very attractive combination, but I think I'd rather take the express train straight to Hell, actually.
This[^] is what you get with firefox -- and I had to install an extension to put the dark line above the active tab.
It's utterly ridiculous that the tab is attached to the address bar. Have these people never seen real paper with real tabs?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: leaves you with nowhere to grab the window to move it, or even to click it to bring it to the front.
I can - there is a thin area above the tabs, and a "gap" to the right of the "new tab" button which you can click / grab with impunity.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yeah, loved that at a place I worked where the only option was edge (they had chrome, but I don't consider that to be an option).
Click a picometre too low and you hit the close-tab cross, which you can't see because of the window in front of it.
And the superb piece of cr@p that edge was didn't have an "undo closed tab" option, so I had to go through the history to figure out which one I had closed.
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
