Re: [Lazarus] Lazarus-CCR - mplayer package
On Sun, 15 Jun 2014 02:39:51 +0200 Michael Thompson mike.cornfl...@gmail.com wrote: [...] Once I'm happy with my additions, I'll upload a patch to the bugtracker. It's open source. Commit early, commit often. Ahh, I hadn't realised. Thought I would need to be added to the Lazarus-CCR developers group in SourceForge before I could commit there. Of course you need access rights to sf to commit directly. I meant: Don't wait with the patch until the code quality is fully mature. It's ok to provide a patch every few days. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] copy from Topenglcontext
My Version uses glReadPixels, result is TBitmap, this can easily be atteched to the cliboard. Function OpenGLScreenshot: TBitmap; Var dim: Array[0..3] Of Integer; c: Array Of Array[0..3] Of Byte; z, i, j: integer; TempIntfImg: TLazIntfImage; ImgHandle, ImgMaskHandle: HBitmap; CurColor: TFPColor; Begin // Auslesen der Framebuffer Auflösung glGetIntegerv(GL_VIEWPORT, @dim[0]); // Erstellen des Bitmaps result := TBitmap.create; result.pixelformat := pf24bit; result.width := dim[2]; result.height := dim[3]; TempIntfImg := TLazIntfImage.Create(0, 0); TempIntfImg.LoadFromBitmap(result.Handle, result.MaskHandle); setlength(c, dim[2] * dim[3]); // Auslesen des Framebuffers in einen temporären Speicher glReadPixels(dim[0], dim[1], dim[2], dim[3], GL_RGBA, GL_UNSIGNED_BYTE, @c[0, 0]); // Umschreiben des Temporären Speichers in das TBitmap z := 0; For j := 0 To result.height - 1 Do For i := 0 To result.width - 1 Do Begin CurColor.red := c[z][0] * 256; CurColor.green := c[z][1] * 256; CurColor.blue := c[z][2] * 256; // c[z][3] wäre der Alphakanal, aber den Braucht man ja hier nicht ... TempIntfImg.Colors[i, j] := CurColor; inc(z); End; TempIntfImg.CreateBitmaps(ImgHandle, ImgMaskHandle, false); result.Handle := ImgHandle; result.MaskHandle := ImgMaskHandle; TempIntfImg.free; End; On 06/14/2014 12:13 PM, Michalis Kamburelis wrote: Andrea Mauri wrote: Dear all, Is it possible to copy the content of OpenGLContext to the clipboard? How can be done? You could also copy the contents of OpenGL context (created by TOpenGLContext or any other similar control) using glReadPixels, and then convert the resulting bytes into a TBitmap instance. Then you can copy TBitmap contents to clipboard like Anton shows, using Clipboard.Assign (see http://wiki.lazarus.freepascal.org/Clipboard#Load_from_clipboard ). Using glReadPixels and then converting the result will be cross-platform, as opposed to Anton's solution using Windows.CreateCompatibleBitmap . Michalis -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- Auf meiner Homepage www.Corpsman.de ist immer was los, ständig wird sie aktualisiert und erweitert. Da ist für jeden was dabei. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] when start Compile, IDE locking everything
On Sat, 14 Jun 2014 14:25:00 +0300 FreeMan freema...@delphiturkiye.com wrote: Hello, I'm try some code, get from lnet example. copy folder to different folder, and change some path and code. project work any error, just click compile or shift + f9 IDE lock in some work, and its in threaded work, 'cos I can minimize or focus to any form. Do you have high CPU load? Can you see (e.g. with top) what process is using the CPU? The compiler ppcx64 and/or lazarus? My idea is searching some pathsfiles, its been endless loop. This is just idea 'cos no any message or error show up. Last test for find bug: open IDE project (via open last saved project), click directly compile button on toolbar in IDE editor, its compiled, click one more, compiled too. Open options from project inspector directly click to Ok then click to compile and bingo, IDE locked. if cancel on options no problem. just when save(ok button click) project options. Kubuntu 14.04 x64 svn fpc lazarus svn 45510 Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] when start Compile, IDE locking everything
15-06-2014 11:19 tarihinde, Mattias Gaertner yazdı: Do you have high CPU load? Can you see (e.g. with top) what process is using the CPU? The compiler ppcx64 and/or lazarus? Yes , So I said endless loop. lazarus has %12 - %13 cpu usage on i7 cpu http://forum.lazarus.freepascal.org/index.php?topic=24876.msg150230;topicseen#new this error has on me too, please check this message 'cos sent demo project too, if you need mine project I can sent it too. more detail: Change source, (for need save flag) without save, click compile or shift f9 and IDE locked -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] when start Compile, IDE locking everything
On Sun, 15 Jun 2014 11:30:55 +0300 FreeMan freema...@delphiturkiye.com wrote: 15-06-2014 11:19 tarihinde, Mattias Gaertner yazdı: Do you have high CPU load? Can you see (e.g. with top) what process is using the CPU? The compiler ppcx64 and/or lazarus? Yes , So I said endless loop. lazarus has %12 - %13 cpu usage on i7 cpu http://forum.lazarus.freepascal.org/index.php?topic=24876.msg150230;topicseen#new this error has on me too, please check this message 'cos sent demo project too, if you need mine project I can sent it too. more detail: Change source, (for need save flag) without save, click compile or shift f9 and IDE locked Can you create a bug report with this project? Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] when start Compile, IDE locking everything
15-06-2014 11:38 tarihinde, Mattias Gaertner yazdı: Can you create a bug report with this project? I did. ID is #0026341 I attached my demo too. its lnet demo small modified. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Can't compile SVN Lazarus, missing lislazbuildisnoninteractive
Missing line: lazarusidestrconsts.lislazbuildisnoninteractiveabortingnow='%s%s%s%slazbu'+ 'ild is non interactive, aborting now.' in lazarusidestrconsts.rst is causing following error when building Lazarus from SVN, revision 45521 and later: lazbuild.lpr(356,72) Error: Identifier not found lisLazbuildIsNonInteractiveAbortingNow lazbuild.lpr(366,72) Error: Identifier not found lisLazbuildIsNonInteractiveAbortingNow -- ~ Juraj Pekar -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] nonlcl design basic issue
Hi Lazarus gurus, looking further into nonlcl designer, a very basic question arose to me. My custom widget designer must be aware of my custom widgetset, otherwise it would be unable to know their properties. But my custom widgetset has dependencies on a lot of non-lcl units, and many of them conflict with an LCL counterpart. I can think only of two ways to go: 1. Surrounding with appropriate $IFDEF LCL / $ELSE the sources of my widgetsets to differentiate what should be visible at design time from what should be visible at run-time. 2. Going the same way as LCL, and taking advantage of an interfaces unit, which provides the actual implementation of virtual methods. Any suggestion? Thanks, Giuliano -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] nonlcl design basic issue
On Sun, 15 Jun 2014 18:45:27 +0200 Giuliano Colla giuliano.co...@fastwebnet.it wrote: [...] 1. Surrounding with appropriate $IFDEF LCL / $ELSE the sources of my widgetsets to differentiate what should be visible at design time from what should be visible at run-time. Pro: code navigation is easier (e.g. jumping between active implementation and interface) Con: you can only work in one part at a time (many codetools will only work in the active IFDEFs). You have to switch often the active build mode. 2. Going the same way as LCL, and taking advantage of an interfaces unit, which provides the actual implementation of virtual methods. Pro: You don't need build modes. Con: You often have to search the implementation of abstract base methods. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Can't compile SVN Lazarus, missing lislazbuildisnoninteractive
On Sun, 15 Jun 2014 18:29:05 +0200 Juraj Pekar pekar.ju...@gmail.com wrote: Missing line: lazarusidestrconsts.lislazbuildisnoninteractiveabortingnow='%s%s%s%slazbu'+ 'ild is non interactive, aborting now.' in lazarusidestrconsts.rst is causing following error when building Lazarus from SVN, revision 45521 and later: lazbuild.lpr(356,72) Error: Identifier not found lisLazbuildIsNonInteractiveAbortingNow lazbuild.lpr(366,72) Error: Identifier not found lisLazbuildIsNonInteractiveAbortingNow Fixed. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] nonlcl design basic issue
Il 15/06/2014 19:57, Mattias Gaertner ha scritto: On Sun, 15 Jun 2014 18:45:27 +0200 Giuliano Colla giuliano.co...@fastwebnet.it wrote: [...] 1. Surrounding with appropriate $IFDEF LCL / $ELSE the sources of my widgetsets to differentiate what should be visible at design time from what should be visible at run-time. Pro: code navigation is easier (e.g. jumping between active implementation and interface) Con: you can only work in one part at a time (many codetools will only work in the active IFDEFs). You have to switch often the active build mode. 2. Going the same way as LCL, and taking advantage of an interfaces unit, which provides the actual implementation of virtual methods. Pro: You don't need build modes. Con: You often have to search the implementation of abstract base methods. Thanks a lot. That's more or less what I was aware of, and having it confirmed by your authority makes me more confident, but I was secretly hoping that you'd pull out of your hat a third way, with just pro's and no con's :-( . FYI My widgets are a port to fpc of the Kylix widgetset, which I never contributed because of license issues, but which are already pretty much debugged. I can use Lazarus IDE to compile them, and to compile applications using them. What I miss is the ability of taking advantage of Lazarus IDE for visual design, because of many differences in properties. My goal, now that I should have some time to spare, is to be able to take advantage of Lazarus IDE, to use it's gorgeous features, and to get rid of Delphi's, requiring a 2.4 Linux kernel, in order to support some one hundred or so applications written with Kylix. Playing with IDE designer shouldn't take as long as converting all of them to Lazarus, and, most of all, should be much more fun. So I think I'll go the first way, which should affect only design time, but shouldn't change my run-time widgets. One more thing: with a design-time-only package including the Designer, and a run-time-only package not including it, will I avoid to pull into my executables the IDE Designer stuff, and all the LCL-related stuff? Any hint to avoid pitfalls? Thanks again, Giuliano -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
