Re: [MSEide-MSEgui-talk] New release?

2023-06-12 Thread Fred van Stappen
Re-hello Vasi.

And the icing on the cake: the binary of mseide for NetBSD.

https://github.com/mse-org/mseide-msegui/files/11727396/mseide_netbsd.tar.gz

NetBSD was kind, he allowed me to upload files!




Have fun!

Fre;D


De : vasi vasi 
Envoyé : lundi 12 juin 2023 17:36
À : General list for MSEide+MSEgui 
Objet : Re: [MSEide-MSEgui-talk] New release?

NetBSD is in full transition to clang but it cannot give up on gcc also, so, 
there are two different linkers with different configurations and expectations. 
With resulted programs that cannot find their shared libs so is a total mess... 
Hopefully, NetBSD 10 will ease things... But not only the BSD world, Linux 
also... there are efforts towards clang...

Until then, even for C programs there are problems... Because I don't know 
other way, I had to copy-symlink all libraries from X11R7 to /usr/lib, not only 
six of them (thanks for the pointer)... I'm pretty sure there is a right way to 
do it?  A manual or something (it wasn't this mess a few years back...)

For example for lockf () function, (if I remember correctly, because I am now 
on the linux laptop) you get errors and if you look at the man manual, things 
are like in linux, but it ends up that you really must change the value of one 
parameter the way compiler suggest it... In the end, raylib 4.0 compiles and 
runs ok but the timing is wrong because of incompatibilities with the timer 
functions that are yet to be solved... A nice graphical library that we have a 
pascal translation for. At least, in OpenBSD didn't worked at all (mouse 
problems in glfw library)...  We really need some pointers from the developers 
and the porting team... Typhoon Relational Database needed also some 
interventions... Because, asking users to do what we do is a no-no... But at 
least, things are working...

Otherwise, NetBSD snappier for me than OpenBSD... Your pointers were helpful. I 
had an X11 freeze trying mseide but I switched to the console and killed the 
X... No system crash, and I activated the journaling for the file system, just 
to be sure is recoverable... It works better than in OpenBSD...

So, it seems that NetBSD requires the most work from the three of them... but I 
expect dflyBSD to be as easier as FreeBSD (if we make mouse and keyboard to 
work on X)...

On Mon, Jun 12, 2023 at 6:18 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Excellent progress!
I also lost the night configuring NetBSD, setting the firewall, installing 
apps... now is up and running, just to make those X11 symlinks. Also having 
some difficulties in compiling a C library, but not mseide related...

On Mon, Jun 12, 2023 at 12:22 AM Fred van Stappen 
mailto:fi...@hotmail.com>> wrote:
Allez, the very last for tonight.

I found the guilty of the icons and images not show and the error message of 
corrupt X11 atom.
It is the image property bmo_graymask.
And in all the mseide project all images or images list have "bmo_graymask = 
true".
When setting bmo_graymask := false for all image and image-list the icon and 
image are ok.

 
https://github.com/mse-org/mseide-msegui/assets/3421249/3452e988-1504-44df-a9e9-84ecdf65806a

By the way, I never understood that property "bmo_graymask", setting it to true 
or false dont change anything on other os.

It is a excellent news because fighting with X11 is a other story.

So, perfect, the icons and images problems are solved.
I will clean all the code, set bmo_graymask := false for eveybody and do the 
commit tonight.

Only remains the access to directory in file dialog that resists.
But not for longtime (but not for tonight).

Fre;D


De : Fred van Stappen mailto:fi...@hotmail.com>>
Envoyé : dimanche 11 juin 2023 21:06
À : General list for MSEide+MSEgui 
mailto:mseide-msegui-talk@lists.sourceforge.net>>
Objet : Re: [MSEide-MSEgui-talk] New release?

Ooops, in previous post, the screenshot was without the run, here the good one.
In the terminal, no more cry of X11 for bad atom.

