Re: [Lazarus] Using event driven components in console application

> Having to have that library is unfortunate, but is a fundamental > requirement since Qt exposes a C++ API which is not directly usable by > FPC. If you start looking too closely at that point, you have to > question the wisdom of using non-mainstream tools... I really don't want > to go there.

Re: [Lazarus] Using event driven components in console application

JuuS wrote: On 11/05/2015 07:05 PM, JuuS wrote: On 11/04/2015 12:30 PM, Mark Morgan Lloyd wrote: JuuS wrote: On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: When building the IDE you'd normally use make bigide or similar which would use the platform defaults, but depending on what

Re: [Lazarus] Using event driven components in console application

On 06/11/2015 11:25 πμ, Mark Morgan Lloyd wrote: JuuS wrote: On 11/05/2015 07:05 PM, JuuS wrote: On 11/04/2015 12:30 PM, Mark Morgan Lloyd wrote: JuuS wrote: On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: When building the IDE you'd normally use make bigide or similar which would use

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 12:30 PM, Mark Morgan Lloyd wrote: > JuuS wrote: >> On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: >>> When building the IDE you'd normally use make bigide or similar which >>> would use the platform defaults, but depending on what libraries etc. >>> were available you could

Re: [Lazarus] Using event driven components in console application

On 11/05/2015 07:05 PM, JuuS wrote: > > > On 11/04/2015 12:30 PM, Mark Morgan Lloyd wrote: >> JuuS wrote: >>> On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: When building the IDE you'd normally use make bigide or similar which would use the platform defaults, but depending on

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 12:45 PM, Mattias Gaertner wrote: I don't know what the two checkboxes mean that appear in front of IDE-Macro: LCLWidgetType:=nogui You can choose in which of your build modes the flag is enabled. Ah, now I see that a lot above there is a caption stating two build modes.

Re: [Lazarus] Using event driven components in console application

JuuS wrote: Excellent research, I see you've tracked this issue for a long time. Not so much that, but my colleagues and I have a fairly wide range of OS versions etc. and there are one or two programs that I really do want to run on just about anything (e.g. one that handles cut-and-paste

Re: [Lazarus] Using event driven components in console application

JuuS wrote: On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: When building the IDE you'd normally use make bigide or similar which would use the platform defaults, but depending on what libraries etc. were available you could also use e.g. make LCL_PLATFORM=qt bigide Hi, This question /

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 12:30 PM, Mark Morgan Lloyd wrote: > JuuS wrote: >> On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: >>> When building the IDE you'd normally use make bigide or similar which >>> would use the platform defaults, but depending on what libraries etc. >>> were available you could

Re: [Lazarus] Using event driven components in console application

On Wednesday 04 November 2015 14:31:34 JuuS wrote: > > But this is what, ultimately, fpGUI will address I believe? Wiki page > says it is still alpha but I anxiously await the opportunity to use it > natively (I work in 1.4.4, I SVN only occasionally in special > circumstances) > It is also

Re: [Lazarus] Using event driven components in console application

On 2015-11-04 16:45, Martin Schreiber wrote: > On Wednesday 04 November 2015 14:31:34 JuuS wrote: >> > >> > But this is what, ultimately, fpGUI will address I believe? Wiki page Interestingly it is now 16:52 local time, and I haven't seen that message from Juus in my Inbox. Umm... Are there

Re: [Lazarus] Using event driven components in console application

On 2015-11-04 17:03, Mark Morgan Lloyd wrote: > No, it's HMG filtering your email. Who've you upset? :-) Who knows. Looking at the mailing list archive, I haven't received any of JuuS's messages on this thread. At least messages from others have come through. And no, I don't have spam filtering

Re: [Lazarus] Using event driven components in console application

Graeme Geldenhuys wrote: On 2015-11-04 16:45, Martin Schreiber wrote: On Wednesday 04 November 2015 14:31:34 JuuS wrote: But this is what, ultimately, fpGUI will address I believe? Wiki page Interestingly it is now 16:52 local time, and I haven't seen that message from Juus in my Inbox.

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: Bo Berglund wrote: How do you change which "widgetset" is used? When building the IDE ... You don't need to rebuild the IDE to change the WidgetType (AKA "Interface") used in a project. It is a project option. In older Lazarus IDE versions

Re: [Lazarus] Using event driven components in console application

Bo Berglund wrote: On Tue, 3 Nov 2015 18:39:50 +0100, Mattias Gaertner wrote: you mean that Application.Processmessages is available in this console program? It is available when you use the NoGUI widgetset. How do you change which "widgetset" is used? (I really

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 10:09 AM, Michael Schnell wrote: "Project options" -> "Additions and Overrides" -> "Set LCLWidgetType". Sorry: "Project options" -> "Compiler Options" -> "Additions and Overrides" -> "Set LCLWidgetType". I don't know what the two checkboxes mean that appear in front of

Re: [Lazarus] Using event driven components in console application

On 11/03/2015 09:01 PM, Bo Berglund wrote: It is available when you use the NoGUI widgetset. How do you change which "widgetset" is used? In the IDE the Macro to be set is called "LCLWidgetType" (not "widgetset"). -Michael -- ___ Lazarus mailing

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 09:48 AM, Mark Morgan Lloyd wrote: > > When building the IDE you'd normally use make bigide or similar which > would use the platform defaults, but depending on what libraries etc. > were available you could also use e.g. make LCL_PLATFORM=qt bigide > Hi, This question /

Re: [Lazarus] Using event driven components in console application

On 11/04/2015 11:28 AM, JuuS wrote: Why would I want to use qt, gtk3, etc? Yes, of course for different platforms but which platforms (Fedora? Debian? ?? ). Lazarus takes a lot of care on portability. So a "normal" user project should run on any supported platform/OS/CPU architecture. Even

[Lazarus] Using event driven components in console application

I am moving a discussion that is being conducted in a thread named: "Lazarus implementation of TListview etc?" to this new thread since the topic has shifted away from the original This topic has to do with using communications components which fire off "OnReceive" events when data arrives

Re: [Lazarus] Using event driven components in console application

On Tue, 3 Nov 2015 14:55:54 +0100, Mattias Gaertner wrote: > >lnet does not use Post/SendMessage, so it works even with the NoGUI >widgetset. > >You can easily implement your own loop and simply call >Application.ProcessMessages. > Thanks, you mean that

Re: [Lazarus] Using event driven components in console application

On Tue, 03 Nov 2015 18:20:53 +0100 Bo Berglund wrote: > On Tue, 3 Nov 2015 14:55:54 +0100, Mattias Gaertner > wrote: > > > > >lnet does not use Post/SendMessage, so it works even with the NoGUI > >widgetset. > > > >You can easily implement your

Re: [Lazarus] Using event driven components in console application

On Tue, 3 Nov 2015 18:39:50 +0100, Mattias Gaertner wrote: >> you mean that Application.Processmessages is available in this console >> program? > >It is available when you use the NoGUI widgetset. How do you change which "widgetset" is used? (I really do not know what

Re: [Lazarus] Using event driven components in console application

On Tue, 03 Nov 2015 14:21:27 +0100 Bo Berglund wrote: >[...] > >Application.QueuAsyncCall() uses yet an additional Event Queue. Here > >using a WidgetType is not strictly necessary, but calling > >"CheckSynchronize() will not help, either. Here, TApplication provides >