Uwe Raabe

There is a new beta available. Changing the version number to 15 resembles not only the completely different new look due to theme support and new icons, but also the internal changes necessary to make all this work. Hopefully I didn’t break too much.

Could it be that the new form was auto-created in the dpr when it should not?

Is this even on new projects? (Can't check here in the moment)

1 hour ago, Bill Meyer said:

I assume, however, that you are implementing for v14, not for earlier versions? Most of my work is in D2007

I am referring to a command line tool.

1 hour ago, Bill Meyer said:

Moreover, I want to organize so that Delphi library modules are in the first grouping, then third-party, and last, units of the application. And then, of course, to provide for walking the file tree and applying changes to each application module found in the map file. 

Are you interested to do some testing?

In addition the LSP can run as a background thread parsing while you type and then providing the results asynchronously.

Well, the actual problem here are the conditionals around the uses keyword and the closing semicolon. The rest inside is fine.

This version is handled without problems:

{$if defined(DEBUG) or defined(DEBUG_SPECIAL)}
uses
{$IFDEF DEBUG}
  dialogs
{$ENDIF}
//<some comment about the following ifdef>
{$IFDEF DEBUG_SPECIAL}
  mmsystem, // timeGetTime()
  messages
{$ENDIF}
  ;
{$ifend} 

While working on a tool for cleaning up uses clauses I stumbled upon this beast (slightly changed to protect the innocent):

{$if defined(DEBUG) or defined(DEBUG_SPECIAL)}
uses
{$ifend}
{$IFDEF DEBUG}
  dialogs
{$ENDIF}
//<some comment about the following ifdef>
{$IFDEF DEBUG_SPECIAL}
  mmsystem, // timeGetTime()
  messages
{$ENDIF}
{$if defined(DEBUG) or defined(DEBUG_SPECIAL)}
  ;
{$ifend} 

If you are only looking for uses clauses inside some Delphi sources and try to avoid a full featured parser, you will have a pretty hard job to detect, parse and interpret that one correctly.

So, if you are interested to make any use of such a tool, please do me a favor: Don't write your code that way! It is hard to read for humans anyway.

1 hour ago, EricNZ said:

Sorry, I missed that link as it wasn't obvious.

I know and I will see what I can do about it.

In the MMX download page click on Previous Versions.

Did you try this?

{$IFOPT C+}

8 hours ago, Bill Meyer said:

Sort the class(es).

I filed a feature request for a new sort option to normalize the code while sorting.

23 minutes ago, Bill Meyer said:

Sort the class(es).

AFAIK, that won't work.

As an alternative you can use the built in Delphi code format feature with <Ctrl>-D.

33 minutes ago, Bill Meyer said:

Actually, it does, or did, convert existing.

It does. When the cursor is somewhere in that method (declaration or implementation) pressing <Ctrl>-E followed by <Enter> to open, close and accept that dialog will unwrap these lines.

24 minutes ago, Attila Kovacs said:

Maybe because I have Autosave Project Desktop on?

Habits and expectations differ, so setting this option to ones personal favor is not bad in the first place. There is only one thing to remember when switching that off: The project desktops are opened in the state they were last saved.

To solve your problem:

• switch this option on
• load a project
• close all forms
• close the project
• switch option off again

9 hours ago, Esteban Pacheco said:

Where did you "released" this library?  github?  the url provided doesnt have links to the library.

Perhaps Roberto is going to sell that library?

You can use the approach shown in TArray from System.Generics.Collection:

type
  TMyExtArray = class(TArray)
  public
    class procedure DeleteElement<T>(var Values: TArray<T>; const Index: Cardinal);
  end;

class procedure TMyExtArray.DeleteElement<T>(var Values: TArray<T>; const Index: Cardinal);
begin
  if (Index < Low(Values)) or (Index > High(Values)) then begin
    raise EArgumentOutOfRangeException.Create('argument out of range');
  end;
  System.Delete(Values, Index, 1);
end;

Note that handling different types (intrinsic, pointer, reference counted) in the implementation part can be a bit tricky.

The problem with a bad framework architecture is not that the framework is unusable. If you are only using the framework the internal architecture may be of less interest.

The documentation is misleading there. The command line switch for not loading the last project is -np.

Currently my favorite is 10,2.3 as it provides the most features with a good stability. Given that it needed 3 updates to get there, I still have hope for the 10.3 branch.

1 hour ago, Rollo62 said:

My first wish would be that Styles would be enhanced to be more flexible and vector-based

The original FMX styles were actually vector based. IIRC that was replaced by bitmaps for performance reasons.

In most cases the widened list is of only limited benefit when the selected item doesn't fit into the edit field either.

In my Rio installation GenDocCLI.exe can be found in the Delphi bin folder. Also the context menu of the project model has a Generate documentation item. Are you aware that these features are part of Architect and Enterprise only?

The Tools menu entry is also missing here. Actually I cannot remember even having it seen before.

Named Pipes may not be the badest decision here. See François Piette blogging about that: Inter Process Communication Using Pipes

Could it be that Z: is a network drive causing that trouble?