FredS

8 minutes ago, Ian Branch said:

Instead of having to delete the directories

Once you have a git repo all you need is Pull: https://git-scm.com/docs/git-pull

7 hours ago, PeterBelow said:

with no project or project group open

RSP-14289 is still open and a comment suggests it still plays this way in Rio..

Created: 24/Apr/16 4:05 PM

2 hours ago, Markus Kinzler said:

Seems no problem for embt.

The coveted Enterprise sector will just love this..

8 minutes ago, WillH said:

registration procedure that is excessively restrictive to use

No argument there, but at least you can 'unregister' and move without problems, if you crash you can get it up for a fixed fee.

Checking this ability in the Delphi License Manager this morning showed the mess that is, plus I didn't see a place where it shows how many activations you have left either which means that the only time you find that out is after digging yourself out of a crash situation.

9 hours ago, Vincent Parrett said:

AFAIK there's no way to deactivate or deregister an install.

Got that confused with IBExpert which has that feature and a fixed price for reactivation after your subscription elapses..

45 minutes ago, Vincent Parrett said:

you MUST offer deactivation or a means to move licenses

Not sure, thought that exists..
However there is no way to deactivate after a crash.

Either way, what you owned yesterday is today only a rental.. and at the mercy of a 'rude' renewal department at that..

10 minutes ago, Attila Kovacs said:

"we need your money"

To me it sounded like 'the litigation department is bored'..

6 hours ago, edwinyzh said:

Holy, EMBT never cease to amaze me.

From the GM: New Updates and Changes to the Registration “Bumps” Policy

" We updated our processes and now route all issues raised from users who are not on Update Subscription to Sales and Renewals. "

21 minutes ago, David Schwartz said:

this is the first evidence of it

I often wonder how many issues in a mature product are actually the misuse of Version Control..

Just now, WillH said:

perpetual license

It appears that feature is no longer implemented..

5 hours ago, Der schöne Günther said:

The task still lives

Tasks can stay idle for something like 5 minutes and then longer in the retired state.

6 hours ago, Rudy Velthuis said:

extremely hard to work around

Not an issue, as I said before 99.9% of the time recompiling fixes it. For the remainder, commenting out a line , any line, do a build all then uncommenting the same line will fix it..

1 hour ago, Rudy Velthuis said:

should perhaps restart the IDE

Yeah, except yesterday I tried to compile that project via msbuild and it still generated the same error:

25 minutes ago, dummzeuch said:

Delphi 10.3

RSP-11530 was fixed for Rio, which means it should also show the correct Build.

8 hours ago, dummzeuch said:

Are you sure about that?

Yes, one of the first things I did back in XE7.

However

Writeln(TOSVersion.ToString);

returns: Windows 10 (Version 10.0, Build 0, 64-bit Edition)

Because in in TOSVersion.Create:

    if not GetNetWkstaMajorMinor(MajorNum, MinorNum) then
      GetProductVersion(kernelbase, MajorNum, MinorNum, BuildNum);

The call to GetNetWkstaMajorMinor doesn't return a Build, if it failed GetProductVersion would have returned the correct Build.

3 hours ago, dummzeuch said:

they made their WinAPI function GetVersionEx lie

OK but.. it reports compatibility which may be important to know..

Of course TOSVersion has always reported the correct version, blatantly ignoring any attempt by M$ to lie 🙂

2 hours ago, PeterPanettone said:

number of bugs

It may be time to focus on the positive news, three new skins have been released since Rio.
Just waiting for all Development Managers to each write a blog about this exciting new feature 🙂

36 minutes ago, dummzeuch said:

It's really annoying that it is that complicated

There is a benefit in maintaining your own fork, wish it was simpler to find the most up to date fork though and fork that 🙂

Also generating a branch before a making a pull request isn't a big deal as long as one knows about that..

2 hours ago, Schokohase said:

For each pull request you need a branch

Didn't know that, here is a way to do that within GitHub

3 hours ago, Stefan Glienke said:

loops in a kinda readable way.

I was adding something to a tested function and the only way I could justify not retesting all of it is by using 'goto'..

17 minutes ago, Mike Torrettinni said:

first time

Used my first 'goto' a couple of weeks ago 🙂

39 minutes ago, Remy Lebeau said:

In those modes, it tries to closely emulate Delphi 7 or 2009, depending on whether Unicode is being emulated or not. 

Check, so the free tool can downshift to accommodate Delphi 🙂

http://wiki.freepascal.org/Helper_types#record_helper

25 minutes ago, PeterPanettone said:

any other bugs

Stefan's link shows 75 bugs.. then there are those 'secret' internal ones..

18 minutes ago, Dalija Prasnikar said:

found and fixed

Those are two different things, but using your release to beta test your tool set isn't really for everyone..

1 hour ago, Stefan Glienke said:

then look for Assert.something calls

Good idea but here is what happened:

1. Was unable to generate the Internal Error this morning
2. The Project Group also contains some components so I right clicked and ran 'Install'
3. After that a 'Build' generated the Error
4. Commented out all 'Assert.'
5. After a bit of tweaking all compiled
6. Was not able to reproduce the Error by running 'Install' again
7. Uncommented chunks of 'Assert.' until I could generate the Error
8. But commenting those back in still generated the Error after running 'Install'

As I have postulated for years, the compiler appears to get confused about which directory its in or something else internally goes haywire.
The degree of which appears to get better or worse with each release..

Just to be clear; 'Install' is executed via the context menu so the active project does NOT change in the Project Group. Certainly rhymes with the 'I did a few things and it broke' we see a lot..