[quote who="Jafo" reply="134" id="3742069"] Of course, when I did use LiteSTEP you only had the Windows in WB to apply [the Explorer shell wasn't running] so all my WB skins looked a bit crap because they were really only for the 'windows'.....[and they were crap anyway]... [/quote] Paul's dissembling. His early skins were very clever & among the best available at the time. And still among my favorites.
Daiwa
First I've heard of the possibility, but should it come to pass that WB & IP are dropped from OD, I'll have no reason to renew thereafter.
For ankirk - It's not intuitively obvious, on first purchasing an Object Desktop (OD) subscription, what the role of the included Object Desktop Manager (ODM) is. It's quite understandable to think from its name that it is an essential component without which nothing can be installed. That, however, is not the case. It is provided as a tool for managing the various apps included in the subscription but provides no desktop enhancement function of any kin
Not sure about "Romulan" - there was this guy & his brother...
After reading through this thread, I find great comfort in not being a gamer. Not that being so is a bad thing.
Fine little Happy New Year gift, there.
Never thought I'd say it: I miss Balmer.
Brave's muon-based browser had been my fave, but they've forked to a chromium-based browser, too. At least their flawless page rendering has been maintained in the chromium version. PDF handling works correctly on all my work-related sites with the chromium version, unlike the muon version, & the few Chrome extensions I liked are usable now. So at the moment I've moved over to Brave's chromium version as my default. Everyone's gonna be selling ice cream, just diffe
Since I'm here, here's a short list of some of the long-departed folks who were a big part of making this place so much fun, in random order: Kingbee TexasWahini Tova7 Myrrander Mumblefratz Gene Nash Jill User Dabe Blogic DrMiler Moderateman BakerStreet ParaTed2K Dr Guy Paladin77 San Chochino Bahu Virupaksha Co
Title describes it. Settings dialogs have always had native Win borders until recent 'upgrade' to 1803. Now they're getting skinned frames. Others seeing this? Thx.
Easy, Jafo - English is second language, Zubish is primary. Likewise, congrats to a fellow long-time JU Rat. 17 years, 4 months here for yours truly.
Sadly interesting how things have changed here since 2012. The Politics section was pretty damn lit from about 2004 up to the 2012 election. Rollicking and contentious but with a lot of legitimate argument and debate and a whole bunch of contributors on both sides of stuff. And a lot of fun. Completely evaporated after BO's re-election.
Confirmed. [e digicons]:)[/e]
Looks like I'm not alone.
My prediction is that my supply of give-a-shits was completely exhausted some time back.
One of those stealthy midnight 'quality updates' to IE, I'd imagine.
[quote who="Uvah" reply="2" id="3731364"] Click on the link like I did and you'd discover it requires you to disable your adblocker. Nope. [/quote] Not the case here for some reason. Works fine with adblocker on.
[quote who="Picciu" reply="6" id="3731147"] To be fair, users also complained back then. [/quote] To be fair, that would seem to have been the appropriate time to do so. Nothing left but the bones of this horse. Just MHO.
[quote who="basj" reply="27" id="3731026"] Just checking, if the problem goes away if you turn the scaling down to 100%? [/quote] 100% makes screen text hard for these old eyes to read. 150% is the recommended scaling for this display as it happens.
In response to my ticket from way back when, Support advised me of the same. I'm content to wait out 1809 a little longer to be sure no additional issues are encountered.
Basj - It's a Dell notebook with a 1920 x 1080 display at 125% scaling. No external monitors involved. And just as a reminder, I'm still on Win 10 Pro v1709. Thanks, Daiwa
CURSORS! Foiled again! The fix lasted roughly 48 hours and about 5 reboots. Now back to random dual cursors once more. - Snidely Whiplash
Just a small PS - It appears the Support FAQ that includes a link to the purge utility was published in November of 2017. I submitted a support ticket on the issue in January of this year and was told in reply that the issue had been forwarded to the development team for review which, in retrospect, seems odd as they apparently had the solution 2 months prior & didn't point me to it. But all's well that ends well. CFX appears to be properly functioning now.
I had in fact NOT tried the purge utility before, just a thorough uninstall/reinstall (twice). The purge utility appears to have fixed it - at least through a couple of reboots. So far so good. So, thanks again, basj!
Thanks, basj - I've done that previously but I'll give it another shot this weekend & post again.