391–400 of 400 posts
Earlier quoted context omitted.
They clearly nailed it, this video from the dev team shows how the understood their users and stuck to the requirements instead of the typical MS feature creep product https://www.youtube.com/watch?v=Hxx2KcPWWZg
"Opens in a matter of...minutes!"
Earlier quoted context omitted.
There are like 50 different toolkits... I exagerate, but: win32 GDI, windows.forms, MFCs, ATL and that is just from microsoft off the top of my head. There are way more when you start looking at all the solutions that a typical user might actually have running on their machine.
MFC, ATL, and the .NET stuff with the exception of XAML all use win32 controls under the hood. XAML still uses user32 albeit not the control toolkit. Because everything shares the same common core things work together better than on Linux.
Oh, I wish that were true. I have twice been a test automation engineer and stopped exactly that not being true for all widgets. Some are, but many of them, including some styles of buttons are not. A simple heuristic to tell is that when a UI widget does something the win32 can't, its probably not a win32 widget.
Even using UI inspection tools like Spy++ panels with .Net buttons that aren't backed by win32 buttons just show don't show up as an item is the tree of UI elements. There are also applications that just do silly things like use GDI, DirectX or OpenGL to draw a thing that looks like a button and isn't controlable of adjustable via external calls at all.
Earlier quoted context omitted.
A Metro-ified flat-design-meme store-dependent mess which takes a noticeable delay to load . I've taken to firing up an instance of IDLE instead - which is actually a little nicer in the end
You need to give ipython a go.
Earlier quoted context omitted.
You need to give ipython a go.
I have one deployed on Digital Ocean ( http://blog.mclemon.io/fedora-jupyter-on-a-linux-remote-usin... ) but it's just not as convenient or quick as a local python repl for quick calcs and sums.
Earlier quoted context omitted.
I've actually used Windows 3.1. In Paintbrush you had palette of 20-ish colors, which were or were not dithered depending on whether they were displayable by your graphics adapter. (The default palette consisted of 16 default EGA/VGA colors and few dithered ones, with particularly notable burgundy-ish color that almost didn't look dithered). In the control panel you could set arbitrary 24b RGB colors for user interfa…
"I've actually used Windows 3.1" God I feel old. Please tell me I'm not the only one who uses dosshell, or hacked gorilla.bas
Earlier quoted context omitted.
Not him, but I would have stayed on 8.1 too if it weren't for processor support. The only annoying thing about it is the start menu, which i only use for maybe 10sec/month. It's faster than win7 and has a bunch of features I would miss, and compared to 10 it's not as bloated with non-win32 apps with less functionality for everything, tracking that you can turn off, and all the other win10 stuff you've heard already.
I am also on Win8 (some of the time) and those are the reasons. What is the processor support issue?
Earlier quoted context omitted.
Checkout ShareX, I was a long time Greenshot user (and it even integrates the nice annotation stuff from Greenshot) but I switched because it has an even nicer UI and a host of additional features while remaining simple to use (still free though.)
But ShareX does not have an image editor, like Greenshot. Which is the whole reason we are discussing alternatives to paint. Or am I wrong and someone implemented one?