https://github.com/mse-org/mseide-msegui/assets/3421249/73bae81e-f28c-4790-b26c-5f408a9a2975

Note too that file access via the file-dialog is not yet perfect, for creating 
the project I have to write the full path + name, playing with the 
directory-icons was not ok.

So, to resume, still some work but it will be possible to terminate the combat.

Fre;D

De : Fred van Stappen mailto:fi...@hotmail.com>>
Envoyé : dimanche 11 juin 2023 20:53
À : General list for MSEide+MSEgui 
mailto:mseide-msegui-talk@lists.sourceforge.net>>
Objet : Re: [MSEide-MSEgui-talk] New release?

OK, I created a new project directly in NetBSD using mseide-pre-alpha, with a 
button and a image on his face.
Compiled and run.
And there the button has his ico-image:
https://github.com/mse-org/mseide-msegui/assets/3421249/ec05ff42-2058-4c2f-9c39-746d9ac4d462
And no more cry when passing with mouse on the button about invalid atom.

Hum, hum, 

Re: [MSEide-MSEgui-talk] New release?

2023-06-12 Thread Fred van Stappen
Re-hello Vasi.

Note that you need to run the application via console, strangely if you 2Xclick 
on the binary, the application run then freeze.
I did try for other binaries (not fpc binaries) and it is the same.
Maybe a protection feature (or a bug).

Fre;D



De : Fred van Stappen 
Envoyé : lundi 12 juin 2023 19:57
À : General list for MSEide+MSEgui 
Objet : Re: [MSEide-MSEgui-talk] New release?

Hello Vasi.

Yep, I finally managed to tame the directory access.
Now, with last commit, all (should) works perfectly, included mseide, no more 
perpetual loop at run, nor crash and file-dialogs are working ok.

NetBSD was not easy to tame, mainly because of missing or wrong doc.
For example, https://man.netbsd.org/dirent.3
The declaration of

 uint16_td_namlen;


is wrong, it should be uint8_t and make the things not work, changing to uint8 
fix it.

Also there is a bug with readdir_r(), sometime it never reach to the end of the 
directory and does a perpetual loop.

I use now readdir(), this one is ok.

It was a hard battle but we win.

Cheers.

Fre;D


De : vasi vasi 
Envoyé : lundi 12 juin 2023 17:36
À : General list for MSEide+MSEgui 
Objet : Re: [MSEide-MSEgui-talk] New release?

NetBSD is in full transition to clang but it cannot give up on gcc also, so, 
there are two different linkers with different configurations and expectations. 
With resulted programs that cannot find their shared libs so is a total mess... 
Hopefully, NetBSD 10 will ease things... But not only the BSD world, Linux 
also... there are efforts towards clang...

Until then, even for C programs there are problems... Because I don't know 
other way, I had to copy-symlink all libraries from X11R7 to /usr/lib, not only 
six of them (thanks for the pointer)... I'm pretty sure there is a right way to 
do it?  A manual or something (it wasn't this mess a few years back...)

For example for lockf () function, (if I remember correctly, because I am now 
on the linux laptop) you get errors and if you look at the man manual, things 
are like in linux, but it ends up that you really must change the value of one 
parameter the way compiler suggest it... In the end, raylib 4.0 compiles and 
runs ok but the timing is wrong because of incompatibilities with the timer 
functions that are yet to be solved... A nice graphical library that we have a 
pascal translation for. At least, in OpenBSD didn't worked at all (mouse 
problems in glfw library)...  We really need some pointers from the developers 
and the porting team... Typhoon Relational Database needed also some 
interventions... Because, asking users to do what we do is a no-no... But at 
least, things are working...

Otherwise, NetBSD snappier for me than OpenBSD... Your pointers were helpful. I 
had an X11 freeze trying mseide but I switched to the console and killed the 
X... No system crash, and I activated the journaling for the file system, just 
to be sure is recoverable... It works better than in OpenBSD...

