Lazarus
Announcements => Lazarus => Topic started by: Martin_fr on January 13, 2014, 06:49:18 pm
-
The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2.
We invite all users to test this Release Candidate.
Please read here why everybody really should join the testing now.
News in this Version
http://wiki.lazarus.freepascal.org/Lazarus_1.2.0_release_notes
On Windows the installer now allows 2 independent installations.
http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
About the release process:
http://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch#Roadmap_to_1.2
The 1.2.0RC2 is built with fpc 2.6.2.
The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/
Choose your CPU, OS, distro and then the "Lazarus 1.2RC2" directory.
Minimum requirements:
Windows: 98, 2k, XP, Vista, 7, 32 or 64bit
FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit
Mac OS X: 10.5 to 10.8, LCL on carbon only 32bit, non LCL apps can be 64bit
== Why should everybody (including you) test the release candidate? ==
It the past months the Lazarus team has stabilized the 1.2 fixes branch. The resulting 1.2RC2 is now stable enough to be used by any one for test purposes.
However many of the fixes and new features that were committed since the release of 1.0 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million.
Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.
Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.2.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features.
== How to test ==
Download and install the 1.2RC2.
- On Windows you can install as a 2ndary install, that will not affect your current install:
http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
- On other platforms, if you install to a new location you need to use --primary-configpath
In either case you should make backups. (including your primary config)
Open your project in the current Lazarus (1.0.14), and use "Publish Project" from the project menu. This creates a clean copy of your project.
You can then open that copy in the RC2. Please test:
- Can you edit forms in the designer
- rename components / change properties in Object inspector / Add new events
- Add components to form / Move components on form
- Frames, if you use them
- Can you navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
- Anything else you use in your daily work
-
Download and install the 1.2RC2.
- On Windows you can install as a 2ndary install, that will not affect your current install:
http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
Windows 7 x64; tried x86 Laz.
Used installer to uninstall existing Lazarus 1.0.14, manually removed some leftover files, continued.
Didn't chose 2ndary install.
Open your project in the current Lazarus (1.0.14), and use "Publish Project" from the project menu. This creates a clean copy of your project.
Was stubborn/lazy and did not bother publishing project (IIRC lately opened with Laz trunk anyway)
You can then open that copy in the RC2. Please test:
- Can you edit forms in the designer
- rename components / change properties in Object inspector / Add new events
- Add components to form / Move components on form
Tested, works.
- Can you navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
Yes.
- Anything else you use in your daily work
Switching build modes works (as I had expected ;) )
Thanks.
-
Windows 7 x64; tried x86 Laz.
Used installer to uninstall existing Lazarus 1.0.14, manually removed some leftover files, continued.
left overs are currently normal. The installer only removes what it installed. ppu and o files created by building packages that where installed as pas only leads to leftovers.
-
Yep. I'm not complaining ;) - suppose you actually had something worthwile (projects etc that you had created yourself). It's like the way most installers work.
-
Hi, my OS is Windows 8.1.
i installed Lazarus 1.2 rc 2 + cross compile Win64
i noticed something on Lazarus 1.2 rc1 & rc2 which did not occur with Lazarus 1.0.14
dialog boxes are very slow
i tried TSelectDirectoryDialog in some code source, and encountered the same behavior with Help menu / Help item / File ... Open
then the windows is very slow to answer.
Reported on Mantis : http://bugs.freepascal.org/view.php?id=25529 (http://bugs.freepascal.org/view.php?id=25529)
-
Windows 7 x64: Lazarus 32-bit.
Installation:
- selecting a custom installation path erroneously adds 'lazarus' to the selected path;
- when ticking the box 'Create a new secondary installation' an invalid pop up msg appears complaining that the folder is not empty, and the installation cannot continue;
- when unticking the box above, the warning screen that a 2nd installation exists is skipped for no apparent reason (it should still pop up);
- 'Delete all user configuration files from previous installs' is an incomprehensible message - details missing about what supposedly will be deleted;
- progress screen during installation: FAQ url http://wiki.lazarus.freepascal.org/Lazarus_Faq cannot be clicked (well it can, but nothing happens).
After installation:
- the components window doesn't not honor a taskbar positioned at the left side of the screen.
The object inspector does, but it's way too small and needs resizing.
- panel for editing build modes has become less usable (hidden under a button/pop up).
- Virtual Treeview is broken again (not so much a Lazarus/FPC problem, but a nuisance nevertheless).
Rebuiling the IDE, installing some components: smooth.
Compiling and running some programs (including debugging and heaptrc) looks ok.
Cannot test any other bigger program unfortunately because of the broken VTV.
All in all a smooth start so far, except for the fact that VTV is now unusable.
Guess it's time for a new and more compatible (V)TV. Also because it doesn't work on x64.
-
Windows 7 x64: Lazarus 32-bit.
Installation:
- selecting a custom installation path erroneously adds 'lazarus' to the selected path;
Yes, always been like that (iirc). Need to dive into the inno docs again to change that. / no priority / patch welcome (ONE issue per patch)
- when ticking the box 'Create a new secondary installation' an invalid pop up msg appears complaining that the folder is not empty, and the installation cannot continue;
More details please, I can not reproduce.
- when unticking the box above, the warning screen that a 2nd installation exists is skipped for no apparent reason (it should still pop up);
Indeed, reproduced, if (and only if), next was clicked with the checkbox, (for me back, since I did not get an error preventing going on), and then change checkbox.
- 'Delete all user configuration files from previous installs' is an incomprehensible message - details missing about what supposedly will be deleted;
IIRC inno does only accept one line per checkbox. That would need to be hacked via pascal script (done on other pages already). Again this falls under someday, or patch welcome.
Also to me that is not unclear, other installers have similar opts. Many apps store config, and keep it on the system even if uninstalled .
- progress screen during installation: FAQ url http://wiki.lazarus.freepascal.org/Lazarus_Faq cannot be clicked (well it can, but nothing happens).
It is a memo. So yes. We use inno installer. All modifications are done at runtime via pascal script. I am not sure, if the required system calls to make it a link, are even available.
--
All other issues via mantis please
-
Wow..... I am expecting the coming of 1.2 formal release... ::)
-
Hello,
I've have an issue under the IDE where controls are not correctly sized !
I can reproduce this issue.
I've have already opened a bug with a test case :
http://bugs.freepascal.org/view.php?id=25530 (http://bugs.freepascal.org/view.php?id=25530)
-
- panel for editing build modes has become less usable (hidden under a button/pop up).
The idea was to make it MORE usable and intuitive. The GUI is now visually above the options GUI pages, thus indicating it has effect on them. Earlier it was at the same level with other options, there was no indication of which options the mode affected.
The button and pop up window make it visually separate from the actual options. Did you notice the window has a button for creating "Debug" and "Release" modes?
Typically you don't add more build modes during every session. Instead you add the needed modes once and then select them many times later. The selection is now easier than before. There is a combobox above compiler options and it stays visible whatever options tab you select. Nice, ha!
You can still select a mode from the main IDE window, too.
Please remember also that in the build mode window you can only add and remove modes and change their names. You change the actual compiler options under the selected mode using the normal options tabs.
This is a matter of opinion of course but I wonder why you find it less usable. (?)
What do others think?
- Virtual Treeview is broken again (not so much a Lazarus/FPC problem, but a nuisance nevertheless).
Do you know which LCL change broke VTV?
How actively is VTV maintained now?
-
What do others think?
IMO it's definitely more usable now.
-
IMHO ok,
But the toolbutton on the main ide bar (quick build mode selector / in front of run button) should always be visible.
Now it is hidden, if a project has no build mode. This means: changing project may lead to all buttons moving, and clicking the wrong button by accident.
Also it is useful, to access the options and create build modes, even if none is defined yet.
-
But the toolbutton on the main ide bar (quick build mode selector / in front of run button) should always be visible.
Now it is hidden, if a project has no build mode. This means: changing project may lead to all buttons moving, and clicking the wrong button by accident.
It could be made visible in future, yes. The current behavior is for hiding build modes for people who don't like to use them.
This is a compromise. Many other people wanted to have predefined modes always defined.
Now "Debug" and "Release" are easy to define for those who need them but all build mode related stuff is hidden for those who don't like them.
-
Well, the button (without dropdown) just gets you to the normal project options. No build mode there.
The dropdown is only of use, if there are buildmodes to choose from.
However, if the dropdown is hidden the space must still be used somehow.
Currently, I switch projects (e.g. to a testcase) and the project I open has buildmodes, where as the other one has not, then instead of running it I end up in the options each time. Major annoyance.
This is when I click, I still see the green start button in position. But when he IDE handles the click, it has moved it....
-
Thx for the feedback.
Couple of quick responses.
- when ticking the box 'Create a new secondary installation' an invalid pop up msg appears complaining that the folder is not empty, and the installation cannot continue;
More details please, I can not reproduce.
This happens when you create the installation folder beforehand and already create a new folder inside (I admit, not something everybody would do). I choose to create a new folder and already copied some custom packages in there so I could include them easily. Seems that ticked off the tick box :)
- 'Delete all user configuration files from previous installs' is an incomprehensible message - details missing about what supposedly will be deleted;
IIRC inno does only accept one line per checkbox. That would need to be hacked via pascal script (done on other pages already). Again this falls under someday, or patch welcome.
Also to me that is not unclear, other installers have similar opts. Many apps store config, and keep it on the system even if uninstalled .
I agree it is a well known option to delete all traces of a program during uninstallation.
However I have a couple of Lazarus versions on my PC. Will it delete/uninstall all versions and all config folders (individually set with the pcp option)? That's what makes it scary to choose this option.
Also, if I'm not mistaken, Lazarus does not misbehave by adding to the DLL hell like many other (windows) programs do. So I can simply uninstall a Lazarus version by deleting the installation folder and config path. The one shortcut I have in my quick launch bar can be easily deleted as well.
- progress screen during installation: FAQ url http://wiki.lazarus.freepascal.org/Lazarus_Faq cannot be clicked (well it can, but nothing happens).
It is a memo. So yes. We use inno installer. All modifications are done at runtime via pascal script. I am not sure, if the required system calls to make it a link, are even available.
I know it is.
But it would be cool/look professional if it actually were a hyperlink.
- Virtual Treeview is broken again (not so much a Lazarus/FPC problem, but a nuisance nevertheless).
Do you know which LCL change broke VTV?
How actively is VTV maintained now?
To be honest I think it was already broken in one of the earlier updates (it was working with version 1.0.4).
Whether VTV is still actively maintained I don't know. But it is one of the more impressive components out there and I use it quite often.
-
- when ticking the box 'Create a new secondary installation' an invalid pop up msg appears complaining that the folder is not empty, and the installation cannot continue;
More details please, I can not reproduce.
This happens when you create the installation folder beforehand and already create a new folder inside (I admit, not something everybody would do). I choose to create a new folder and already copied some custom packages in there so I could include them easily. Seems that ticked off the tick box :)
But then it is not empty, so the message is right.
Yes It could have an ignore options. Currently falls under patches welcome.
However I have a couple of Lazarus versions on my PC. Will it delete/uninstall all versions and all config folders (individually set with the pcp option)? That's what makes it scary to choose this option.
Also, if I'm not mistaken, Lazarus does not misbehave by adding to the DLL hell like many other (windows) programs do. So I can simply uninstall a Lazarus version by deleting the installation folder and config path. The one shortcut I have in my quick launch bar can be easily deleted as well.
About dll: QT there is one dll.
About config: By default it deleted the config in the %APPDATA%.... folder. But if you do a 2ndary install (or actually update), it should delete the config in the folder of that installation.
It does not read pcp from shortcuts. It looks for the lazarus.cfg file.
The option originally was added, because sometimes people messed up their install, and uninstalling did not help, as config remained. So the target group usually only has one config.
Yet, I agree, if you are updating a 2ndary install, it could show the path, of the config, that it will delete.
You can add a feature request, but again more than likely: patches welcome.
I know it is.
But it would be cool/look professional if it actually were a hyperlink.
Well yes "would be"...
About the installer and it maintenance: It has somehow ended up on my list. Well mainly because there where a few things that I r*wanted* to be fixed. And 2ndly because I wanted to add the 2ndary installer.
For all else, I have enough other things that I prioritize much higher. So except for really bad bugs ("format c" kind of stuff), I will likely not do much work on it. (hence all the "patches welcome")
If any one wants to pick it up. It would also be nice to have a tool, that detects all files that were moved, and builds a list, of all ppu in the old place. This list can then be put in the installer, and the itnstaller can clean such old files (those must only be files that were actually installed by a previous installer).
That would make updating without uninstalling safer (I did such a list by hand for 1.0.0, but not doing it now)
-
All work is much appreciated Martin_fr.
And as I said overall it's working smoothly. Just throwing in my own pet peeves from time to time :)
Now to contribute something as well on the VTV problem: I did some digging and it seems that the function declarations in the ActiveX unit for the interface IDropsource have changed. The two functions QueryContinueDrag and GiveFeedback (what's in a name) both have a DWORD parameter. That used to be an Integer parameter. No idea when that was changed, but that is what makes the compilation of the package fail.
When in the Virtualtrees.pas file the parameters in the two corresponding functions are also changed from Integer to DWORD, all compiles, installs and works as advertised. Class TVTDragManager. Change the declaration and implementation obviously.
Or just simply try to compile, wait for the compiler to break at the right location and make the change then.
[edit]
Or I could have used the search function on the forum (which in this case gives the correct solution, just not the reason why...)
http://forum.lazarus.freepascal.org/index.php/topic,17389.msg95823.html
-
Sorry to bother everyone, but I could use come confirmation.
Is anyone having trouble with Windows console (CMD) mode programs
just the simplest hello world bombs out at the writeln on line 9.
program TestConsole;
{$mode objfpc}{$H+}
uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Classes;
begin
WriteLn('Hello World!');
ReadLn;
end.
I also get a debugger error, that I captured in a screenshot.
(why do I feel like I just called for a biblical demon, after typing surazal )
-
is it really a console application that you are compiling? Why do I get the feeling that you have not unchecked the gui option as the attached screen shot shows.
-
How can the error be reproduced?
If there are steps, then it should be reported on mantis. (Best to include a coopy of your environmentoptions.xml)
It looks to me as if the IDE tries to restore the compile-info-window, after the debugging finished?
-
I just tested to make sure I didn't screw up.
The IDE, on making a new project, and selecting 'console application' is not setting the W32gui compiler option to off.
But I don't recall having to check it before, and I think it's turning the W32gui setting on in my exsiting project, ...... ummmmm going to test all this is the existing release version of Lazarus and make a report in the bug-tracker.
Thanks for helping, I appreciate it.
-
Hi,
having a problem with 1.2RC1 and 2:
I have a template form with a pagecontrol and 2 tabsheets. One tabsheet has a panel and a toolbar.
This template then is inherited to a new form. When I wanted to add some other components (like edit, comboboxes) onto the inherited new tabsheet-panel, these controls are not shown on the panel but on the parent form itself. So all components appear on each tabsheet, which is not what I wanted. It is not possible to place these controls onto the tabsheets panel andI cannot move these components to the tabsheets-panel in the objectinspector.
This problem is not on actual 1.0.14.
I´m using windows 7 and the 32bit version of Lazarus.
Regard MSC
-
Please report in bugtracker, with compilable actual demo (sources only) that shows the difference between 1.0 and 1.2 branch.
Bart
-
is it possible to install into Program Files on windows with 1.2?
-
Try it but I don't think it'll work due to the version of binutils not liking spaces... see report here http://wiki.lazarus.freepascal.org/Bounties#Windows_8_64bit_Pro_.28Full.2FUpgrade.29
Edit: the 1.2 release notes don't mention anything either so that's fairly definitive I'd say.
Finally: why would you install in program files on modern windows? Wouldn't you need to deal with UAC whenever you try to add a package & recompile?
-
:o I'm just starting to learn how to use Lazarus 1.0.14 and freePascal I would not make a good tester ... >:D
-
I'm not a beta tester but like the improvment things.
What I noticed : TFBAdmin and TFBEventmonitor. Really good tools (now I have to create a small TFBadmin like for myself), but the FPC release make me worry. Release 1.2Rc2 will be delivered with FPC 2.6.2, but in http://wiki.lazarus.freepascal.org/Firebird_in_action#Database_Administration they want explicitly FPC 2.6.3 or higher running.
Will these two tools working in the future releases of Lazarus/FPC?
-
I want to make a case for VTV also. I haven't been able to get it to compile. It worked fine for me in the 1.1 series with FPC 2.6.2.
-
I installed vtv yesterday and I didn't touch a think, it is the same code that I used for my 1.0.10 installation. What exactly is the error you are getting?
-
Is it me or some one disabled the ability to drag a component in negative positions on the designer and if its not me, why?
-
@taazz I just tried this in Lazarus 1.2 RC 2. Seems to work fine. I could drag a button to the left border of the form and further so that part of it became not visible
-
@taazz I just tried this in Lazarus 1.2 RC 2. Seems to work fine. I could drag a button to the left border of the form and further so that part of it became not visible
Same here.
I'm using Linux, FWIW.
-
I tried it again and I definitely can't drag anything on negative numbers. Try it your self place a button on your form set its width and height to 5000 and rty moving it outside the boundaries of the form at your left or top. I couldn't do it. If I set its size to a more logical number eg 50, then it jumps from 0 to -50 in one step it is not smooth as it should be I'm thinking something is very very wrong with the config if no body else has the problem so I'm going to delete the config folder and try it again.
-
I'm Windows 7 win32 same as you, and don't see the problem you're having with the Designer in RC2.
-
removing the cfg folder solved the problem but reintroduced the enter key problem I was having late last year. I'm going to re introduce the xml files one by one to the existing config folder and see which one is creating the problem for me.
-
Perhaps a diff between the xml files is more useful (though I suppose diffing xml files is like diffing bin files... not very useful)? It'll probably be environmentoptions.xml anyway (the biggest => Murphy's law)
-
I just installed new RC2 v1.2.
Perfect, no problem and fast.
PS : I realy like the new feature :
{$IFsomething}
do this;
{$else}
do that;
{$endif}
It high-light at RUNTIME what is true and do darker what is false.
Very impressed (never seen that in other code-editors).
Many thanks.
-
It high-light at RUNTIME what is true and do darker what is false.
Very impressed (never seen that in other code-editors).
Many thanks.
Thanks go to Martin and partly to Mattias on this feature.
-
Many thanks to Martin and Mattias for this feature.
PS: I highly recommend to everybody (even the old Lazarus-users) to take a look and read, from beginning to end, this wiki :
http://wiki.lazarus.freepascal.org/New_IDE_features_since (http://wiki.lazarus.freepascal.org/New_IDE_features_since)
There are lot of hidden gems... ;D
-
http://wiki.lazarus.freepascal.org/New_IDE_features_since (http://wiki.lazarus.freepascal.org/New_IDE_features_since)
There are lot of hidden gems... ;D
And being at this: You really want to read this page too. http://wiki.lazarus.freepascal.org/Lazarus_IDE_Tools
-
There is still the problem of the IDE 'hanging' when a .o file cannot be found.
Was playing with the zenGL demos and that made the IDE stop responding in case of missing .o files.
(Reported (http://bugs.freepascal.org/view.php?id=25611))
-
I have just started testing 1.2RC2 on a recently clean installed Win7 64-bit pro system, running Lazarus 32 bit version - so far a plain single default install without any additions. One issue that I encountered, which may, or may not be a Lazarus problem is running it on a secondary monitor (extended desktop), where I use a third party open source program to get a task bar on the secondary monitor: http://sourceforge.net/projects/dualmonitortb/ (http://sourceforge.net/projects/dualmonitortb/)
Everything is fine until after I minimize Lazarus. On maximizing it, the Lazarus IDE window with the menu bar is gone; there are a number of icons in the second monitor taskbar for the other windows which work switching to, but I cannot get the main IDE window back when clicking it's icon. If I right click the icon, and click the Lazarus IDE link, it just opens a new instance of Lazarus on the primary display. If I instead close the dualmonitor program by right clicking it, Lazarus returns back to normal with its single taskbar icon on the primary display, and the IDE window restored on the secondary display as before minimizing it.
Again, I am not sure this is specific to 1.2RC2 or even a Lazarus fault, but I thought I would report it in case it could lead to some useful insight, as one other program (Nikon Capture NX2) I am running that also is based on multiple undocked/docked windows within the program behave OK with the dualmonitor taskbar. (I do not use the docking solution for Lazarus yet, as last time I tested it about a year ago, it did not work very well for me).
Edit: I did a temporary re-install of v. 1.0.14 and the same issue exists there.
-
What is Subversion URL for Lazarus 1.2?
http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_2
is that correct?
-
1.2 does not yet exist.
But the fixes branch is at http://svn.freepascal.org/svn/lazarus/branches/fixes_1_2
-
hi all,
I need some help on how to connect to Oracle DB in Lazarus. I have the error "OracleConnection1: ORA-12154 TNS: could not resolve the connect identifier specified' when I change the connected property of OracleConnection1 object to True. Note that I can TNSPING oracle without any issue and tnsnames.ora seems to be ok.
can some one please help?
Jean Michel
-
hi all,
I need some help on how to connect to Oracle DB in Lazarus.
snip.....
wrong thread try starting a new thread at the programming\databases category and delete your message from here.
-
After that, read:
http://wiki.freepascal.org/oracle
Maybe help
-
Hi
Thanks for this new release !
I installed and recompiled some various and large applications, and specific packages, without any issue.
The new design for Project, Options, Builds is good.
I have only noticed problems in the french translations, but I don't know if they are expected to be finished.
During installation, some of the first windows are not translated.
The last ones and the readme are OK.
This is strange, probably due to ISS internal translations, or an old release.
In the EDI most of the new features are not translated. And Some old ones are still not properly translated (E.g : "pas à pas approfondi" shown for both F8 and Shift F8, as in 1.0.14).
Do you need a bug report to list what I have found ? Or help to update the translation file ?
Regards
-
just updated my 1.0.14 to 1.2 RC2
Just noticed that when I do the release and debug build modes there is not a huge difference in exe size.
In 1.0.14 the exe size was huge when debugging, not complaining but why is the debug exe size so much smaller now?
-
Never mind,
I see now it defaults to using a external symbol file.
-
First of all, congratulations to the Lazarus team.
I've been following the Lazarus project since the early days. And I I'm glad to see that it is becoming a *very powerful* environment.
Over the years I used lots of tools and several IDE and I must say that Lazarus is probably one of the best, if not the best.
Lazarus efficient, light and fast (not on Mac OS, see below) IDE, multiplatform capabilities, ultra fast native binaries and Object Pascal friendly and easy to read code, makes it a formidable tool.
But on Mac OS there are several (near) show stoppers.
I've been using 1.2 RC2 for MacOS Leopard 10.6.8, for several weeks now and I would like to report several bugs I found:
1. The first thing I experienced is that RC2 refused to load. I had to recompile Lazarus with the 'clean all' flag in order to be able to use it.
2. One of the (almost) show stoppers for Lazarus in Mac Os is the terrible slowness of the Source Editor. At least in my dual core MacBook.
I thought that this would be fixed in RC2 but this behavior still exists.
When I select the Source Editor window, the CPU usage of Lazarus jumps to 40%. Scrolling, typing and debugging is very slow and uncomfortable. It is like coding in slow motion :)
If I select any other window in Lazarus, for example, the Code Explorer, the CPU usage drops to 0. Or if I switch to another application the CPU drops to 0.
3. Also I noticed that 'indent selection' y 'unindent selection' do not work.
That's it for now.
Thanks again and keep up the good work! :)
Hoch.
-
2. One of the (almost) show stoppers for Lazarus in Mac Os is the terrible slowness of the Source Editor. At least in my dual core MacBook.
I thought that this would be fixed in RC2 but this behavior still exists.
Well I am not aware, that his was reported by anyone. So there is (was) no work/investigation into that.
And afaik, for many people this does no happen, for them it works fast.
Please read and reply the new thread I opened for this issue:
http://forum.lazarus.freepascal.org/index.php/topic,23494.msg140283.html#msg140283
-
One thing I noticed is when I create the two build modes (release and debug) the debug build mode has the
heaptrc unit option checked by default, this is actually annoying because by default it shows the heap trace info in a message box and
some third party libs show a lot of info and the message box can't handle the amount of data and the OK button goes off the
screen.
Also is there a way to have the release and debug as the default for all projects?
-
Also is there a way to have the release and debug as the default for all projects?
.....
-
One thing I noticed is when I create the two build modes (release and debug) the debug build mode has the
heaptrc unit option checked by default, this is actually annoying because by default it shows the heap trace info in a message box ...
It only shows a message box on Windows. The option can be unchecked easily, although the best solution would be to fix this issue:
http://bugs.freepascal.org/view.php?id=19837
Also is there a way to have the release and debug as the default for all projects?
Yes, there could be another option for that, maybe in the build mode manager window.
I did not consider it important because clicking the button is so easy.
Creating those modes is behind a button because not all users wanted to use or see build modes at all.
-
One thing I noticed is when I create the two build modes (release and debug) the debug build mode has the
heaptrc unit option checked by default, this is actually annoying because by default it shows the heap trace info in a message box
That is why I build all my debug builds with -WC
Then they have a console, and the info goes there.
If I need to catch it, I can use a logfile.
-
Laz 1.2RC2 on win32 issue:
When I save a project that has a Lazreport component on it that I made a change to I get this error:
[Window Title]
Streaming error
[Content]
Unable to stream MainReportMod:TMainReportMod.
Illegal character
Path to failed Instance:
TMainReportMod.report.ReportXML
[Abort] [Retry] [Ignore]
I have not been able to resolve this issue, any ideas?
-
Also is there a way to have the release and debug as the default for all projects?
.....
Thanks Tazz, I totally did not see that.
The version I have of rc2 does not have a build mode tree node in the project options, but it does have the use compiler settings as default.
it does work perfectly though, thanks.
-
The version I have of rc2 does not have a build mode tree node in the project options,
Nobody has it any more because the GUI for build modes was moved above the compiler options.
but it does have the use compiler settings as default.
What is that? I didn't understand your meaning.
-
The version I have of rc2 does not have a build mode tree node in the project options,
Nobody has it any more because the GUI for build modes was moved above the compiler options.
but it does have the use compiler settings as default.
What is that? I didn't understand your meaning.
No worries, it's cool, works great now that I know I can set the compiler options as default.
-
Maybe I missed it but after I set a build mode there is no visual indication of what build mode you are using.
Would it be possible to put the build mode name after the project name in the main title bar? Or maybe at least change the hint of the
drop down to change the build modes so there is some indication of what mode you are currently using.
For the title bar:
Lazarus IDE v1.2RC2 - Project1 (debug)
Lazarus IDE v1.2RC2 - Project1 (Release)
Or for the menu item, have two icons one with a red gear to indicate debug and one with a green gear to indicate Release.
I think just the title bar would be sufficient though.
Just a thought.
-
No worries, it's cool, works great now that I know I can set the compiler options as default.
Ok, right, "set compiler options as default" checkbox. It has been there for long.
Did you find the Build Mode GUI? It is above the project setting panes. First you must enable "Build Modes" checkbox. Then you can add and modify modes.
-
yes, it's only visible when I have the debugging tree node selected in project options.
The screen shot Tazz showed had the build modes as a tree node item, which was a bit easier to find.
-
yes, it's only visible when I have the debugging tree node selected in project options.
Oh, that sounds like a bug. It should be visible for any compiler options pane. Can you please check again.
Now is the last moment to fix bugs before 1.2.
The screen shot Tazz showed had the build modes as a tree node item, which was a bit easier to find.
I have problems seeing screenshots in this forum, including this one.
Anyway, earlier the build modes had a tree node item and a pane.
It was side-by-side with the actual project options and there was no visual indication of which build mode was affected when changing the options.
Now the GUI for build modes is visually above the project options and you see all the time which mode is affected when changing options. You can also change build mode without leaving a settings page, and you can more easily see differences between 2 modes. Ain't it cool?
Maybe my mind works differently also with this issue. I felt the old build mode GUI was confusing but the new one is intuitive.
Some other people have felt the opposite. Such is life ...
-
Sorry,
yes it does show for all the compiler options.
The only issue I see with it is no visual indication of what mode you are currently using.
Maybe if debug mode is selected show the icon as a gear with a bug on it so we are currently using the debug build mode.
Not a huge deal about the visual indicator.
Great work guys :-)
-
The only issue I see with it is no visual indication of what mode you are currently using.
Maybe if debug mode is selected show the icon as a gear with a bug on it so we are currently using the debug build mode.
Well, the combobox caption "Debug" is also a visual indication, but yes, an additional icon is a very good idea.
"Debug" and "Release" modes could have predefined icons but a user could add his own icons for other modes.
Great work guys :-)
Thanks. Slowly but surely it advances.
-
The only issue I see with it is no visual indication of what mode you are currently using.
Maybe if debug mode is selected show the icon as a gear with a bug on it so we are currently using the debug build mode.
Well, the combobox caption "Debug" is also a visual indication, but yes, an additional icon is a very good idea.
"Debug" and "Release" modes could have predefined icons but a user could add his own icons for other modes.
Yes, when you are in the project options dialog,but when it's closed and your just in the IDE working on something there is no indicator of what build mode the IDE is currently
set to. What I am proposing is when the build mode name = 'Debug' then change the icon in the IDE toolbar to a gear with a bug on it instead of a gear with a wrench.
Or add the debug name to the IDE main form title bar, which right now shows "Lazarus IDE v1.2RC2 - Project Name" but I don't think it would by to far of a stretch to have it in
addition to displaying the project name also show the current build mode name for the project, if it's default then don't show anything, but if it's release or debug then show that
along with the project name i.e.
"Lazarus IDE v1.2RC2 - Project1:Debug"
This would be handy for when you come back to a project and you would immediately know what build mode its in.
Just a idea :-) Feel free to use it if you like :-)
I will post a mock up of what I am talking about.
-
Toolbar mockup for build mode indicator.
-
Toolbar mockup for build mode indicator.
A patch would be even better. :)
But yes, good ideas. In fact there are many good ideas floating around but only few people who implement them.
-
Modifying the Icon, how is it going to work? Debug and release are not the only build modes.
They may not even be defined at all, while someone has plenty other build modes.
Adding it's name to the IDE title, seems a much better idea
-
Modifying the Icon, how is it going to work? Debug and release are not the only build modes.
They may not even be defined at all, while someone has plenty other build modes.
Adding it's name to the IDE title, seems a much better idea
Well,
for anything other than Debug and release show the standard gear icon, if lowercase(buildmodename) = 'release' then show the release icon
do the same for debug.
Obviously the icon thing would only work for build and release and if someone modify them to My Release it would show the default icon.
having it in the IDE caption would be nice as well.
I would take a look at it, but I don't even know where the toolbar form or code is. I looked in the source directory and nothing popped out as being the IDE toolbar.
-
What real advantage has modifying the icon, over adding it to the title.
Something that outweighs the limitation to just 2 randomly selected build modes?
The fact that they can be created with a button, does not (IMHO) make them any more important, than any other buildmode would be.
Even, if the proposal was to add both (title and icon), I would at this point still question the icon (for it still is good that needs maintaining (or being there, when other code in maintained), but does not bring a benefit).
-
What real advantage has modifying the icon, over adding it to the title.
Something that outweighs the limitation to just 2 randomly selected build modes?
The fact that they can be created with a button, does not (IMHO) make them any more important, than any other buildmode would be.
Even, if the proposal was to add both (title and icon), I would at this point still question the icon (for it still is good that needs maintaining (or being there, when other code in maintained), but does not bring a benefit).
I am fine with it just being in the title caption as well. Just ideas :-)
-
Laz 1.2RC2 on win32 issue:
When I save a project that has a Lazreport component on it that I made a change to I get this error:
[Window Title]
Streaming error
[Content]
Unable to stream MainReportMod:TMainReportMod.
Illegal character
Path to failed Instance:
TMainReportMod.report.ReportXML
[Abort] [Retry] [Ignore]
I have not been able to resolve this issue, any ideas?
Anyone have any ideas on how to resolve this streaming error with Laz report on 1.2RC2? win32 Windows 7?
I should add the project in question was working fine with LazReport in 1.0.14.
-
was working or it still works fine on 0.14? can you upload a minimal sample for me to test?
If you revert your 1.2RC2 lazreport to the one you have on your 1.0.14 installation does it work then in 1.2RC2?
-
I got it working, I had to remove the laz report component from the datamodule and recreate it.
Works fine now and I can't see any difference between the one I deleted and the the new one I dropped on the form.
For whatever reason it could not stream the saved report to the form for storage.
oh well works now.
-
I just noticed that the build number auto increment works like it should in 1.2RC2 :-)
In Laz 1.x the number that got stored to the resource was 1 less than what the project properties said.
Looking forward to the final release :-)
-
I am fine with it just being in the title caption as well. Just ideas :-)
Lazarus 1.3 Revision 43949
Must be enabled in options first. (Because other such options are off by default too, like showing the path). Default is a "cleaner" title.
-
I just noticed that the build number auto increment works like it should in 1.2RC2 :-)
Can you please look at this:
http://bugs.freepascal.org/view.php?id=25683
I will look at it, too, but now I have something else going on...
-
I am using an i7 PC with Linux Mint 16, Cinnamon. [EDIT -- 1.2RC2]
Jedi Code Formatter halts at conditional defines like those below.
{SIfdef Win32 or Win64}
Do something...
{$Endif}
{SIfdef Linux}
Do something else...
{$Endif}
The conditionals are defined in Project | Project Options | Other
If I comment out the {$Ifdef } statements then the JCF works.
Am I doing something wrong?
-
I just noticed that the build number auto increment works like it should in 1.2RC2 :-)
Can you please look at this:
http://bugs.freepascal.org/view.php?id=25683
I will look at it, too, but now I have something else going on...
The issue I had in Laz 1.x was the version number stored in the application resource was always one less than what the project options said when the auto inc option was enabled, it was fine when you manually incremented it. Not sure if that bug report is the same issue.
Seems to work fine in 1.2rc2 though.
-
Seems to work fine in 1.2rc2 though.
Only when using Shift-F9 (Build). Updated the issue.
-
I think I have finally isolated a problem with the Jedi Code Formatter.
(1.2RC2, Intel i7, Linux Mint 16, Cinnamon, 64 bit, GTK2)
I submitted a rather garbled bug a few days ago, and concluded I had made an error. Could someone please test and confirm the code below, and I will resubmit it.
When an If ... Then block is split with an {$Ifdef}...{$Endif} construct, the compiler handles it, but the JCF does not. The following code snippets illustrate this.
Create a project with a single form.
In Project/Project Options/Other add the conditionals 'Red' and 'Blue'. (Case should not matter.) Select one of the conditions. leave the other unselected.
This works in JCF:
procedure TForm1.FormClick(Sender: TObject);
var
myBool: boolean;
begin
MyBool := True;
{$IfDef Red}
If MyBool then Form1.Caption := 'Red'
else Form1.Caption := 'Black';
{$Endif}
{$IfDef Blue}
If MyBool then Form1.Caption := 'Blue'
else Form1.Caption := 'Black';
{$Endif}
end;
This does not work in JCF:
procedure TForm1.FormClick(Sender: TObject);
var
myBool: boolean;
begin
MyBool := True;
if MyBool
{$IfDef Red}
then Form1.Caption := 'Red';
{$Endif}
{$IfDef Blue}
then Form1.Caption := 'Blue';
{$Endif}
end;
[Edit] Adding an Else after the blocks also appears not to work very well.
-
Seems to work fine in 1.2rc2 though.
Only when using Shift-F9 (Build). Updated the issue.
Ok, it does seem to only increment it in the exe if you do a build and then a compile right after.
Just doing the build increments it in project options, but not in the exe resource.
Prior to 1.2 I don't remember it incrementing in the exe if I did a compile right after the build, it would never show the correct version number in the exe in 1.x from what I remember. I had to turn off the auto inc feature and do it manually.
-
More problems with Lazreport.
I had a issue with lazreport on a project I opened up with 1.2RC2 before with a stream read error, and I just got it again on
a more substantial older project.
This project has a couple of reports and one is on a form and it worked just fine, the other one is on a datamodule and it gives the
stream read error when I try and save the project. The report on the datamodule lost all the objects in the bands when I opened it as well.
The other project I had the problem with also had the report on a datamodule, so the problem with the stream error seems to be if the Lazreport from 1.0.14 etc was on a datamodule.
UPDATE:
I restored a older copy of the datamodule with the report on it from my SVN repository and the lfm file from the 1.2rc2 has totally messed up the reportxml that lazreport uses and appears to have converted it to a binary form. The lfm from before I opened it with 1.2RC2 had a report.xml with text based XML in the LFM file. It appears that when a 1.x project is opened with 1.2rc2 it's doing something to the data module LFM file and pretty much wiping out the stored LazReport XML.
I can't be the only one that has used Lazreport by putting the report on a datamodule. I will see if I have any other projects from 1.x that I put the report on a datamodule.
To get the XML back I had to open a older copy of the project on 1.x then copied the report to a form in the project, I then copied that form to the 1.2 copy of the project and opend it, then copied the good report from the form to the datamodule.
UPDATE:
The report on the datamodule was stored as reportform and was binary.
The report on the form was stored as reportXML and was in the LFM as plain text XML.
Not sure but it might be the version of LazReport shipping with 1.2RC2 does not know what to do with reportform and binary data in the LFM.
It seems that in 1.x Lazreport was storing the report on a form differently than on a datamodule.
Has anyone else noticed this behavior?
Update 3:
seems to be related to this:
http://bugs.freepascal.org/view.php?id=24756#bugnotes
In my case it seems the reports I had on forms where converted in 1.x but not those on datamodules.
-
Hi
I have some remarks and question, only about the cross compiler installation.
1)
The install title, displayed several time during install is "Lazarus" which might be confusing. 'Lazarus cross compiler" or something more specific would be better and might prevent mistakes.
2)
I installed Lazarus in "c:\Lazarus\1.2RC2" (not the default location, but could be). When choosing the installation location of the cross compiler, I browse to the same directory, but the path displayed after choosing it is "c:\Lazarus\1.2RC2\lazarus". Is it a correct choice ? If we confirm the default location and do not browse for another, the installation folder is set to the same directory "c:\lazarus".
3)
In addition, and if possible, it would be smarter if the cross compiler was for ISS "a patch" of the corresponding version of the IDE. I do not know if ISS have such functionnality, but with other product I uses this allows to remove the question for an install location and reduces risks of mistakes
.
Best regards
Tintinux
-
1 and 2: please report on mantis.
2: You need to remove the extra "lazarus"
IIRC the main installer, adds the same, if you change location.
3: If it did not ask then you could not install it with the secondary install.
Keep in mind, that you can have several installations of the same version.
Yes there could be checks, if the selected folder contains an installation. Patches for this will be welcome.
-
Will there be a Lazarus 1.2 RC3?
http://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch#Roadmap_to_1.2
Is it possible that Lazarus 1.2.0 FINAL to be released around 2014-03-01?
http://bugs.freepascal.org/roadmap_page.php says:
Lazarus - 1.2.0 (Scheduled For Release 2014-03-01) = 98%
Packages - 1.2.0 (Scheduled For Release 2014-03-01) = 100%
Patches - 1.2.0 (Scheduled For Release 2014-03-01) = 100%
-
This is actually an open decision, that will probably be made in the next 7 days.
*IF* there is an RC3, then release will be a month later.
-
take the time needed to do a great release. I would rather see a RC3 and wait a bit for a 1.2 final.
-
Windows 7 ultimate 32 bit, openSuSe 13.1 32bit Gnome, Lazarus 1.2.RC2 works perfect.
Regards!
-
I have been working with RC2 for over a month and it works fine.
However an RC3 wouldn't be a problem.
-
Any chance that someone could review the vertical scrolling methods used in this great IDE? Vertical scrolling does not work in the editor with the track point on my Lenovo Compact Bluetooth keyboard, opposed to the one on my T440p, and with scroll whell on a mouse. It works in all other applications except Notepad++ and Chrome above version 31 (They introduced new minimalist scroll bars in v. 32). I understand there are also issues in Chrome with USB version of that keyboard. The scrolling mouse cursor shows up in both cases but is different. The one on the Bluetooth keyboard will scroll any window below the cursor (and the scrolling mouse cursor has some vertical lines added to it), while the one on the computer requires a window be the selected to scroll. This is with "Lenovo preferred scrolling method" turned on which should basically be the same as result mode on a mouse. Some writings on the Chrome support pages could indicate that there is a problem with the program requiring the name of the window to scroll, but not getting it.
The two finger vertical scroll on the pad of the computer also does not work, but in this case the scrolling mouse cursor is similar to the one with the computer's trackpad that work, so this could be a separate issue. Horizontal scroll works with any method. I also tested the scrolling example, and the same vertical scroll problem is present there. This problem is not unique to 1.2 RC2, the same happens in earlier versions, tested v. 1.0.14.
-
@otoien: please open a bug report with exact details about your system and the behaviour you see.
You could also try with current development/trunk version of Lazarus to see if scrolling behaviour has improved. If so, a backport to the Laz 1.2.x series could probably be made fairly easily.
Thanks.
-
About scrolling:
related to: http://bugs.freepascal.org/view.php?id=25209
Other IDE windows do scroll? (e.g. Object Inspector?)
For the bug report, not here on the forum, please put some debugln into
procedure TCustomSynEdit.WMMouseWheel(var Message: TLMMouseEvent);
(file synedit.pp / line 7163)
And capture see output (log file --debug-log=)
See if it is called, and what params are passed
debugln(['WHEEL ',Message.X,' ',Message.Y,' ',Message.WheelDelta]);
-
Thanks for the responses both of you, and please bear over with me being a bit slow here, things are pretty new to me, and I am trying to find my way around things.
As a start I can confirm that the scrolling issue also affects Object Inspector, Code Explorer and windows like the Debug Output, but not surprising it does not affect the file dialogs as Windows probably is responsible for those. I assume this means the problem is not limited to SynEdit? One little thing is that when first clicking a window and trying vertical scroll I may occasionally get a scrolling response on the very first attempt (may happen with both the bluetooth keyboards trackpoint and two-finger scroll with two-finger scroll on the Thinkpad T440p, but on the next attempts to scroll, it remains unresponsive. So perhaps it is a timing issue with respect to catching the mouse messages? I do use another compiler IDE, mikroPascal for dsPIC, that as far as I know is also based on SynEdit, but written in Delphi 2007, and I have no scrolling issues in that compiler.
I am not sure that the bug report referenced by you Martin is the same as the bluetooth keyboards trackpoint scrolling, but it may well be the case for the two-finger scroll on my T440p which seems different, and that is a Synaptics trackpad. While the bluetooth keyboard trackpoint, vertical scroll does not work in Notepad++, the two finger scroll on the computer does. There are two different issues on the Chrome pages, the one related to the bluetooth keyboard is this one: http://code.google.com/p/chromium/issues/detail?id=335941.
I was able to register on the bugtracker page, but I did not want to enter the bugreport before I have all the information, and I am not sure I got the debug output to work with RC2. (I found a proper place to insert the line at the end of the TCustomSynEdit.WMMouseWheel procdure ). Where is the log file supposed to be written and how is it named? (The info in the debug output windows does not seem to output any related information.) I am working on learning how to download and install the trunk/SVN version; my computer is so new that I have not configured much in Lazarus yet, so I might just as well install it over RC2? Would the patch mentioned in the bugreport already have been included in the SVN version or do I have to learn how to install that one?
-
Generally:
If a bug report is marked as closed, an included patch is probably included. Probably because the developers can choose to implement another solution or not, so you'd have to go by the comments in the report.
Also, the revision number of the change is marked in closed bug reports; you can track exactly what was implemented using subversion tools, e.g. example for revision 44287:
http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision&root=lazarus&revision=44287
If the report is still open, a patch has probably not been included.
-
If it happens in all windows, (except the dialogs, which indeed a handled by windows), then you do not need to add the line to SynEdit.
Instead you should apply the patch that is attached to the issue, and see if that helps.
Not sure what patch command best to use (I use TortoiseSvn, but you might need an svn checkout for that to work). There is a "patch.exe" in the fpc binaries folder, and IIRC the wiki has some article on using patches.
(If it crashes, use notepad++ to change the line-endings.)
should be
cd lazarus
patch -p0 < synaptics_new.patch
-
Thanks Martin,
I tried tried ToroiseSVN, and not surprisingly it reported it was "not a working copy".
I tried the command line patch after copying patch.exe to the lazarus window, it just opened up a black window with no report. Nothing appeared to have been added to win32callback.inc. Not surprising as the svn listed in the patch is lower than the one in RC2, so line numbers might have differed for the patch to work. Inspecting the patch in TortoiseSVN, it marked pretty clearly where the patch was to go, so I patched win32callback.inc manually by editing the code.
After Lazarus rebuild, as suspected, the patch fixed the problem with the two-finger scroll on the Thinkpad T440p touchpad in the editor and object inspector etc, but not the problem with vertical scroll with the Lenovo Compact Bluetooth keyboard. (The scroll bar example still does not work, but even before the patch, it would also not work with my bluetooth mouse, only the trackpoint on the T440p. The IDE does work with the Bluetooth mouse, so this might be a problem with the example).
So I assume I should file a separate bug report for the Bluetooth keyboard, and perhaps one need to look into whatever solution the Chrome project find to that (see my last reference above). Yesterday there was one report that it worked in the latest version of Chrome after another fix, but I have not tested that as I have disabled Google update beyond v. 31 until I have a god confirmation that it is fixed.
-
Yes probably best to open another bug report, and mention the findings that where made until now. (Also that it is not fixed by the patch)
It will probably someone other than me, who will look at it. I picked up this thread because the editor/synedit was mentioned. SynEdit is my domain.
In any case, it may be useful to see what happens in wint32callback.
Where you added the code:
GetClassNameA(SynapticsWindow, SynapticsClassName, 50);
if SynapticsClassName = 'SynTrackCursorWindowClass' then
TargetWindow := Window;
Add the following:
GetClassNameA(SynapticsWindow, SynapticsClassName, 50);
debugln(['WHEEL ', SynapticsClassName,
' W=', dbgs(Window),
' TW=', dbgs(TargetWindow),
' MWRedir=', dbgs(InMouseWheelRedirection)
]);
if SynapticsClassName = 'SynTrackCursorWindowClass' then
TargetWindow := Window;
-----------
You can also *Always* (without condition) do
TargetWindow := Window;
This will disable the "follow mouse" behaviour, that is scroll will apply to the focused window, instead of the window below the mouse.
-
Thanks a lot, removing the condition gave me the vertical scrolling as you predicted, I am very happy, as I have become very addicted to using the trackpoint for scrolling, and it is very efficient and saves a lot of repetitive movements!
The interesting thing is that it still is able to scroll even if the window is not selected, i .e the window is just under the mouse cursor. Another interesting thing is that the way the selected "Thinkpad preferred scrolling" in the Keyboard setup is supposed to work is to only act on the selected window, not the one under the cursor, at least this is the way it worked when I initially tested the keyboard on a WinXP system. But on Win7 it acts on window under the mouse cursor. Perhaps there is a bug in the driver under win7 that confuses certain applications?
The scroll example still do not work though, either with the bluetooth keyboard trackpoint or the mouse scroll wheel, only with the trackpoint on the computer itself. Might be a different problem perhaps.
I have not been able to make the log file output work. Before rebuild, I turned on the debugging option under configure build Lazarus, and as instructed in the wiki FAQ, "How can I use a Log-file for debugging the IDE itself", I run it with parameters --debug-log=lazarusdebuglog.txt in the shortcut or activated from the command line, but no logfile seen in the lazarus folder.
Should I still do the bug report or would just adding a comment about the findings to the current one be more appropriate?
-
There is a bug with the logfile. (will be fixed in next release)
Specify a full qualified name --debuglog=C:\foo\bar.txt
-
Still no debug log file. Rebuilt lazarus with the debug option on in the configure build lazarus.
Then started lazarus with the command line:
lazarus --debuglog=C:\lazarus\debuglog.txt
I am still running 1.2 RC2. Anything else I am missing? I see a number of debug statements inserted in the code elsewhere. It occurs to me that the file would become big very quickly when catching mouse messages?
-
Sorry this was my fault, I missed a dash
--debug-log=c:\log.txt
The log will grow yes, but it will be reasonable, if you only use it for a minute or two.
-
Thanks, got it working now, I have one log with (scroll not working) and without (scroll working) the conditional statement. Should I now create a separate bug report as initially planned to upload those logs?
-
probably, unless you have enough knowledge to say it is the same issue. You can always refer to the other bug, so they can be set to be related.
-
Thanks, bug report submitted.