Hallo Fred van Stappen,
vous ecrit au Fri, 10 Jun 2022 20:52:04 +0000:
> About MSEclock, I did this:
>
> Copy all the files of /MSEclock/newdialogs into root directory of
> project /MSEclock/.
>
> But when compiling with fpc 3.3.1. there are those errors:
>
> clockwork.pas(487,56) Error: Incompatible type for arg no. 2: Got
> "PointValues", expected "complexarty" clockwork.pas(489,58) Error:
> Incompatible type for arg no. 2: Got "PointValues", expected
> "complexarty" etc.
Ok, but these errors have no relation whatever to the "newdialogs"
units.
> So I added in top of clockwork.pas: {$modeswitch arraytodynarray}
> and then it compiles OK.
Did you compile with fpc 3.3.1? Their now stricter type checking could
have caused this. I'm still using 3.2.2, because I also work on a
customer project, and I'm reluctant to do this using tools that are
not yet released.
But for fpc 3.3.1, a "PointValues" type (FIXED array type) will not be
acceptable in place of a "complexarty" (why's that, BTW? There's
nothing complex in here? Funny idea that...)
> I have also to comment the first line of procedure
> tclockworkfo.Zeitstart()
"Hide;"? How's that? Anyway, the form is set to "visible:= false;"
anyway, so this shouldn't cause trouble, but why on earth should an
additional "hide" cause a problem?
> procedure tclockworkfo.Zeitstart (const Sender: TObject);
> begin
> // Hide; //comment this
> Otherwise I get a error at run : "Form not decorated".
Interesting... The "not decorated" error showed up here too, but it was
NOT caused because of a superfluos "hide", but rather by the language
dialog when it was closed. This might need some research, as it looks
like there is something done that interferes with the window manager.
> Doing this the application runs.
Fine that it does work with the development branch of fpc (3.3.1) now
also. I should probabely adjust it accordingly and repackage it to
avoid problems later on, when fpc 3.3.? becomes official.
BTW, I downloaded the video about Martin and his work (english version)
you mentioned lately. Very interesting, he was a very undertaking guy,
even leading his own company and doing a lot of consulting work.
(BTW, the speaker displays a very special pronunciation of "msegui",
sounding somewhat like "em-segway" - I always had the impression that
this should rather be pronounced like "em-se gooey", as I often found
the term "gooey" as a misunderstood pronunciation of the abbreviation
"GUI".)
I always wonder how the authors of such stuff get at all the
information they use to present - following the mailing lists and
news groups his work was discussed on, one never got anywhere near
so rich a picture about his person.
(And as an aside, I was surprised to see most of the parts of the
"gallery" entry that I put together around mid-2008 as an example
project for msegui, of an old project of mine, one I'm again working
on now.)
--
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
-----------------------------------------------------------
Mit freundlichen Grüßen, S. Schicktanz
-----------------------------------------------------------
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