So, it seems that NetBSD requires the most work from the three of them... but I 
expect dflyBSD to be as easier as FreeBSD (if we make mouse and keyboard to 
work on X)...

On Mon, Jun 12, 2023 at 6:18 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Excellent progress!
I also lost the night configuring NetBSD, setting the firewall, installing 
apps... now is up and running, just to make those X11 symlinks. Also having 
some difficulties in compiling a C library, but not mseide related...

On Mon, Jun 12, 2023 at 12:22 AM Fred van Stappen 
mailto:fi...@hotmail.com>> wrote:
Allez, the very last for tonight.

I found the guilty of the icons and images not show and the error message of 
corrupt X11 atom.
It is the image property bmo_graymask.
And in all the mseide project all images or images list have "bmo_graymask = 
true".
When setting bmo_graymask := false for all image and image-list the icon and 
image are ok.

 
https://github.com/mse-org/mseide-msegui/assets/3421249/3452e988-1504-44df-a9e9-84ecdf65806a

By the way, I never understood that property "bmo_graymask", setting it to true 
or false dont change anything on other os.

It is a excellent news because fighting with X11 is a other story.

So, perfect, the icons and images problems are solved.
I will clean all the code, set bmo_graymask := false for eveybody and do the 
commit tonight.

Only remains the access to directory in file dialog that resists.
But not for longtime (but not for tonight).

Fre;D


De : Fred van Stappen mailto:fi...@hotmail.com>>
Envoyé : dimanche 11 juin 2023 21:06
À : General list for MSEide+MSEgui 
mailto:mseide-msegui-talk@lists.sourceforge.net>>
Objet : Re: [MSEide-MSEgui-talk] New release?

Ooops, in previous post, the screenshot was without the run, here the good one.
In the terminal, no more cry of X11 for bad atom.


Re: [MSEide-MSEgui-talk] New release?

2023-06-12 Thread Fred van Stappen
Hello Vasi.

Yep, I finally managed to tame the directory access.
Now, with last commit, all (should) works perfectly, included mseide, no more 
perpetual loop at run, nor crash and file-dialogs are working ok.

NetBSD was not easy to tame, mainly because of missing or wrong doc.
For example, https://man.netbsd.org/dirent.3
The declaration of

 uint16_td_namlen;


is wrong, it should be uint8_t and make the things not work, changing to uint8 
fix it.

Also there is a bug with readdir_r(), sometime it never reach to the end of the 
directory and does a perpetual loop.

I use now readdir(), this one is ok.

It was a hard battle but we win.

Cheers.

Fre;D


De : vasi vasi 
Envoyé : lundi 12 juin 2023 17:36
À : General list for MSEide+MSEgui 
Objet : Re: [MSEide-MSEgui-talk] New release?

NetBSD is in full transition to clang but it cannot give up on gcc also, so, 
there are two different linkers with different configurations and expectations. 
With resulted programs that cannot find their shared libs so is a total mess... 
Hopefully, NetBSD 10 will ease things... But not only the BSD world, Linux 
also... there are efforts towards clang...

Until then, even for C programs there are problems... Because I don't know 
other way, I had to copy-symlink all libraries from X11R7 to /usr/lib, not only 
six of them (thanks for the pointer)... I'm pretty sure there is a right way to 
do it?  A manual or something (it wasn't this mess a few years back...)

For example for lockf () function, (if I remember correctly, because I am now 
on the linux laptop) you get errors and if you look at the man manual, things 
are like in linux, but it ends up that you really must change the value of one 
parameter the way compiler suggest it... In the end, raylib 4.0 compiles and 
runs ok but the timing is wrong because of incompatibilities with the timer 
functions that are yet to be solved... A nice graphical library that we have a 
pascal translation for. At least, in OpenBSD didn't worked at all (mouse 
problems in glfw library)...  We really need some pointers from the developers 
and the porting team... Typhoon Relational Database needed also some 
interventions... Because, asking users to do what we do is a no-no... But at 
least, things are working...

