Leaderboard

It is my experience that issues with the installation are usually targeted quickly. I know what you mean, but if we stop filing bug reports to notify them about existing stuff not working they will have more time to add unwanted features. Even if the chances for a filed bug to be fixed are pretty low, they are still higher than those for a bug not filed at all. After all 10.3.1 fixes more than 150 reported bugs, which were probably still not fixed if they weren't be reported in the first place.

No I would not because its not a list but a set which are implemented as bitmask and thus have a fixed order.

Somehow I totally missed this, but in october 2017 Microsoft did a complete U-turn on deprecating OleDB database connectivity. They have even released new OleDB providers for MS Sql Server which will be maintained and updated with the most recent server features. https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-release-of-ole-db-driver-for-sql-server/ https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-2017

So that it is also ignored as all the other high voted bug reports, that will probably never be fixed? It seems to be more important to add unwanted features than to get the existing stuff working.

New Delphi, old bugs, including serious: I think I’m slowly starting to Understand Delphi Hater's blog... RSP-23466 RSP-23320 + hundreds of others.... I wonder if this will ever happen, to manage this product properly, why do they think that developers needs tons of new usless features instead of making fast and solid current functionality.

Strictly speaking assuming a specific order in a for-in loop is wrong to begin with.

Here a small working demo project how to get translations.. translation api.zip

That's what I was referring to in your previous post https://stackoverflow.com/questions/4950129/delphi-for-in-loop-set-enumeration-order and https://stackoverflow.com/questions/1600575/iterate-through-items-in-an-enumeration-in-delphi

https://quality.embarcadero.com/browse/RSP-14452 P.S. Probably only GetIt was fixed...

StyleControls VCL is a powerful package of components, which uses Classic drawing, system Themes, GDI+ and VCL Styles. This package contains the unique solutions to extend standard VCL controls and also has many unique, advanced controls to create Windows 10 Modern UI Applications (UWP design). UWP-like form can be used with VCL Styles or System Themes, because controls have flexible solutions for adjusting. Note, that all windows has a native DWM system shadow (and with VCL Styles too). http://www.almdev.com

Then you need to figure out what that logic is, it's not word boundaries: https://regex101.com/r/bnXElq/1

Does that function ReplaceWords() work for you? http://codeverge.com/embarcadero.delphi.general/stringreplace-with-a-whole-word-on/1063318

Splitted bands (displaying long HTML) Video

First, it would be nice if you posted at least the title of the report here, and not just a link... Not a great report; it is unclear exactly what issue is pointed out in the report, and "difficult to reproduce" in steps isn't going to help matters. If you are affected, you could improve chances of a fix by adding something helpful in comments.

I said it before (to somebody else on a different topic: Please file a feature request on SourceForge. That way all these are in one place and whenever I find time I can look if something there looks interesting. Anything mentioned only here will most likely be forgotten in no time. (And no: I am not going to write these feature request entries for people who can't be bothered. I prefer spending my time on more interesting things. You get to use GExperts free of charge and profit from my work, so do your duty. - Sorry if this sounds harsh, but my time is limited.)

What about the people who you are asking for help? I would post on one site first, and if you don't get a good response, then post elsewhere, with link to the first place.

Actually it's "EMB" text compression, probably they should patent it and proudly add in About product information. Much better than LZ4, LZO or LZMA, because it's 3d multilayer

First impressions count.

If you want to keep your settings you should answer NO. The question is about removing the settings.

From their website

@Silver Black I guess it is "expected". So many files are envolved, it will takes more time to check and update then deleting everything and installing again.

I just fixed two (newly reported) bugs in GExperts: The Set Tab Order dialog no longer worked in Delphi 6, 7 and 2005. This was due to me adding AlignWithMargins (and the associated Margins property) to the dfm file. This property apparently was introduced in Delphi 2006. Again, this underlines what I mentioned several times: I do not use Delphi < 2007 for anything but testing and fixing bugs GExperts. That’s why glitches like this tend to slip by unnoticed. That’s why I would like people to volunteer for testing the various versions. But apparently nobody can be bothered. Fine by me, but you will have to live with the consequences. I don’t have a QA department. The extensions to the Uses Clause Manager caused several thousand (small) files to be created in the GExperts configuration directory. This directory is located under AppData\roaming\GExperts which means it will be copied when roaming profiles are enabledin a Windows domain. I didn’t know that anybody still uses roaming profiles since they are usually not worth the trouble, but apparently they are still being used. So I now moved that cache to AppData\local and also added a config option to disable caching altogether. https://blog.dummzeuch.de/2019/02/09/two-gexperts-bugs-fixed-14-to-go/

I'm here!

I agree with Erix A. Settings or parameters should be stored in a file, not in registry. A. in developing time maybe you will modify your settings by hand and modify registry is so trouble. B. If you release your APP, maybe user want modify settings manually not by using your APP UI, modify a file is more easy. And if you want to separate your logic code and UI, you should use object. In this object your code can settings from file or save to file, and other module in your APP like UI module needs this settings data, just access this object. So this settings module is a independent module for other modules reuse it. What kind of file for store your settings data? A ini file, TIniFile can access it. Or you can serialize your settings object to JSON or XML strings and save it into a file, etc. And you can store your settings into a SQLite database file. Settings should be strings that human can read, should not be binary, cause sometimes man want to modify some parameters by hand. I prefer using TStringList to read and write parameters, cause TStringList has three functions: 1. It can work as Key=Value mode. 2. It support SaveToFile and LoadFromFile. Your object which maintain setting parameters and your UI can interact by DataBinding mechanism of Delphi then you do not write code to synchronize UI and parameters object, and object with file.