Forum > Lazarus
Lazarus Release Candidate 1 of 4.0
flowCRANE:
I installed Lazarus 4.0 RC1 and there are problems with the coloring of the code editor. Some options have changed (relative to what was previously set), and some do not work, i.e. despite the color set, they do not color the given editor element.
The ObjectPascal -> Modifier element was set to Bold even though I don't use bold style anywhere.
The second problem is that Gutter -> Gutter was previously set to black (RGB 10,10,10), but after installation it became gray (default system color) and even if I change its color to black, it is not applied (see attachment). Applying new colors does not change anything — gutter color is ignored.
jamie:
https://www.youtube.com/watch?v=Vh51gDpIzeQ
Thats all I have to say about this subject.
ccrause:
I recently started testing RC1 on Linux Mint Mate and noticed that Lazarus would die when plugging in/out an external monitor into the laptop. Below the last bit of output from the launching terminal:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---TCodeHelpManager.GetHTMLHint Exception: include file not found "systemh.inc" (lazarus:63793): Gdk-CRITICAL **: 12:48:22.173: IA__gdk_screen_get_monitor_geometry: assertion 'monitor_num < screen_x11->n_monitors' failed (lazarus:63793): Gdk-CRITICAL **: 12:48:22.174: IA__gdk_screen_get_monitor_geometry: assertion 'monitor_num < screen_x11->n_monitors' failed (lazarus:63793): Gdk-CRITICAL **: 12:48:22.179: IA__gdk_screen_get_monitor_geometry: assertion 'monitor_num < screen_x11->n_monitors' failed (lazarus:63793): Gdk-CRITICAL **: 12:48:22.183: IA__gdk_screen_get_monitor_geometry: assertion 'monitor_num < screen_x11->n_monitors' failed (lazarus:63793): Gdk-CRITICAL **: 12:48:22.188: IA__gdk_screen_get_monitor_geometry: assertion 'monitor_num < screen_x11->n_monitors' failedThe program 'lazarus' received an X Window System error.This probably reflects a bug in the program.The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 21248483 error_code 9 request_code 14 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
I use the following script to start Lazarus:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---#!/bin/sh# Fix for synedit receiving double characters: qwerty => qqwweerrttyyexport GTK_IM_MODULE=gtk-im-context-simpleexport QT_IM_MODULE=simpleexport XMODIFIERS=@im=none ./lazarus --pcp=~/lazarus/4.0rc1/.lazarus
Any thoughts on where to start digging?
Note that I haven't noticed this with previous versions, or with the main version from ~ September 2024.
ASBzone:
--- Quote from: piola on November 11, 2024, 12:26:08 pm ---
--- Quote from: ASBzone on November 01, 2024, 12:26:22 am ---
--- Quote from: piola on October 30, 2024, 10:15:24 am ---I'd like to encourage the Lazarus maintainers to provide a "Lazarus 4.0 with trunk FPC 3.3" release in addition to the regular one with FPC 3.2. There are so many great features in trunk meanwhile, but it's horribly compilcated to get it working properly. So please, an FPC 3.3 with Lazarus 4.0 release would be a great option!
--- End quote ---
This is why tools like FpcUpDeluxe exist
--- End quote ---
Yes, but FpcUpDeluxe unfortunately uses an entirely different directory structure than official Lazarus releases. So it's not an option for me.
--- End quote ---
Can you help me understand why that matters? If you use FpcUpDeluxe to get the configuration you want, won't you keep using it for ongoing maintenance of the development environment as well?
Mark Paley:
Thank you for the Lazarus 4.0 release candidate.
I have been testing it within an isolated QEMU Virtual Machine, running Windows 7 x64. I've also cross-compiled my own applications to x86_64-linux, copied the resulting executables to my linux home directory, and run them there -- all without incident.
I especially like the appearance and usability of the new docked IDE.
I have to ask: since you're creating a new installer anyway, could it also ask to apply Whole Program Optimization to the entire Lazarus IDE itself during the installation compilation process? Lazarus could really stand out from the crowd (Delphi, CodeTyphon, dBase, Python...) in execution speed if LAZBUILD defaulted (or had an option) to WPO the entire IDE itself.
Full disclosure: I created/posted the wiki section "https://wiki.freepascal.org/Whole_Program_Optimization#Concrete_Lazarus_IDE_example". When creating that methodology for applying WPO, I couldn't help thinking that there really should be a simple checkbox in the compilation options to apply WPO (basically doing the steps shown in the wiki for the user).
Navigation
[0] Message Index
[#] Next page
[*] Previous page