Otherwise, NetBSD snappier for me than OpenBSD... Your pointers were helpful. I 
had an X11 freeze trying mseide but I switched to the console and killed the 
X... No system crash, and I activated the journaling for the file system, just 
to be sure is recoverable... It works better than in OpenBSD...

So, it seems that NetBSD requires the most work from the three of them... but I 
expect dflyBSD to be as easier as FreeBSD (if we make mouse and keyboard to 
work on X)...

On Mon, Jun 12, 2023 at 6:18 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Excellent progress!
I also lost the night configuring NetBSD, setting the firewall, installing 
apps... now is up and running, just to make those X11 symlinks. Also having 
some difficulties in compiling a C library, but not mseide related...

On Mon, Jun 12, 2023 at 12:22 AM Fred van Stappen 
mailto:fi...@hotmail.com>> wrote:
Allez, the very last for tonight.

I found the guilty of the icons and images not show and the error message of 
corrupt X11 atom.
It is the image property bmo_graymask.
And in all the mseide project all images or images list have "bmo_graymask = 
true".
When setting bmo_graymask := false for all image and image-list the icon and 
image are ok.

 
https://github.com/mse-org/mseide-msegui/assets/3421249/3452e988-1504-44df-a9e9-84ecdf65806a

By the way, I never understood that property "bmo_graymask", setting it to true 
or false dont change anything on other os.

It is a excellent news because fighting with X11 is a other story.

So, perfect, the icons and images problems are solved.
I will clean all the code, set bmo_graymask := false for eveybody and do the 
commit tonight.

Only remains the access to directory in file dialog that resists.
But not for longtime (but not for tonight).

Fre;D


De : Fred van Stappen mailto:fi...@hotmail.com>>
Envoyé : dimanche 11 juin 2023 21:06
À : General list for MSEide+MSEgui 
mailto:mseide-msegui-talk@lists.sourceforge.net>>
Objet : Re: [MSEide-MSEgui-talk] New release?

Ooops, in previous post, the screenshot was without the run, here the good one.
In the terminal, no more cry of X11 for bad atom.

https://github.com/mse-org/mseide-msegui/assets/3421249/73bae81e-f28c-4790-b26c-5f408a9a2975

Note too that file access via the file-dialog is not yet perfect, for creating 
the project I have to write the full path + name, playing with the 
directory-icons was not ok.

So, to resume, still some work but it will be possible to terminate the combat.

Fre;D

De : Fred van Stappen mailto:fi...@hotmail.com>>
Envoyé : dimanche 11 juin 2023 20:53
À : General list for MSEide+MSEgui 

Re: [MSEide-MSEgui-talk] New release?

2023-06-12 Thread vasi vasi
NetBSD is in full transition to clang but it cannot give up on gcc also,
so, there are two different linkers with different configurations and
expectations. With resulted programs that cannot find their shared libs so
is a total mess... Hopefully, NetBSD 10 will ease things... But not only
the BSD world, Linux also... there are efforts towards clang...

Until then, even for C programs there are problems... Because I don't know
other way, I had to copy-symlink all libraries from X11R7 to /usr/lib, not
only six of them (thanks for the pointer)... I'm pretty sure there is a
right way to do it?  A manual or something (it wasn't this mess a few years
back...)

For example for lockf () function, (if I remember correctly, because I am
now on the linux laptop) you get errors and if you look at the man manual,
things are like in linux, but it ends up that you really must change the
value of one parameter the way compiler suggest it... In the end, raylib
4.0 compiles and runs ok but the timing is wrong because of
incompatibilities with the timer functions that are yet to be solved... A
nice graphical library that we have a pascal translation for. At least, in
OpenBSD didn't worked at all (mouse problems in glfw library)...  We really
need some pointers from the developers and the porting team... Typhoon
Relational Database needed also some interventions... Because, asking users
to do what we do is a no-no... But at least, things are working...

