Lazarus Release Candidate 1 of 1.2

[Edson]

Can you check the source file in tools\install\win\lazarus.es.isl ?

It is OK, but it is on UTF-8 on my PC. I'm using Win7 Starter, all in spanish.

That is because according to the Rules of most OS (incl Windows) config goes into a special folder in the users home dir.
So the primary goes into %appcondir%/lazarus   (or0 maybe app_local_conf)

I think we don't need to follow the rules for a second installing. It could be the same path that we choose for the Second installation. It would be simpler for the user.

[Martin_fr]

I think we don't need to follow the rules for a second installing. It could be the same path that we choose for the Second installation. It would be simpler for the user.

The installation may run as admin, and the path may not be writeable to the user. What then?

If you want to add options and sent a patch, we can discuss what is acceptable.
E.g.
- a set of 2 buttons to fill in 1) the conf in install; 2) the path to %localappconf% + random none existing folder
- Or a list of proposals with radio buttons.

It is a bit of work though.


My current point is:
- I think it is wrong to offer ONLY the "conf in install"
- I will not work an it in the foreseeable future

[Martin_fr]

About the Spanish: I did sent you a PM, maybe it is utf8 vs ansi.

[jwdietrich]

Is there anywhere a precompiled version for Mac OS X PPC available or have I to build it myself?

[Edson]

About the Spanish: I did sent you a PM, maybe it is utf8 vs ansi.

It's OK now. Thanks. There is some text in English yet, but it's another problem

I think we don't need to follow the rules for a second installing. It could be the same path that we choose for the Second installation. It would be simpler for the user.

The installation may run as admin, and the path may not be writeable to the user. What then?

I just suggested to use the same Path used for installation. If you can install there, you can write. Or probably, I'm not understanding the problem.

[Martin_fr]

Is there anywhere a precompiled version for Mac OS X PPC available or have I to build it myself?

For now you have to build it yourself.  Hopefully in future it can be provided again.

[Martin_fr]

The installation may run as admin, and the path may not be writeable to the user. What then?

I just suggested to use the same Path used for installation. If you can install there, you can write. Or probably, I'm not understanding the problem.

If I can install there as admin, I may not be able to write there as user when using it. Admitted this may be rare, but (if nothing is broken) that should be possible (afaik). All files that are created, if you rebuild, should then end up in the primary-conf. (At least from what I understand).

This can also bring other conflicts.
- Some people want to delete the config, if they uninstall, or if they just delete the folder.
- Other people expect, that they can remove and delete the install folder, and the conf is still there. (After all it was/is like this with many apps and with current Lazarus too)

If the user has to take an action to set the conf folder inside the install, the the user is (or should be) aware.
If the user just clicks "next", then he/she may not be aware.

Another option in to add more explaining text to the page. But again, I am not going to spent any of my time on that. The only time I will spent is applying patches (except setting the conf inside the install, WITHOUT any user interaction.)

[marc_dsb]

The installation of RAUDUS component was not successful, the message error "RaCreatorFPC.pas(72,12) Fatal: Can not find RaCreatorFPC used by RaudusFPC, C:\Users\usuario\Documents\Raudus2\bin\fpc262\i386-win32\RaCreatorFPC.ppu, package RaudusFPC" (Win 7 Home)

Was successfuly installed on Windows XP under VIRTUALBOX.

Was tipycally installed on windows 7 home version 1.010  FPC 2.6.2

Thanks for the good works !!

marc_dsb       

[hinst]

How very interesting. I tried enabling easydockmgr package after installing this version of Lazarus and once again source editor window gets stuck inside the main window. I guess it is a feature then
This bug was present about two years ago I think. Is this the "wrong" docking manager? I keep forgetting which one I should use "anchor" or "easy".
Anyway, neither of them is usable. Well, they are usable to some point, but both contain bugs. Docking never works like it should for me. Is it just me? Or am I the only one who uses docking?

[zamtmn]

>>Or am I the only one who uses docking?
not one. I use anchordoсking ... it is far from ideal, and goes from the release to release in this state

[hinst]

