That sounds like one of the many video card driver issues I've heard about. I'm still waiting on AMD to come up with a driver that doesn't make my second monitor blink every time I do something as basic as closing a browser tab or right-clicking.
That sounds like one of the many video card driver issues I've heard about. I'm still waiting on AMD to come up with a driver that doesn't make my second monitor blink every time I do something as basic as closing a browser tab or right-clicking.
NVidia support has been pretty shit so far. I earlier predicted a zero-day patch for their drivers; it never came. Windows has always recovered quickly for me, but it's still annoying how crashy NVidia's drivers are right now.
Guess I shouldnt have hope that they will be fixing Surround any time soon then
"In a field where an overlooked bug could cost millions, you want people who will speak their minds, even if they’re sometimes obnoxious about it."
Thanks. My graphics card is an AMD.Originally Posted by Echovirus
For those that lost fonts when upgrading to Windows 10 (like my look of disapproval) install these: https://docs.google.com/uc?id=0B3FIi...xport=download
"In a field where an overlooked bug could cost millions, you want people who will speak their minds, even if they’re sometimes obnoxious about it."
Last week the one on mine started popping up aggressively on start-up and every time the computer woke up from sleep. I finally gave in and told it to reserve and am expecting to have to kill attempts to slide me into upgrading before I want to.
Last night as I lay in bed, looking up at the stars, I thought, “Where the hell is my ceiling?"
You do know that Windows 10 is riddled with spyware?
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
As I hadn't had any problems with my Laptop I updated my PC and have ran into a couple of localisation problems.
Firstly the date was being shown as 8/17/15 when it is of course 17/8/15. The short date default is the format M/d/yyyy with no equivalent d/M/yyyy option listed in the drop-box. The only d/m option is dd-MMM-yyyy (ie 17 Aug 2015). The Sage software I use gave an error message when I logged on saying that the system date was in the wrong format. It then couldn't interpret the dates properly based on that as it was showing dates as 17-008-0015 which is meaningless and unaccepted. I searched Google and found the solution is to go to Windows Date and Time Advanced Settings and manually type the format you want to use (ie dd/MM/yyyy) since Microsoft don't provide it as an option by default for some reason. Very bizarre and very poor to just ignore standard settings for much of the globe.
Second problem I've just ran into was I was working on an Excel spreadsheet and entered some prices. Went to format cells and selected the Accounting category to get the prices to show as prices ... and the currency selected was $ rather than £ as it normally would be.
As far as I know I'm still set to English language and English localisations in Windows so I have no idea why it'd change my default currency to the dollar.
EDIT: Found despite United Kingdom being the location my settings were changed elsewhere to English (United States).
Beat the Sage software developers over the head because they'reprobablydefinitely not knowing what they're doing.
Seriously, interpreting DateTime is a solved problem for decades now and the problem you had? It pops up because some stupid programmer, instead of using the language's DateTime-functions instead decided to roll his own function, fucking it up in the process. From your description they're obviously casting the DateTime to a string and then inflict regular expressions on it. No wonder that the program barfed.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
Why not blame both?
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
Because the default DateTime format that Windows uses is culture-invariant, i.e. a universal representation of the current date and time which you then convert into a human-recognizable string of characters.
For instance, in C# it looks like this:
It's also easy to manipulate:Code:DateTime present = DateTime.Now; var day = present.Day; //gives the number 17 var weekDay = present.DayOfWeek; //gives the string Monday
That way you don't have to worry about leap years, leap seconds, the number of days in a month and so on an so forth. It's easy to use, fool proof and the only way you can fuck it up is by not using it.Code:var inTwoYears = present.AddYears(2);
The date you're seeing in the task bar? That's Windows using the exact same methods to create a human-parsable string. But if you're using this human-parsable string and convert it back into a DateTime without checking for the culture, you shouldn't be let near a program of any sort.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
Yes, I am aware of that, but it's still no excuse for using the (frankly batshit) American date format as default when a machine was supposed to have been localized for the UK, then making it non-obvious how to change it.
'checking for the culture' aye.But if you're using this human-parsable string and convert it back into a DateTime without checking for the culture, you shouldn't be let near a program of any sort.
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
I'm not blaming Microsoft for Sage's screw up, I agree with you that Sage should be better programmed than that. It is a market leading software for its industry not some minor niche one, it is not one I expected to throw up a conflict.
But it is weird that Microsoft would alter my localisation settings from British to American - while still showing it as British in one window but needing to find another to see its now American. That is poorly implemented. Not the end of the world but it could have been much clearer that it had been done, nor should it be a change an upgrade should make. In the past I've always preferred formats and clean installs for OS upgrades for this reason though.
PS this was definitely fully localised to being British in the past with the £ symbol being the default Excel used based on that localisation.
Tell me Khen, which do you think is more likely:
a) That of all the 100s of programmers who have likely worked on the Sage software over the users, not a single solitary one of them had ever heard of their languages built in DateTime functions, nor when they came up against this seemingly insurmountable challenge of 'there are different ways you can write dates', they didn't, e.g. google it and find out about them in about 35 seconds leading us to the inevitable conclusion that the most popular and well regarded accountancy package in the world has been written and is continuing to be maintained by students straight off a Programming 101 course with no access to the internet or textbooks
b) there is actually a reason why they didn't or can't use them, or can't rely on them
which do you think it is.
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
Actually, it's a) Steely. You're misinformed if you think that your "100s of developers" all have a clue and, more importantly, they don't all look at the same parts of the code and are responsible for the same parts.
Which means that someone included a custom DateTime-library for others to use, everyone else thought this to be a good idea and actually used that and furthermore, there was no code review by a capable developer who would have spotted the WTF.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
Playing around with the new multiple desktop mode, it works quite smoothly so far.
One thing that surprised me is that I was listening to music (via YouTube, via Chrome) when I opened and switched to the second desktop. The music continued uninterrupted the whole time without skipping a beat. So while its not clearly visible everything in the other desktop continues running uninterrupted (including sound).
Seems like a great mode for hiding that you're slacking at work. Load work in desktop one, load Facebook etc in desktop two.
What do you think how I post here. Linux (KDE, GNOME, CDE...) has multiple desktop for decades.
"Wer Visionen hat, sollte zum Arzt gehen." - Helmut Schmidt
Can it be set up to work for multiple monitors? Eg rather than having monitor two be an extension of monitor one, you have two desktops each with their own monitor?
In KDE, no. But I can have different task-bars for each monitor so that's about the same effect isn't it?
"Wer Visionen hat, sollte zum Arzt gehen." - Helmut Schmidt
If not there's always this :
http://www.actualtools.com/virtualde...monitors.shtml
"One day, we shall die. All the other days, we shall live."
Well at home I got a single wide screen monitor anyway, and at office I will go for that as well the next time I buy a monitor.
"Wer Visionen hat, sollte zum Arzt gehen." - Helmut Schmidt
Please regale us with more tales of your time working at Sage!
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
Listen, Steely, if you haven't got a clue of how developing a program works, just say so.
You're trying to excuse a developer's WTF without having the faintest idea of how a program actually works. Again, there simply is NO reason to roll your own DateTime functions. None. All modern languages (and by "modern" I mean: Younger than COBOL and FORTRAN) have such functions and methods in their APIs. C++ has them, C# has them, Java has them, Rust has them, Haskell has them, Ruby/Python/Perl/PHP have them.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
New WTF and it could be a coincidence or it might not be.
Spent the day working on a spreadsheet for a business proposal. Quite a basic spreadsheet, three tabs of data with all data fitting on one screen per tab. After finishing I loaded up Gmail webmail (that I use for my email) and attached it as a spreadsheet. As I always do when I send an attachment I clicked to download it (to see that I've not sent an earlier draft) but now its saying that it is corrupt. Checked through File Explorer (or whatever its called nowadays) and this basic Excel spreadsheet was saving as 3.1MB. WTF?
Started a new spreadsheet, copied and pasted everything and it now saved as 15kb. A bit better. Reattached that but again its showing as Corrupt when I try and download it. Gave up, emailed it anyway and now Gmail is showing the spreadsheet perfectly through its preview feature but when I click to download it, it is still corrupt. Hoping the other person I've emailed it too doesn't see it as corrupt.
Never had this happen before so its an almighty coincidence if its not related. Only software used in this is Windows, Excel and Gmail (via Chrome) so no third parties.
That's most likely a problem with Chrome and/or GMail. You're not the first to run across this issue: https://productforums.google.com/for...il/MoV8OuxAvYk
Did you try the same in Edge?
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
I'm fairly certain the only person around here who doesn't have a clue is you. You have absolutely no frigging idea why Sage even needs Windows date format to be set a certain way, yet your first assumption is that it's because the developers didn't know some pretty elementary stuff about the language they were developing in, which demonstrates nothing but the most breathtaking arrogance on your part.
It *could* have been a mistake, it would hardly be the worst WTF ever found in production code, but there may actually be perfectly valid or at least understandable reason for it which neither you nor I being entirely unfamiliar with the code I'm question are in any position to speculate on.
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
Steely, if they're getting basic stuff like DateTime wrong then I wouldn't really trust them to get more complicated stuff right.
And that they don't know pretty elementary stuff about the language they were developing in, that, my dear, they actually demonstrated by having their program throw a hissy fit about the date format. And frankly, in your case the Dunning-Kruger-Effect comes fully into play. But I'm done arguing with you. Keep on finding excuses just because you're deadset on proving that Windows done goofed. Anyone who actually knows their stuff will only laugh at you.
When the stars threw down their spears
And watered heaven with their tears:
Did he smile his work to see?
Did he who made the lamb make thee?
Just tried with Firefox and Edge and it still shows as corrupt. So Chrome isn't the issue.
Going back to Sage when it detected that Windows was using the wrong date format it gave me prompted me with saying that Windows was using the wrong format and giving me the option of three different date settings. Using Windows default was the default setting, there were two others that I ignored because I'd rather get Windows working properly than fiddle around with other settings. Sage may or may not be using DateTime in the second or third setting, I don't know and honestly don't care.
When I referred a few pages back to a company advising that upgrading is delayed a month so that someone else spots incompatibilities, that was Sage btw. I timed the upgrade by waiting until after I'd finished running payroll and paid everyone and finalised this months accounts before upgrading to 10. No regrets whatsoever over that and my teething problems kind of match my concerns and Sage's advise over timing your updates at a time that suits you properly. Had I been dealing with these incompatibilities while I was on a deadline to pay wages that'd be very frustrating.
This is absolutely ridiculous. You have no idea what weird and wonderful combination of edge cases and quirks may or may not have lead to that particular decision. You have no business simply *assuming* "oh they just rolled their own DateTime library, because they're idiots" based on nothing but a few vague statements from randblade, and no business questioning anyone else's competence based on the level of assumptions you're comfortable making.
The light that once I thought compassion still casting shadows in your action
The words you shared were cold transactions that bring me to curse what you've done
When you're up there absorbed in greatness with such success you've grown complacent
I hope you scorch your many faces when you fly too close to the sun
To be fair the description given by RB doesn't exactly make it sound like it was deliberate. The first part just looks like an oversight which I guess is a little dumb but that's how the world is. Of course Khen is also dumb if he gets this pissed off about what seems to be a mistake. It does not however sound like someone rolled their own datetime function so much as someone neglecting to store some data as dates similar to what happens when you enter a date in the wrong format into an excel cell.
"One day, we shall die. All the other days, we shall live."
Posting Permissions
Reply With Quote