Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Mattias Gaertner via lazarus

On 28.07.23 16:35, Michael Van Canneyt via lazarus wrote:

[...]
Naming something Unicode without adding any new Unicode feature can 
hardly be called consistent.


As I wrote, the "Unicode" refers to String = UnicodeString. In that 
sense it is 'consistent with existent terminology'


Yes, but you didn't name it "UnicodeString RTL", you named it "Unicode 
RTL". You can't blame CodeGear for that choice.


The new RTL has dotted units, so "Namespaced RTL" or "Dotted RTL" would 
fit too - also no catchy.




So far, nothing catchy has been offered.


If you want something catchy, don't use a descriptive name.

Since the cheetah is a dotted (spotted) animal and it is the fpc mascot, 
maybe Cheetah RTL?



Mattias



--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread DougC via lazarus
I like WideChar RTL over Unicode RTL!!-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Werner Pamler via lazarus

Am 28.07.2023 um 11:37 schrieb Michael Van Canneyt via lazarus:

I updated my lazarus today, and the following fails:

procedure TLazCanvas.Polygon(const Points: array of TPoint; Winding: 
Boolean);

begin
  PolygonNonZeroWindingRule := Winding;
  inherited Polygon(Points);
end;

it does not know PolygonNonZeroWindingRule.

I removed that line, and all compiles, but I suppose this is not the 
correct

fix ?
Last time there was a complaint about this I checked all combinations I 
have access to, and it was working. You are talking of Laz/main? In 
combination with which FPC? And on which OS? Did you try a *clean 
*rebuild of the Lazarus IDE?-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Alexey Torgashin via lazarus




Objection duly noted.


Yes, 'Unicode RTL' sounds very bad. Before it was Unicode too. So, 
"UTF16 RTL", "WideChar RTL" or so.


Alex
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Michael Van Canneyt via lazarus




On Fri, 28 Jul 2023, Alexey Torgashin via lazarus wrote:




Objection duly noted.


Yes, 'Unicode RTL' sounds very bad. Before it was Unicode too. So, "UTF16 
RTL", "WideChar RTL" or so.


The "Unicode" refers to String = UnicodeString.

The latter has been in use for what, 15-20 years ?

The name is chosen to remain consistent with existing terminology.

Assuming you guys are consistent, I guess you people are also not 
comfortable with the term 'UnicodeString' ?


Working with FPC must be a really annoying experience then...

Michael.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Michael Van Canneyt via lazarus




On Fri, 28 Jul 2023, Adriaan van Os via fpc-devel wrote:


Michael Van Canneyt via fpc-devel wrote:


Hello,

I have just completed phase one of the "Unicode RTL" effort.


I object to the name "Unicode" RTL. Where people talk about what they call 
"Unicode" they usually mean UCS-16 or UTF-16 or UTF-16-mishandled-as-UCS16.


Objection duly noted.

Michael.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


[Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Michael Van Canneyt via lazarus



Hi,

I updated my lazarus today, and the following fails:

procedure TLazCanvas.Polygon(const Points: array of TPoint; Winding: Boolean);
begin
  PolygonNonZeroWindingRule := Winding;
  inherited Polygon(Points);
end;

it does not know PolygonNonZeroWindingRule.

I removed that line, and all compiles, but I suppose this is not the correct
fix ?

Michael.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] MJPEG streamer

2023-07-28 Thread Ondrej Pokorny via lazarus

On 28.07.2023 03:40, Steve Gatenby via lazarus wrote:


On 24/7/23 09:35, Steve Gatenby via lazarus wrote:


On 23/7/23 18:35, Steve Gatenby via lazarus wrote:
Would anybody know if there is a component / code to enable reading 
an mjpeg stream from a http camera to a Lazarus form/panel (or 
anything really)


Dont mind installing libraries etc -

Looking to suit Linux specifically though

Thanks - SteveG



Thank you all -

exactly what I was hoping for - possibilities to follow :)

I will post if / once I get it figured as may be useful to others


I have written a (very) small unit to capture stream from esp32-cam 
(currently) and display in standard Lazarus TImage. First draft allows 
multiple cams / images.


What is the accepted way of supplying for use by others ? - do we have 
a central place for snippets / units for Pascal / Lazarus.


I know about CCR etc, but this is a bit small for that :) - so not 
sure what to do with it.


