Hello.
I did try using aligntoqword() but without luck, I only get crash at
loading.
It is very sad but I dont have the skill to fix this and mse depends of a
guru with brave heart to make it compatible with fpc 3.3.1.
Anyway, many thanks Martin for your light.
Fre;D
-
Many thanks ;-)
Hello Martin.
Wow.
Indeed, I did a check in mse code and only exists, in msearrayutils.pas:
function aligntoptr(p: pointer): pointer; inline;
begin
{$ifdef FPC_REQUIRES_PROPER_ALIGNMENT}
result:= align(p,sizeof(p));
{$else FPC_REQUIRES_PROPER_ALIGNMENT}
result:=p;
{$endif
On 02/02/2020 04:22, fredvs via fpc-pascal wrote:
Hello everybody.
Good time to go back with that problem and fix it forever the right way!
The problem is isolated and is fixed "hardcoded".
From rev 42375, in msegui function dynarrayelesize(const typinfo:
pdynarraytypeinfo): sizeint; inline;
Hello everybody.
Good time to go back with that problem and fix it forever the right way!
The problem is isolated and is fixed "hardcoded".
From rev 42375, in msegui function dynarrayelesize(const typinfo:
pdynarraytypeinfo): sizeint; inline;
the result is always = 0.
This function is used in
Oops, sorry, fake news.
It was my mistake, I did compile with fpc 3.0.4.
So, no, with last commits, it does not fix the problems.
Fre;D
-
Many thanks ;-)
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
___
fpc-pascal maillist
Hello.
Great news!
With last fpc commits, msegui is fpc compatible again!
(And I am very curious what was the problem, if you can explain what you did
it would be super.)
Anyway, perfect and many thanks.
Fre;D
-
Many thanks ;-)
--
Sent from:
Hello Sven.
> I can't see any difference in that procedure to the one in Classes.TReader
> except for the ifdefs and a few extensions for events and UTF-8 strings,
> so the problem must be somewhere else.
Ha, we are going forward. so maybe TReader is not the problem.
Ok, I will try to
fredvs schrieb am Fr., 6. Sep. 2019, 22:23:
> Hello everybody (included Sven).
>
> It seems that the problems come from
> /mseide-msegui/lib/common/fpccompatibility/mclasses.pas.
>
> In procedure TReader.ReadPropValue(Instance: TPersistent; PropInfo:
> Pointer), IMHO there is something not
fredvs schrieb am Mi., 9. Okt. 2019, 12:00:
> Could it be possible to simplify the life of rtl-users and add methods with
> same parameters as previous version and make it compatible with new
> features?
>
Working with the RTTI simply is *not* simple, because you're interfacing
with binary data
Hello everybody.
Sorry to come back with this but I am lost (and all my stock of Aspirina is
dead).
Could it be possible to simplify the life of rtl-users and add methods with
same parameters as previous version and make it compatible with new
features?
Other wishes:
It seems that the updates
Hello everybody (included Sven).
It seems that the problems come from
/mseide-msegui/lib/common/fpccompatibility/mclasses.pas.
In procedure TReader.ReadPropValue(Instance: TPersistent; PropInfo:
Pointer), IMHO there is something not compatible with rev 42375.
It would be wonderful if somebody
> sounds like you need a copy of the files before and after so you can easily
diff them and see where the difference is...
Are you talking about the .sta file?
Good, idea, I will see if it is different at saving.
But I have doubt because using a fpc < rev 42375 all is ok, even after
saving the
On 8/31/19 11:15 AM, fredvs wrote:
And rev 42375 was the guilty, before that rev, all is working ok.
Do you get a compile error, or do the files no longer read/write properly
?
No, no compile error, it is only he files no longer read/write properly.
sounds like you need a copy of the
fredvs schrieb am Sa., 31. Aug. 2019, 22:00:
> Hello Sven.
>
> > Just look at the changes: ...
>
> OK, but before I have to check my stock of aspirin.
> I think I'm going to need a lot this time.
>
> Many thanks Sven to help me in that complete darkness.
>
Alternatively try alcohol. ;)
And I
Hello Sven.
> Just look at the changes: ...
OK, but before I have to check my stock of aspirin.
I think I'm going to need a lot this time.
Many thanks Sven to help me in that complete darkness.
Fre;D
-
Many thanks ;-)
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
Am 31.08.2019 um 18:24 schrieb fredvs:
Hello.
Type information contains reference to attribute table
Old behavior: The first field of the data represented by TTypeData is
whatever the sub branch
of the case statement for the type contains.
New behavior: The first field of the data represented
Hello.
> Type information contains reference to attribute table
> Old behavior: The first field of the data represented by TTypeData is
> whatever the sub branch
> of the case statement for the type contains.
> New behavior: The first field of the data represented by TTypeData is a
> reference to
Hello Sven.
> I assume your code in msegui directly accesses the RTTI instead of using
> the types provided by the TypInfo unit.
IMHO, after check, it seems that msegui uses the types provided by the
TypInfo unit.
In each "uses" section of a msegui unit was added "typinfo".
So maybe it should
Hello Sven.
> I assume your code in msegui directly accesses the RTTI instead of using
> the types provided by the TypInfo unit.
Ha, ok, I will jump into mse + TypInfo and see what it says.
Thanks.
Fre;D
-
Many thanks ;-)
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
Am 31.08.2019 um 14:31 schrieb fredvs:
Hello everybody and specially Sven Barth.
With last trunk of fpc, msegui is no more compatible with fpc.
After big fight, it appears that commit of Sven Barth on Jul 13 2019, rev
42375 breaks compatibility --->
"as attributes can be part of any type they
> Yes, but that does not tell me why a change in RTTI info would stop this
from working.
Same for me, I absolutely dont understand why a change in RTTI info would
stop this from working.
It is why I did the "explorer" way to debug the problem: doing regression
from last fpc trunk until a revision
On Sat, 31 Aug 2019, fredvs wrote:
What is a sta file ?
"sta" file is a stat-like file that contains some infos about msegui widget
behavior (and much more if you want).
For example you may use mse-sta file as ini (or json) file, used to store
parameters of layout of forms of your mse
> What is a sta file ?
"sta" file is a stat-like file that contains some infos about msegui widget
behavior (and much more if you want).
For example you may use mse-sta file as ini (or json) file, used to store
parameters of layout of forms of your mse application.
You may use also mse-sta files
On Sat, 31 Aug 2019, fredvs wrote:
Hello Michael.
Can you be more precise ?
I would like!
It appends when reading mse sta files.
with that types:
tstatreader = class;
tstatwriter = class;
With rev 42375, some sections of the sta-file are no more recognized, like
"layout" section.
What
Hello Michael.
> Can you be more precise ?
I would like!
It appends when reading mse sta files.
with that types:
tstatreader = class;
tstatwriter = class;
With rev 42375, some sections of the sta-file are no more recognized, like
"layout" section.
I have to confess that I am in the dark
On Sat, 31 Aug 2019, fredvs wrote:
Hello everybody and specially Sven Barth.
With last trunk of fpc, msegui is no more compatible with fpc.
After big fight, it appears that commit of Sven Barth on Jul 13 2019, rev
42375 breaks compatibility --->
"as attributes can be part of any type they
26 matches
Mail list logo
