![]() ![]() (*) Well, there is some rudimentary support for WideString's and some basic string manipulation functions for WideString exist, but the vast majority of D7's built-in functions are AnsiString-only. Why re-invent the wheel, when newer Delphi versions provide proper Unicode support "out of the box" and excellent GUI frameworks, such as Qt, are available for free? This means you would have to replace all the GUI code as well.Īfter all you would be writing your own Standatd Library as well as your own GUI Framework (more or less), which is a tremendous amount of work. Moreover, and even more important, all the GUI components in D7/VCL do not support Unicode either. This means that you would have to replace all of D7's built-in functions - at least those that use a String parameter or return type - with your own Unicode-aware versions. But all* the "built-in" functions of D7 use the String type and thus will never support Unicode. Sure, you can explicitly use the 'WideString' type in all your own code. Well, the native 'String' type of D7 is a synonym for 'AnsiString', so everything that uses the String type does not support Unicode - at least not as UTF-16. ![]() I implemented unicode support in D7, it's very doable. (I know that there is Free Pascal and Lazarus, but the last time I tried to compile my Delphi projects with Lazarus, there were a whole lot of compatibility problems) Unfortunately the price is beyond what I am willing to pay for my "homebrew" projects. lack of Unicode support.ĭelphi is still under development, now by Embarcadero. Mainly because my Delphi 7.0 feels a bit dated nowadays, e.g. ![]() Personally I did a lot of projects with Delphi and only recently made the switch to C++ with Qt. Last but not least, and probably most important: If you already have a big project written in Delphi (Object Pascal), porting that to C++ is a huge amount of work! Still Delphi is a great "all in one" package for developers. Some are painful (MFC) others are more fun to use (Qt). ![]() There are frameworks to create GUI applications with C++ too. That's like having a cheap radio shack digital volume control sitting in front of your DAC, before going to amplification.Why still ues Delphi to compiled? use msvc is good!ĭelphi is an IDE for creating GUI applications with Pascal (actually an object-oriented derivative of Pascal), while MSVC is a C/C++ compiler :rolleyes: I completely agree w/ poster that the preamp part of the foobar deform the sound, and it should've had the option to disable it. When u have a volume/preamp layer in the code, it's there then, even if u set it 0db, or just leave it 100%. Now even if there are new builds w/ that option working, I'm still curious, why would an "audiophile" software player doesn't have an option to "bypass everything" per se. I could never be able to disable the volume on foobar,someone on the forum said setting volume control 0db or something like that, which didn't work for me. Jriver came out ahead on my listerning test, but that's not the point. Several months ago, after I did a new install of xp (I'm a programmer by trade, refresh is a quarterly business), installed asio4all, I got (foobar+foobar_native_asio_plugin) against (Jriver+jriver_native_asio_plugin) against (winamp+otachan_asio.dll) against Media monkey. So people.STOP SAYING FOOBAR TO BE THE BIT PERFECT HOLY GRAIL, ITS NOT! You like foobar, but haven't tried setting up the poster's approach and denounce it as no improvement.Īnd quanghuy147, I know EXACTLY what you mean, I asked the same question.why the heck the volume still work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |