Hi all,

- fixed synedit highlighter: string constant at line end, drew a special char
- added new pascal highlighter attribute: directive
- CodeTools: added global-write-lock. Update checks are now minimized.
- CodeTools: added codetree-node-cache: This accelerates mass find declaration

Mattias

Hi all,

Updates:
- added new compiler option: LCL Widget Type
- added new transfer macro: $(LCLWidgetType)
This macro contains 'gtk' or 'win32', the value of the compiler option.
- Many options set in the compiler options dialog are now also set in the codetools. For example: find declaration will now consider the unit path.
- added new compiler option: Show Procs On Error, which corresponds to -vb

You can now set the widget type with a simple click (I think, Michael A.H. was the first who wishes this feature). The new option is in Run -> Compiler Options -> Search Paths -> LCL Widget Type. This option sets the transfer macro $(LCLWidgetType), which can be used to create search paths for all widget example: Set the unit search path to

$(LazarusDir)/lcl/units;$(LazarusDir)/lcl/units/$(LCLWidgetType)

New projects will already contain the new macro.

Mattias

Hi all,

Window positions can now be set in various ways. See Environment -> General options -> Desktop. This should fix the window position problems under enlightenment.

Minor updates:
- CodeTools: Fixed node cache range
- fixed 'external' keyword with variables
- fixed linkscanner error messages
- fixed statusbar update on search&replace

Mattias

Hi all,

I have completed the Complete Code insert policies. see Environment->CodeTools->Code Creation. The insert policies define the way, where the Complete Code function will add new variables, method definitions and method bodies. The 'Class part insert policy' defines where variables and property access methods will be added to the class definition. For example:

  property MyInteger: integer;
will be completed to
  property MyInteger: integer read fMyInteger write SetMyInteger;
and it will add two new lines:
  fMyInteger: integer;
  procedure SetMyInteger(const AValue: integer);

If you set 'Class part insert policy' to 'Last' the new lines will be appended to already existing variables/method definitions. So, private variables will grow down. If you set 'Class part insert policy' to 'Alphabetically' the new lines will be inserted in alphabetical order. For example if there is already a variable 'Z: integer;', then 'fMyInteger: integer;' will be inserted in front of Z.

The 'Method insert policy' defines where method bodies will be inserted in the code (e.g. implementation section). The above property write access method 'SetMyInteger' also creates a method body:

procedure MyClass.SetMyInteger(const AValue: integer);
begin
end;

If 'Method insert policy' is set to 'Last' the new proc will be added behind the last already existing method. i.e. new method will be appended at the end. If 'Method insert policy' is set to 'Alphabetically' the new proc will be added behind an already existing method, which is alphabetically in front. So, if you keep your method bodies in alphabetical order, these policy will keep the order. If 'Method insert policy' is set to 'Class order' the new proc will be added at the corresponding code in the class. For example, if you have a method definition

TMyClass = class
  procedure DoSomething;
end;

and you add 'DoIt'

TMyClass = class
  procedure DoSomething;
  procedure DoIt;
end;

Then the new method body for 'DoIt' will be added behind the method body of 'SoSomething'. That means, that the method bodies will be in the same order, as in the the class. I like this most.

Minor updates:
- fixed codetools define for lcl interface directory
- fixed parser: nested record case
- fixed code completion: fixed long property proc splitting
- fixed: compiling via external tools, does now reset error line
- added 'close all' menuitem
- fixed loading codetools options at start
- fixed ttreeview crash on adding root treenode
- added menu shortcuts to keymapping
- splitted keymapping in categories
- added find declaration, find block start, find other block end to search menu
- method jumping will now jump to any difference in variable or type names
- fixed code completion: will now check for redefined procs
- fixed empty line at end of code template
- added codetemplate option: indent to Token/Line start

Mattias

it should fix them but i looks like it raises some new also

why is the source editor window position and size not saved anymore when you quit lazarus? the main lazarus windows size and position is saved

and what are the differences of the options?

i have no jumping around window at all (means using default, restore ..., custom) when using get from wm it creates the main window with guessed 320x200 at its saved position

any clues???

fixed

Window positions were not saved correctly. So, no jumping. With the fixed saving the restore option will create jumping windows under enlightenment.

and what are the differences of the options?

Ok, here are some notes:

"Use windowmanager setting" will not position the window manager will decide where to put it. If it supports some nice geometry management and can restore the windows correctly this will be nice, if not (e.g. sawfish) then it will look like crap.

"Default" let decide the IDE where to put the window. This will create a window layout similar to Delphi. A good start, but probably not what you want.

"Restore window geometry" saves the window positions on every quit and everytime you click OK in the environment options. Next time lazarus starts, these will be restored.

"Custom" allows to explicit define a window position via Left, Top, Width and Height. Use the "Get Position" Button to read the current window position.

"Apply" will show, where the window will be placed next time.

Mattias

"Use windowmanager setting" will not position the window manager will decide where to put it. If it supports some nice geometry management and can restore the windows correctly this will be nice, if not (e.g. sawfish) then it will look like crap.

under enlightenment it looks like crap, too
any window manager known where this works