Otherwise, NetBSD snappier for me than OpenBSD... Your pointers were
helpful. I had an X11 freeze trying mseide but I switched to the console
and killed the X... No system crash, and I activated the journaling for the
file system, just to be sure is recoverable... It works better than in
OpenBSD...

So, it seems that NetBSD requires the most work from the three of them...
but I expect dflyBSD to be as easier as FreeBSD (if we make mouse and
keyboard to work on X)...

On Mon, Jun 12, 2023 at 6:18 AM vasi vasi  wrote:

> Excellent progress!
> I also lost the night configuring NetBSD, setting the firewall, installing
> apps... now is up and running, just to make those X11 symlinks. Also having
> some difficulties in compiling a C library, but not mseide related...
>
> On Mon, Jun 12, 2023 at 12:22 AM Fred van Stappen 
> wrote:
>
>> Allez, the very last for tonight.
>>
>> I found the guilty of the icons and images not show and the error message
>> of corrupt X11 atom.
>> It is the image property bmo_graymask.
>> And in all the mseide project all images or images list have
>> "bmo_graymask = true".
>> When setting bmo_graymask := false for all image and image-list the icon
>> and image are ok.
>>
>>
>> https://github.com/mse-org/mseide-msegui/assets/3421249/3452e988-1504-44df-a9e9-84ecdf65806a
>>
>> By the way, I never understood that property "bmo_graymask", setting it
>> to true or false dont change anything on other os.
>>
>> It is a excellent news because fighting with X11 is a other story.
>>
>> So, perfect, the icons and images problems are solved.
>> I will clean all the code, set bmo_graymask := false for eveybody and do
>> the commit tonight.
>>
>> Only remains the access to directory in file dialog that resists.
>> But not for longtime (but not for tonight).
>>
>> Fre;D
>>
>> --
>> *De :* Fred van Stappen 
>> *Envoyé :* dimanche 11 juin 2023 21:06
>> *À :* General list for MSEide+MSEgui <
>> mseide-msegui-talk@lists.sourceforge.net>
>> *Objet :* Re: [MSEide-MSEgui-talk] New release?
>>
>> Ooops, in previous post, the screenshot was without the run, here the
>> good one.
>> In the terminal, no more cry of X11 for bad atom.
>>
>>
>> https://github.com/mse-org/mseide-msegui/assets/3421249/73bae81e-f28c-4790-b26c-5f408a9a2975
>>
>> Note too that file access via the file-dialog is not yet perfect, for
>> creating the project I have to write the full path + name, playing with the
>> directory-icons was not ok.
>>
>> So, to resume, still some work but it will be possible to terminate the
>> combat.
>>
>> Fre;D
>> --
>> *De :* Fred van Stappen 
>> *Envoyé :* dimanche 11 juin 2023 20:53
>> *À :* General list for MSEide+MSEgui <
>> mseide-msegui-talk@lists.sourceforge.net>
>> *Objet :* Re: [MSEide-MSEgui-talk] New release?
>>
>> OK, I created a new project directly in NetBSD using mseide-pre-alpha,
>> with a button and a image on his face.
>> Compiled and run.
>> And there the button has his ico-image:
>>
>> https://github.com/mse-org/mseide-msegui/assets/3421249/ec05ff42-2058-4c2f-9c39-746d9ac4d462
>> And no more cry when passing with mouse on the button about invalid atom.
>>
>> Hum, hum, hum.
>>
>> So could it be that the _mfm.pas gives problem and maybe oblige, for all
>> imported image, to re-do-it when compiling a project in NetBSD?
>>
>> Anyway I have to stop for the moment this exploration.
>> Yes, it is not a combat out-of-the-box, but sure we will win.
>>
>> Fre;D
>>
>>
>> --
>> *De :*