Screw docking. I found another bug. Which makes IDE unusable.
Every time I click File -> Open it shows Open File dialog and then crashes immediately.
I rebuilt the IDE using debug configuration, here is what I got:

C:\Lazarus_1.2_RC1>Lazarus.exe
using config file C:\Lazarus_1.2_RC1\lazarus.cfg
SetPrimaryConfigPath NewValue="C:\Lazarus_1.2_RC1\USERSETT_INGS" -> "C:\Lazarus_1.2_RC1\USERSETT_INGS"
TMainIDE.ParseCmdLineOptions:
  PrimaryConfigPath="C:\Lazarus_1.2_RC1\USERSETT_INGS\"
  SecondaryConfigPath="C:\Lazarus_1.2_RC1"
TIDEAnchorDockMaster.MakeIDEWindowDockSite MainIDE:TMainIDEBar
TIDEAnchorDockMaster.LoadUserLayout anchordocklayout.xml
TIDEAnchorDockMaster.LoadUserLayout restoring ...
TSourceEditorSharedValues.GetMainLinkScanner CodeBuffer=nil
TSourceEditorSharedValues.GetMainLinkScanner not a pascal source: unit1.pas
TIDEAnchorDockMaster.ShowForm AControl=ObjectInspectorDlg:TObjectInspectorDlg NeedPlacing=True Floating=True
TIDEAnchorDockMaster.ShowForm placing ObjectInspectorDlg:TObjectInspectorDlg ...
TIDEAnchorDockMaster.ShowForm creator for ObjectInspectorDlg:TObjectInspectorDlg found: Left=0 Top=120 Right=+230 Bottom=-120 DockSiblingName= DockAlign=alNone l=0,t=200,
r=230,b=750
TIDEAnchorDockMaster.ShowForm MakeVisible ObjectInspectorDlg:TObjectInspectorDlg l=0,t=0,r=300,b=669 Floating=True
here I click "Open..."
TApplication.HandleException Access violation
  Stack trace:
  $000000010001A2C8
lazarus.pp - unhandled exception
[FORMS.PP] ExceptionOccurred
  Sender=EAccessViolation
  Sender=EAccessViolation
[FORMS.PP] ExceptionOccurred

No stack trace actually. Despite the fact that I built it with debug information enabled. Well, Lazarus executable file size is 197 megabytes now, so I am pretty certain that debug information is included now. Too bad it does not appear in console.
It crashes right after I click "Open" menu item, not when I choose some file. I don't even get to choosing file. Open File dialog appears and stays on screen just long enough to notice the presence of it. And then it crashes and "Application stopped working" standard Windows dialog window appears.
---
Windows 8 Pro 64bit

[Martin_fr]

* AFAIK *

EaysDocking was once contributed. No idea if it will be maintained at all, unless the original contributor picks up issues (last seen march 2012, If I am correct). Or patches are submitted.

AnchorDocking, was started by Mattias, it does actually receive fixes (according to SVN). But it is still beta (afaik), and will probably still be for a while.
I do not know what the priorities on this are.

[hinst]

What about "crash on open file" bug? [which I described in my previous message in this thread] Should I post it to bug tracker? Anyone else experienced it?
P.S.: looks like it also crashes when I click "new unit" button on the toolbar
P.P.S: I am talking about >this< version of Lazarus 1.2 RC1

[Martin_fr]

The "crash on open file" is a knows problem, and a report already exists.
(Well most likely, the same as you experienced)

It is a win 64 bit issue afaik, and it is due to missing SEH support in current released FPC.

It is fixed in fpc 2.7.1, but apparently can not be backported to 2.6.x

It affects the IDE and user apps.

You can sue the 32 bit IDE, with the 64 bit add on. Then you have a stable IDE, and you can build, run and debug 32 and 64 bit apps.

However, compiling 64 bit apps only is useful if they do not need SEH.

-----------------
That is all I know on the topic.

If you need further info, best to open a dedicated topic.

[Martin_fr]

P.S.: looks like it also crashes when I click "new unit" button on the toolbar

That shouldn't use any file dialog, so it should be reported (works fine on my 32 bit win)