Jump to content

David Szkilnyk

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. David Szkilnyk

    Delphi 12: internal errors

    At the start of Feb, using D12, I spent quite a few weeks porting and testing a couple of million LOC. Opinion, the IDE is a joke, this has to be the worst IDE I have seen, QA needs to be sacked. These are just some issues I have noticed, note I use it every day. - the toolbars are wrecked - the menu system doesn't appear. - the layout on opening Delphi on my machine opens 1in wide no matter how many times I save a new layout. - the evaluate dialogs constantly expand and expand upon reopening. - code insight hangs the system from time to time especially when trying to do a for loop syntax. The nice things are the compiler is faster at least with my application, I have gone from 6min builds back to under 2mins. The debugger is working even on a standard compile rather than a build. 10.3.3 would only let us Debug once before the IDE had to be reloaded. As for the code base so far it's looking very promising. My app is in QA's hands now looking for issues. But overall it looks a little faster on painting of vcl/forms something has changed I haven't picked what yet. Given the IDE is not in a great state it is still workable for me at least. So far I am pleased.
  2. David Szkilnyk

    IDE adds <ProjectExtensions> twice in .dproj file

    We got a similar corruption on upgrading a project 10.2.2 to 10.3.1 . It literally destroyed the .dproj but due to the IDE reapplying a number of settings it wasn't obvious. What we found though was certain options in Project Options windows just completely vanished and left us stumped as why we couldn't compile anymore. In the end we just re applied ever from 10.2.2 and it all worked again. The only thing we had done to prior this issue arising was we were adjusting our licensing information transfer keys. regards Dave.
  3. David Szkilnyk

    Rio 10.3.1 Debugger is often dead after a second build.

    Ok its been awhile as I had to ditch it and go back to the previous version to get some work done. Anyhow tried all the above options no luck. What I did find that worked to a point was I am currently building with msbuild externally to compile (true). Well if I set it to false I can get a compile or two before I run into memory issues. But it does reset the debugger and enable me to use it. But alas if msbuild option back to true debugger fails again. Time for a support ticket me thinks.
  4. Not Happy, and very time consuming to get anything done. Steps Open fresh IDE. Build to debug the application. Perform debugging to view some execution of code. Either Terminate session or even run till application is shutdown. Make changes. Debug Build again Run and all breakpoints have failed and Debugger is no longer working. Ok this a very large win32 Vcl desktop application. Debug exe is compiling in at 300meg. Did not have this issue in Tokyo. Nothing special in it other than your standard component libraries and Devexpress libs. I have seen this before in earlier version of Delphi but this version seems to be really bad. Anyone experience this? Or seen a solution? Regards Dave
×