What about this: https://github.com/jgraph/drawio
That repository only contains the minified code, not the original source.
What about this: https://github.com/jgraph/drawio
That repository only contains the minified code, not the original source.
<https://www.quora.com/What-is-the-tools-and-languages-used-i...>
However it is important to recall that the people who actually made all the money extracting the wealth got out years before, retiring and/or selling stock. They're bystanders now and probably happy to run the whole operation again.
Although as an aside who these people are who think corporate pensions are a good idea is beyond me. People really should be in charge of their own savings in preference to their employer, expecting some random corporation to cover the cost was always a bit crazy even when it seemed sort-of possible that the system was stable. It is easy to have some sympathy but, as a practical matter, it was never going to work and it isn't a surprise that it didn't.
The arrangement where the _company_ controls the account seems to me to be more of a allowed delay in salary payout, to the benefit of the company, than a retirement account for the employee.
The win32 API has its origins on the 8088 processor and doing things a certain way results in saving 40 bytes of code or uses one less register or something.
I wrote a lot of toy gui apps using mingw and Petzold's book back in the day. Writing custom controls, drawing graphics and text, handling scrolling, hit testing etc was all a lot of fun.
I see in your app you're using strcpy, sprintf. Any kind of serious programming you should be using the length-checked variants. I'm surprised the compiler didn't spew.
You'll also find that the Win32 API has a lot of replacements for what's in the C standard library. If you really want to try and get the executable size down, see if you can write your app using only <Windows.h> and no cstdlib. Instead of memset() you've got ZeroMemory(), instead of memcpy() you've got CopyMemory().
At some point writing raw C code becomes painful. Still, I think doing your first few attempts in raw C is the best way to learn. Managing all the minutiae gives you a great sense of what's going on while you're learning.
If you want to play more with win32 gui programming, I'd have a look at the WTL (Windows Template Library). It's a C++ wrapper around the win32 API and makes it much easier to reason about what's going on.
The real problem is acceptance of non-word/latex papers
Some scientific journals, which only provides a Word template, require you to print to PDF to submit, then ships this PDF to India, where a team recreates the look of the submission in LaTeX, which is then used to compose the actual journal. I wish this was hyperbole. For these journals, you can safely create a LaTeX-template looking _almost_ the same, and get away with it.
Get a B&W Brother laser (or LED, nowadays), it'll be good, last long and… I expect it won't delight you because you want to print in colour, or if you don't want that, people will send you things that you need to print and they presume colour.
I replaced my B&W Brother with a colour LED a few years ago, because some documents really need colour. Sigh. MFC-L3770. The colours aren't good but the printer does what I want and without any hassle.
If one wants an inkjet, I'd go for an Epson EcoTank.
I recall trying OS/2 2.0 or 2.1 back in the day, coming from a DOS/Win3.11 setup. It seemed to have the same basic features as DOS/Windows but wasn't properly compatible with my existing software. Admittedly, this was before I knew anything about programming. I discovered Linux not much later. It wasn't compatible with anything either, but seemed like a totally different and much more compelling proposition.
I started out with OS/2 v1.1. It had threads, DLLs, multi-tasking, much larger memory space, and from v1.2 a somewhat decent filesystem. Coming from DOS 3.2/Win 2.0 this was an incredible leap, in particular the SDK was amazing compared to the ragtag assembly of info I was used to. The _delta_ between two systems haven't been this large ever since, and I think that is what contributes to the "magic" feeling.