Have considered github, but seems overkill for such a small offering 
(and no guarantees it would always exist)


I am interested in your solution.

If the unit uses the Lazarus-included lazvlc.lpk (or any other solution 
included in FPC/Lazarus), I would store it in the examples folder within 
Lazarus main: 
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/main/examples


Please either create an issue in Lazarus gitlab and send the code there 
or send me the example as zipped file and I will upload it to examples.


Thanks,
Ondrej

--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] MJPEG streamer

2023-07-28 Thread Ondrej Pokorny via lazarus
Just to make sure: do you show a real-time video stream in TImage or do 
you just extract a single frame from the camera one by one?


Ondrej

--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Werner Pamler via lazarus

Am 28.07.2023 um 15:10 schrieb Michael Van Canneyt via lazarus:
It is Laz/Main (updated today), FPC 3.2.2 and clean rebuild (I have 
the option 'clean always' set in the lazarus build config).

This is my standard development system. No problem with it.


Where is this PolygonNonZeroWindingRule supposed to be defined ?


For some time this was an addition to TLazCanvas.Polygon in Laz/2.3 and 
it had a different name which I cannot remember. Then I sent a patch for 
Polygon fill routines for TFpPixelCanvas which introduced the 
PolygonNonZeroWindingRule to FP/main (you committed it, 
https://gitlab.com/freepascal.org/fpc/source/-/issues/40286). I reworked 
TLazCanvas and removed the no-longer needed, old polygon fill of 
TLazCanvas in case of too-old FPC. So, there may be some combinations in 
the history of the Laz and FPC projects where there is a conflict, but 
there is definitely no conflict within Laz/main/fixes and 
FPC/main/fixes/3.2.2


--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Michael Van Canneyt via lazarus




On Fri, 28 Jul 2023, Mattias Gaertner via lazarus wrote:


On 28.07.23 13:42, Michael Van Canneyt via lazarus wrote:



On Fri, 28 Jul 2023, Alexey Torgashin via lazarus wrote:




Objection duly noted.


Yes, 'Unicode RTL' sounds very bad. Before it was Unicode too. So, "UTF16 
RTL", "WideChar RTL" or so.


The "Unicode" refers to String = UnicodeString.

The latter has been in use for what, 15-20 years ?


...wrong for 20 years.




The name is chosen to remain consistent with existing terminology.


It seems, it was chosen because it is easier to pronounce than UTF16 RTL.


No, see below (or above).



Naming something Unicode without adding any new Unicode feature can hardly be 
called consistent.


As I wrote, the "Unicode" refers to String = UnicodeString. 
In that sense it is 'consistent with existent terminology'


That the original terminology "unicodestring" is badly chosen,
see first line in the feature list:

https://delphi.embarcadero.com/project/delphi-2009/

So complaints to CodeGear, please.

But if all these terribly unhappy and depressed users have a better name, I'm 
all ears.

So far, nothing catchy has been offered.

We'll attribute this lack of creativity to the state of depression due to
having to use such awful and horrifying terminology for ~15 years ;-)

Michael.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Luca Olivetti via lazarus

El 28/7/23 a les 16:35, Michael Van Canneyt via lazarus ha escrit:
But if all these terribly unhappy and depressed users have a better 
name, I'm all ears.


So far, nothing catchy has been offered.


What about "Futura RTL"?
Short, catchy and...completely meaningless in this context :-D

Great song, though
https://www.youtube.com/watch?v=RXjE4q3Hyd4

Bye
--
Luca Olivetti
Wetron Automation Technology https://wetron.es/
Tel. +34 93 5883004 (Ext.3010)  Fax +34 93 5883007

--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Michael Van Canneyt via lazarus



On Fri, 28 Jul 2023, Werner Pamler via lazarus wrote:


Am 28.07.2023 um 11:37 schrieb Michael Van Canneyt via lazarus:

I updated my lazarus today, and the following fails:

procedure TLazCanvas.Polygon(const Points: array of TPoint; Winding: 
Boolean);

begin
  PolygonNonZeroWindingRule := Winding;
  inherited Polygon(Points);
end;

it does not know PolygonNonZeroWindingRule.

I removed that line, and all compiles, but I suppose this is not the 
correct

fix ?
Last time there was a complaint about this I checked all combinations I have 
access to, and it was working. You are talking of Laz/main? In combination 
with which FPC? And on which OS? Did you try a *clean *rebuild of the Lazarus 
IDE?


It is Laz/Main (updated today), FPC 3.2.2 and clean rebuild 
(I have the option 'clean always' set in the lazarus build config).


Where is this PolygonNonZeroWindingRule supposed to be defined ?

Michael.-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Maxim Ganetsky via lazarus

28.07.2023 16:10, Michael Van Canneyt via lazarus пишет:



On Fri, 28 Jul 2023, Werner Pamler via lazarus wrote:


Am 28.07.2023 um 11:37 schrieb Michael Van Canneyt via lazarus:

I updated my lazarus today, and the following fails:

procedure TLazCanvas.Polygon(const Points: array of TPoint; Winding: 
Boolean);

begin
  PolygonNonZeroWindingRule := Winding;
  inherited Polygon(Points);
end;

it does not know PolygonNonZeroWindingRule.

I removed that line, and all compiles, but I suppose this is not the 
correct

fix ?
Last time there was a complaint about this I checked all combinations 
I have access to, and it was working. You are talking of Laz/main? In 
combination with which FPC? And on which OS? Did you try a *clean 
*rebuild of the Lazarus IDE?


It is Laz/Main (updated today), FPC 3.2.2 and clean rebuild (I have 
the option 'clean always' set in the lazarus build config).


Lazarus can be built with FPC 3.2.2 just fine. Our CI ensures this (and 
it does exactly clean builds which include TLazCanvas too).


Judging from your description, it looks like you use by accident some 
outdated revision of FPC 3.2.3 or 3.3.1.



Where is this PolygonNonZeroWindingRule supposed to be defined ?


--
Best regards,
 Maxim Ganetsky  mailto:gan...@narod.ru

--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Compilation failed : PolygonNonZeroWindingRule unknown

2023-07-28 Thread Michael Van Canneyt via lazarus



On Fri, 28 Jul 2023, Maxim Ganetsky via lazarus wrote:


28.07.2023 16:10, Michael Van Canneyt via lazarus пишет:



On Fri, 28 Jul 2023, Werner Pamler via lazarus wrote:


Am 28.07.2023 um 11:37 schrieb Michael Van Canneyt via lazarus:

I updated my lazarus today, and the following fails:

procedure TLazCanvas.Polygon(const Points: array of TPoint; Winding: 
Boolean);

begin
  PolygonNonZeroWindingRule := Winding;
  inherited Polygon(Points);
end;

it does not know PolygonNonZeroWindingRule.

I removed that line, and all compiles, but I suppose this is not the 
correct

fix ?
Last time there was a complaint about this I checked all combinations 
I have access to, and it was working. You are talking of Laz/main? In 
combination with which FPC? And on which OS? Did you try a *clean 
*rebuild of the Lazarus IDE?


It is Laz/Main (updated today), FPC 3.2.2 and clean rebuild (I have 
the option 'clean always' set in the lazarus build config).


Lazarus can be built with FPC 3.2.2 just fine. Our CI ensures this (and 
it does exactly clean builds which include TLazCanvas too).


That is why I was so surprised to see the failure...

After some searching, it seems I was using a fixes compiler and didn't
notice. Seems my mind wanted to read 3.2.2 instead of the actual 3.2.3 :/

Apologies for the noise.

Michael.-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Unicode RTL

2023-07-28 Thread Mattias Gaertner via lazarus

On 28.07.23 13:42, Michael Van Canneyt via lazarus wrote:



On Fri, 28 Jul 2023, Alexey Torgashin via lazarus wrote:




Objection duly noted.


Yes, 'Unicode RTL' sounds very bad. Before it was Unicode too. So, 
"UTF16 RTL", "WideChar RTL" or so.


The "Unicode" refers to String = UnicodeString.

The latter has been in use for what, 15-20 years ?


...wrong for 20 years.




The name is chosen to remain consistent with existing terminology.


It seems, it was chosen because it is easier to pronounce than UTF16 RTL.

Naming something Unicode without adding any new Unicode feature can 
hardly be called consistent.





Assuming you guys are consistent, I guess you people are also not 
comfortable with the term 'UnicodeString' ?


Of course not.




Working with FPC must be a really annoying experience then... 


;)


Mattias


--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus