• 0

C++ Graphical Interface?


Question

Well, I'm a beginner here, deciding whether to work on learning C++ or Delphi....

The main problem with C++ is I can't figure out how to make a simple graphical interface (with buttons, etc)

I know you can use toolkits like QT, etc. but it seems like too much trouble.

Is delphi the same way? I remember about a year ago trying delphi and I managed to make something with a graphical interface, so I'm guessing it isn't.

Also I'm still trying to decide between C++ and C#. Seems like C++ is getting outdated, I don't really know though. :p

Link to comment
https://www.neowin.net/forum/topic/660758-c-graphical-interface/
Share on other sites

13 answers to this question

Recommended Posts

  • 0

Good choice! C# is gaining lots of popularity and it is (usually) good to stay up to date with the newest technology. Although don't get me wrong, other languages can be just as great, each programmer has his own preferences on how he gets the job done. As far as delphi goes it would have been a decent choice as well, it's like VB but (in my opinion) it is much more feature rich.

  • 0

C++Builder is the same as Delphi, except it uses C++ instead of Object Pascal (Delphi).

http://www.turboexplorer.com/ is CodeGear's free range of developer products, Turbo C++ is the one you'll want to use. (There is also Turbo Delphi). There great tools to use if you want to learn without spending money.

I use Delphi for personal stuff as well as for my job.

  • 0

Creating a GUI from scratch is NOT a simple problem. GUIs are everywhere now but they took much time and research to develop. Using the Win32 API is a lot more simple, but it's still quite a steep learning curve.

So, using the drag-and-drop interface in VC# or VBasic is really the way to go for beginners, else they want to hit a formidable brick wall. I wouldn't invest too much energy in learning WinForms, though, as it is being phased out in favour of WPF.

  • 0
So, using the drag-and-drop interface in VC# or VBasic is really the way to go for beginners, else they want to hit a formidable brick wall.

I don't think it's just good for beginners; I think it's good for everyone that has no need to write their programs in C++ using MFC, Win32, Qt, or GTK. It's quicker to develop, easier to maintain, and, as a result, costs less to develop.

I wouldn't invest too much energy in learning WinForms, though, as it is being phased out in favour of WPF.

It's definitely not being phased out. Both environments will be maintained for years to come.

  • 0
I wouldn't invest too much energy in learning WinForms, though, as it is being phased out in favour of WPF.
It's definitely not being phased out. Both environments will be maintained for years to come.

sbauer is right, but here's why. Windows Forms is just a light wrapper over Windows API (just use Reflector and see for yourself). And Windows API isn't being phased out because it's the very basis for the entire Windows operating system.

WPF (Windows Presentation Framework) isn't a replacement for Windows API. It's entirely new functionality for cool things like vector layouts (and much more cool stuff).

  • 0

If your target platform is Windows, then C# is really the best way to go these days. The biggest exceptions are if you're doing in-process add-ins for the Windows shell or an unmanaged app, or trying to write "close to the metal" for a super optimized game or something. Or, you know, working on Windows itself :p

That's not to say C++ is going anywhere, but the main reasons it will remain pervasive are that people already know it and already have code written in it. For a new programmer, C# generally makes the most sense. Then if you do learn C++ later on you'll at least have learned a language that's kinda sorta syntactically similar.

  • 0

Visual C++ used to be pretty cool, but I think these days people are just using C# or VB.NET.

C++ is still a language that any worthwhile programmer should be fairly comfortable with. I'm not saying you need to be an expert in it (although you SHOULD be an expert in at least one full-fledged object-oriented language), but if you aren't at least familiar with lower-level things like memory management and pointer arithmetic, you're not fully understanding how programming works and your higher-level code won't be as good.

The bottom line is this: more new projects are being done in C#, so if you're looking for a job right now, C# is probably better to have on your resume. But there's way more code out there that's in C++, so if you're more likely to be maintaining C++ code. Plan accordingly.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!