Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[fredvs]

Hello Roland, hello Code DZ.

> where is the repository that contain the fix ? 

https://github.com/mse-org/mseide-msegui

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[code dz]

thanks fred for the effort .
where is the repository that contain the fix ?


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[fredvs]

Hello everybody.

OK, I think it is ok now.
You may compile mseide with fpc >= 3.1.0.
The "live- parameters-matcher" is working too.

I did test with trunk fpc 3.3.1.

All the fixes are in last commit 44f515f.

Test and comment about the commit are welcome.

Fre;D





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[Roland Chastain]

Hello Fred!

 

Unfortunately I have no idea of the problem and no time to put my head into it. So I have no opinion.

 

Thank you for your efforts around MSEide.

 

Best regards.

 

Roland


Envoyé: jeudi 25 juillet 2019 à 15:29
De: "fredvs" 
À: mseide-msegui-talk@lists.sourceforge.net
Objet: Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

Hello everybody.

Sadly, the attempt to use fpc forum did not give lot of success:

http://free-pascal-general.1045716.n5.nabble.com/TParamFlags-and-fpc-3-2-0-td5733871.html

So finally, after a big fight, I did find a workaround.
Now, if you create a method via the mse-designer the correct parameters will
be used with fpc 3.2.0, like in the video here:



But there is a bemol.

In mse code, after creating a new method via the mse-designer, there is a
check with:

function parametersmatch(const a: ptypeinfo; const b: methodparaminfoty):
boolean;

With the workaround that I use, this parametersmatch is set to always to
true if using fpc 3.2.0.

So, if you change manually the parameters used by the method created by the
mse-designer, (and use bad parameters) there will be a error message only at
compilation, not directly like when using fpc 3.0.4.

So the question is: should I commit the changes to make mseide work when
compiled with fpc 3.0.4. (but without live- parameters-matcher).

I did many test and did not find any problems.

Or do you think it is better to wait that a TParamFlags guru appears ?

Thanks.

Fre;D





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[fredvs]

Ooops, in previous mail, please read (---> fpc 3.2.0, not fpc 3.0.4) :

> So the question is: should I commit the changes to make mseide work when 
> compiled with fpc *3.2.0* ? (but without live- parameters-matcher).

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

[fredvs]

Hello everybody.

Sadly, the attempt to use fpc forum did not give lot of success:

http://free-pascal-general.1045716.n5.nabble.com/TParamFlags-and-fpc-3-2-0-td5733871.html

So finally, after a big fight, I did find a workaround.
Now, if you create a method via the mse-designer the correct parameters will
be used with fpc 3.2.0, like in the video here:


   

But there is a bemol.

In mse code, after creating a new method via the mse-designer, there is a
check with:

function parametersmatch(const a: ptypeinfo; const b: methodparaminfoty):
boolean;

With the workaround that I use, this parametersmatch is set to always to
true if using fpc 3.2.0.

So, if you change manually the parameters used by the method created by the
mse-designer, (and use bad parameters) there will be a error message only at
compilation, not directly like when using fpc 3.0.4.

So the question is: should I commit the changes to make mseide work when
compiled with fpc 3.0.4. (but without live- parameters-matcher).

I did many test and did not find any problems.

Or do you think it is better to wait that a TParamFlags guru appears ?

Thanks.

Fre;D





--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk