Re-hello Graeme.
I seems that there is a problem with pfSelf parameter and last fpc 3.2.0, it
is always set to true.
Using flags:= [] shows always self-parameter.
And using flags:= [pfSelf] or no has no difference, it is always pfSelf on
(and so first parameter added).
I did test all other
> So I would expect we simply need to add an extra check
> during that iteration and discard all pfHidden and pfSelf parameters
Yes, it is the fix.
(But I maintain that if fpc did find a way to not show those new pfHidden
and pfSelf parameters as default, it would be great too).
Thanks Graeme.
--
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
Hi Fred,
On 27/04/2019 13:08, fredvs wrote:
> In last fpc 3.2.0. was added a "hidden" parameter for TParamFlags (to do
> like Java does?).
> OK but why add this new parameter as default, why not add it with a no
> default parameter to keep compatibly with earlier version?
I do agree that FPC's
> I'll take a look at the MSEide code.
IMHO, the problems and the fixes can be found in msedesigner.pas and
msedesignparser.
IMHO bis, it is great that fpc add new features in each new version but it
would be even better if those new features are backward compatible.
In last fpc 3.2.0. was
On 26/04/2019 22:40, fredvs wrote:
> The only problems found are with mseide himself and the new behavior of
> TParamFlags.
> But it seems, after lot of search, that, in all fpc world, only Martin did
> know how to use TParamFlags.
>
6 matches
Mail list logo
