Linux development was included in the Red/Pro project.docker-red-gtk, we could pretty easily use red/gtk in the macOS environment by developping taylor-made bash scripts. As I said before, my thought is that it could be a possible temporary replacement when macOS 32bit disappears and if red/64bit not yet provided by the Red team. Of course, developemenit of the Linux Red/View really matters alone because of the magic cross-compilation of red toolchain. GTK-New is the development that I have done to be poissibly merged in the red/master branch. @qtxie asks me this and it will review it. Right now, I have treated it and it works (apparently) for red-0.6.4 red/GTK.Compiling /home/maciek/red/github-red-gtk/environment/console/CLI/console.red ...
*** Syntax Error: Invalid word! value
*** in file: /home/maciek/red/github-red-gtk/modules/view/backends/platform.red
*** line: 846
*** at: {]
#switch config/GUI-engine [
^-native [}rcqls/red/GTK-New and it compiles and tests run ok.console-view.red (console.red with Needs: 'View ) and then execute console-view tests/react-view.red?rcqls/red:GTK-New branch, @dockimbel merged master branch into the GTK branch. This makes the GTK branch unusable for a temporary while until the validation of the PR for mergingrcqls/red:GTK-New branch . It could be good maybe to tag the commit 4de550b00b7e1b0fa410ec93dd3e9cc3336abad8 (corresponding to the GTK branch related to red-0.6.3) to something like red-0.6.3-gtk3 .rcqls/red:GTK-New was to make GTK backend compatible with the latest version View engine being in the red/red:master branch. So @qtxie is preparing improvements with respect to rcqls/red:GTK-New ? Ok, I’ll wait for these changes.rcqls/red:GTK-New… I don’t understand why I have to sync my rcqls/red:GTK since I put everything in rcqls/red:GTK-New which is based on red/red:master with the corrected GTK codes introduced to solve the problem of compilation and execution.red/red:master into red/red:GTK my PR was enough so I think that fix: red/red@6c55966 was unnecessary and if I send my PR now I think it could have some slight conflicts because of slight change of formatting between fix: red/red@6c55966 and my PR rcqls/red:GTK-New. BTW, I am not used to sync red/GTK with rcqls/red:GTK-New. Is it possible to cancel red/GTK with the commit red/red@6c55966 to only resend my PR as is?red/red:master and the goal was to red/red:master red/red:GTK branch directly to integrate the latest red master was more difficult. It was also an exercise for me to really see what are the files to maintain like expressed in the repo rcqls/red-gtkred/red:master into red/red:GTK my PR seems to be ok without loosing the history. But maybe, I miss something… rcqls/red:GTK branch before the new PR. Hope it is the good one! Thanksred:GTK branch is some sort of developping branch since it integrates all the backends (except Android one) and necessarily the GTK backend. It could be good to have a more general branch called red:View (for instance) integrating Android backend too because IMHO one of the killer feature of red is the cross-compilation. Remember that I am more a macOS user (even if I use it mostly as a linux user)… So my humble effort in helping in the development of GTK backend is mostly because of this feature of cross-compilation which is of course combined with View. red has eveything to be THE master language to manage your computer. Needs: View) from *GTK-New* runs tests/react-test.red ok. I haven't found tests/react-view.red.tests/react-view.red, it is indeed tests/react-test.red. But you can also try a lot of examples in tests/and tests/gtk3 folders of the red:GTK branchred/code repored/community repoNeeds: View line in GTK branch?rcqls/red:GTK (which would become red/red:GTK after PR validation ) is the official one (and is the same than rcqls/red:GTK-New but with history). rcqls/red:GTK-New` will then be removed! It only helps me to update to red-0.6.4...https://toltex.u-ga.fr/RedGtk is my own page that I can modify easily… there is nothing official with this page. Obviously, it is much better to manage a wiki page on GitHub and you are welcome to create it.red/red:GTK branch which would be (I hope) merged soon!red/red:GTK repo. We hope that other developers than me propose PR to the red/red:GTK repo. When a PR is significant the reviewing is obviously longer than a short PR.view [button "hello"] and it works.>> view [button "hello"] *** Runtime Error 32: segmentation fault *** at: F63B733Eh
pacman -Q | grep lib32?[red]$ pacman -Q | grep lib32 lib32-alsa-lib 1.1.7-1 lib32-at-spi2-atk 2.30.0-1 lib32-at-spi2-core 2.30.0-1 lib32-atk 2.30.0-1 lib32-attr 2.4.48-1 lib32-bzip2 1.0.6-3 lib32-cairo 1.16.0-1 lib32-colord 1.4.3-1 lib32-cracklib 2.9.6-2 lib32-curl 7.63.0-1 lib32-dbus 1.12.12-1 lib32-dconf 0.30.1-1 lib32-e2fsprogs 1.44.5-1 lib32-expat 2.2.6-1 lib32-fontconfig 2:2.13.1+12+g5f5ec56-1 lib32-freetype2 2.9.1-1 lib32-fribidi 1.0.5-1 lib32-gcc-libs 8.2.1+20181127-1 lib32-gdk-pixbuf2 2.38.0-1 lib32-glib-networking 2.58.0-1 lib32-glib2 2.58.2-1 lib32-glibc 2.28-5 lib32-gmp 6.1.2-2 lib32-gnutls 3.6.5-1 lib32-gtk3 3.24.2-1 lib32-harfbuzz 2.3.0-1 lib32-icu 63.1-2 lib32-json-glib 1.4.4-1 lib32-keyutils 1.6-1 lib32-krb5 1.16.1-1 lib32-lcms2 2.9-1 lib32-libcanberra 0.30+2+gc0620e4-1 lib32-libcap 2.25-2 lib32-libcroco 0.6.12+4+g9ad7287-2 lib32-libcups 2.2.10-1 lib32-libdatrie 0.2.12-1 lib32-libdrm 2.4.96-1 lib32-libelf 0.175-1 lib32-libepoxy 1.5.3-1 lib32-libffi 3.2.1-2 lib32-libgcrypt 1.8.4-1 lib32-libglvnd 1.1.0-1 lib32-libgpg-error 1.32-1 lib32-libgudev 232-1 lib32-libgusb 0.3.0-1 lib32-libidn 1.35-1 lib32-libidn2 2.0.5-1 lib32-libjpeg-turbo 2.0.0-1 lib32-libldap 2.4.46-1 lib32-libltdl 2.4.6+40+g6ca5e224-4 lib32-libnsl 1.2.0-1 lib32-libogg 1.3.3-2 lib32-libpciaccess 0.14-1 lib32-libpng 1.6.36-1 lib32-libproxy 0.4.15-2 lib32-libpsl 0.20.2-1 lib32-librsvg 2.44.11-1 lib32-libsoup 2.64.2-1 lib32-libssh2 1.8.0-3 lib32-libtasn1 4.13-1 lib32-libthai 0.1.28-1 lib32-libtiff 4.0.10-1 lib32-libtirpc 1.1.4-1 lib32-libunistring 0.9.10-1 lib32-libusb 1.0.22-1 lib32-libvorbis 1.3.6-1 lib32-libx11 1.6.7-1 lib32-libxau 1.0.8-2 lib32-libxcb 1.13.1-1 lib32-libxcomposite 0.4.4-3 lib32-libxcursor 1.1.15-1 lib32-libxdamage 1.1.4-3 lib32-libxdmcp 1.1.2-2 lib32-libxext 1.3.3-2 lib32-libxfixes 5.0.3-2 lib32-libxft 2.3.2-2 lib32-libxi 1.7.9-2 lib32-libxinerama 1.1.4-1 lib32-libxkbcommon 0.8.2-1 lib32-libxml2 2.9.8-5 lib32-libxrandr 1.5.1-2 lib32-libxrender 0.9.10-2 lib32-libxshmfence 1.3-1 lib32-libxtst 1.2.3-2 lib32-libxxf86vm 1.1.4-2 lib32-llvm-libs 7.0.1-1 lib32-lm_sensors 3.5.0-2 lib32-lz4 1.8.3-1 lib32-mesa 18.3.1-1 lib32-ncurses 6.1-3 lib32-nettle 3.4.1-1 lib32-openssl 1:1.1.1.a-1 lib32-p11-kit 0.23.14-1 lib32-pam 1.3.1-1 lib32-pango 1:1.42.4-1 lib32-pcre 8.42-1 lib32-pixman 0.34.0-2 lib32-polkit 0.114-1 lib32-readline 7.0.005-1 lib32-rest 0.8.1-1 lib32-sqlite 3.26.0-1 lib32-systemd 240.0-1 lib32-tdb 1.3.16-1 lib32-util-linux 2.33-1 lib32-wayland 1.16.0-1 lib32-xz 5.2.4-1 lib32-zlib 1.2.11-2 lib32-zstd 1.3.7-1 [user@4fd1ae2b91a9 red]$
archlinux tag would suggest a solution.[sony@manjarovm ~]$ pacman -Q | grep lib32 lib32-alsa-lib 1.1.7-1 lib32-alsa-plugins 1.1.7-1 lib32-at-spi2-atk 2.30.0-1 lib32-at-spi2-core 2.30.0-1 lib32-atk 2.30.0-1 lib32-attr 2.4.48-1 lib32-bzip2 1.0.6-3 lib32-cairo 1.16.0-1 lib32-colord 1.4.3-1 lib32-cracklib 2.9.6-2 lib32-curl 7.63.0-1 lib32-dbus 1.12.12-1 lib32-dconf 0.30.1-1 lib32-e2fsprogs 1.44.5-1 lib32-expat 2.2.6-1 lib32-flac 1.3.2-2 lib32-flex 2.6.4-2 lib32-fontconfig 2:2.13.1+12+g5f5ec56-1 lib32-freetype2 2.9.1-1 lib32-fribidi 1.0.5-1 lib32-gcc-libs 8.2.1+20181127-1 lib32-gdk-pixbuf2 2.38.0-1 lib32-glew 2.1.0-1 lib32-glib-networking 2.58.0-1 lib32-glib2 2.58.2-1 lib32-glibc 2.28-5 lib32-glu 9.0.0-4 lib32-gmp 6.1.2-2 lib32-gnutls 3.6.5-1 lib32-gtk3-classic 3.24.2+7+g43aeb52b73-1 lib32-harfbuzz 2.3.0-1 lib32-icu 63.1-2 lib32-json-glib 1.4.4-1 lib32-keyutils 1.6-1 lib32-krb5 1.16.1-1 lib32-lcms2 2.9-1 lib32-libasyncns 0.8+3+g68cd5af-2 lib32-libcanberra 0.30+2+gc0620e4-1 lib32-libcanberra-pulse 0.30+2+gc0620e4-1 lib32-libcap 2.25-2 lib32-libcroco 0.6.12+4+g9ad7287-2 lib32-libcups 2.2.10-1 lib32-libcurl-compat 7.63.0-1 lib32-libdatrie 0.2.12-1 lib32-libdrm 2.4.96-1 lib32-libelf 0.175-1 lib32-libepoxy 1.5.3-1 lib32-libffi 3.2.1-2 lib32-libgcrypt 1.8.4-1 lib32-libglvnd 1.1.0-1 lib32-libgpg-error 1.32-1 lib32-libgudev 232-1 lib32-libgusb 0.3.0-1 lib32-libice 1.0.9-3 lib32-libidn 1.35-1 lib32-libidn2 2.0.5-1 lib32-libjpeg-turbo 2.0.0-1 lib32-libldap 2.4.46-1 lib32-libltdl 2.4.6+40+g6ca5e224-4 lib32-libnsl 1.2.0-1 lib32-libogg 1.3.3-2 lib32-libpciaccess 0.14-1 lib32-libpng 1.6.36-1 lib32-libproxy 0.4.15-2 lib32-libpsl 0.20.2-1 lib32-libpulse 12.2-1 lib32-librsvg 2.44.11-1 lib32-libsm 1.2.3-1 lib32-libsndfile 1.0.28-2 lib32-libsoup 2.64.2-1 lib32-libssh2 1.8.0-3 lib32-libtasn1 4.13-1 lib32-libthai 0.1.28-1 lib32-libtiff 4.0.10-1 lib32-libtirpc 1.1.4-1 lib32-libunistring 0.9.10-1 lib32-libusb 1.0.22-1 lib32-libva 2.3.0-1 lib32-libva-intel-driver 2.2.0-1 lib32-libva-mesa-driver 18.3.1-1 lib32-libva-vdpau-driver 0.7.4-6 lib32-libvdpau 1.1.1-3 lib32-libvorbis 1.3.6-1 lib32-libx11 1.6.7-1 lib32-libxau 1.0.8-2 lib32-libxcb 1.13.1-1 lib32-libxcomposite 0.4.4-3 lib32-libxcursor 1.1.15-1 lib32-libxdamage 1.1.4-3 lib32-libxdmcp 1.1.2-2 lib32-libxext 1.3.3-2 lib32-libxfixes 5.0.3-2 lib32-libxft 2.3.2-2 lib32-libxi 1.7.9-2 lib32-libxinerama 1.1.4-1 lib32-libxkbcommon 0.8.2-1 lib32-libxml2 2.9.8-5 lib32-libxmu 1.1.2-2 lib32-libxrandr 1.5.1-2 lib32-libxrender 0.9.10-2 lib32-libxshmfence 1.3-1 lib32-libxss 1.2.3-1 lib32-libxt 1.1.5-2 lib32-libxtst 1.2.3-2 lib32-libxxf86vm 1.1.4-2 lib32-llvm-libs 7.0.1-1 lib32-lm_sensors 3.5.0-2 lib32-lz4 1.8.3-1 lib32-mesa 18.3.1-1 lib32-mesa-demos 8.4.0-1 lib32-ncurses 6.1-3 lib32-nettle 3.4.1-1 lib32-openssl 1:1.1.1.a-1 lib32-p11-kit 0.23.14-1 lib32-pam 1.3.1-1 lib32-pango 1.43.0-1 lib32-pcre 8.42-1 lib32-pixman 0.34.0-2 lib32-polkit 0.114-1 lib32-readline 7.0.005-1 lib32-rest 0.8.1-1 lib32-sqlite 3.26.0-1 lib32-systemd 239.6-2 lib32-tdb 1.3.16-1 lib32-util-linux 2.33-1 lib32-wayland 1.16.0-1 lib32-xz 5.2.4-1 lib32-zlib 1.2.11-2 lib32-zstd 1.3.7-1
Manjaro.-d flag) and examine the output.system/view/debug?: yes output from SO is of any use?recycle/off).recycle/off line in red script?-d -r flag correct to debug?[sony@manjarovm red]$ ./console-view --== Red 0.6.4 ==-- Type HELP for starting information. >> view [button "hello"] *** Runtime Error 32: segmentation fault *** Cannot determine source file/line info. *** Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) [sony@manjarovm red]$
-d -r flags:>> view [button "hello"] *** Runtime Error 32: segmentation fault *** Cannot determine source file/line info. ***
view [button "hello"]*** Runtime Error 32: segmentation fault *** Cannot determine source file/line info. *** Segmentation fault
prints in various places inside modules/view/backends/gtk3/gtk.reds :-)tests/gtk3/view-test.red failed (was not for red-0.6.3). I added recycle/off and eveything was ok! So i’ll add it in the red:GTK branch.recycle/off.recycle/off (I guess it is the same on Windows system.)! So I think that something is missing in the red:GTK branch. macOS redred:GTK is unstable… $ ./console
--== Red 0.6.4 ==--
Type HELP for starting information.
>> system/view/debug?: yes
== true
>> view []
-- on-change event --
face : window
word : type
old : word
new : word
-- on-change event --
face : window
word : size
old : none
new : pair
-- on-change event --
face : window
word : pane
old : none
new : block
-- on-change event --
face : window
word : parent
old : none
new : object
-- on-change event --
face : window
word : text
old : none
new : string
-- on-change event --
face : window
word : offset
old : none
new : pair
-- on-change event --
face : window
word : offset
old : pair
new : pair
show: window with?: false
*** Runtime Error 32: segmentation fault
*** at: F75B0C58hshow (IMHO randomly depending on the example)…. console binary differ from usual red binary? I want to compile Red Wallet for Gtk and run command ./console -r wallet.red, but I get error: *** Access Error: cannot open: %-r *** Where: read *** Stack:
inside docker-red-gtk. it is mostly equivalent to red binary which « encapsulates » the rebol binary. The info for compiling sred cript is provided on the Readme of the main repo.. BTW, you already did that when you compiled react-test.red`console.red is a compiled red script providing a REPL combined with a runner of red-script.usb-device (in libs/usb-monitors.red) is not iyet mplemented on linux. #switch OS [ Windows [#include %windows.reds] macOS [#include %macOS.reds] linux [#include %linux.reds] #default [] ]
read_timeout -> read-timeoutdocker-red-gtk (that I change slightly to have also an archlinux distrib) with ubuntu container and if you assume you have cloned red/red:GTK and red/walllet in a home subfolder ~/RedLinux you could compile wallet.red with the command-line red-compile —root RedLinux/red RedLinux/wallet/wallet.red by assuming thaht in the container pwd is /home/user/work as it is by default when you run the container red-docker. ./react-test &; ./react-test&. I fixed that in my repo (from now) by changing the kind of GApplication. Now it works… react-test compiled from tests/react-test.red works fine in Centos. Issue seems to be related to Archlinux and maybe the dynamic library loading process since the binary produced by ARchlinux run perfectly on Centos and Ubuntu. So it is not a pb of compilation…. red/system/config.r Linux-Musl [ OS: 'Linux format: 'ELF type: 'exe dynamic-linker: "/lib/ld-musl-i386.so.1" ]
-t Linux-Musl for must-gcc (which has its own glibc). Nothing major, since the result is the same (than installing Alpine package libc6-compat): GTK windows are shown but not the widgets inside. Don’t know what is the issue…. I created a virtualbox with alpine i386 edge linux and same result with the same installation than my dockerfile. musl. But it's been a year, so maybe it's fixed already. Having Red working with musl would be great for embedded devices, it's libc of choice for OpenWRT and other small distros.libc6-compat that allows us to use /lib/ld-linux.so.2. (gcompatused to be too but it does not work now). Apparently, everything goes well on alpine without package libc6-compat as shown below (you can test it with rcqls/docker-red-gtk repo):bash-4.4$ ldd console-view-musl /lib/ld-musl-i386.so.1 (0xf7732000) libc.so.6 => /lib/ld-musl-i386.so.1 (0xf7732000) libm.so.6 => /lib/ld-musl-i386.so.1 (0xf7732000) libgtk-3.so.0 => /usr/lib/libgtk-3.so.0 (0xf6fcb000) libcurl.so.4 => /usr/lib/libcurl.so.4 (0xf6f52000) libgdk-3.so.0 => /usr/lib/libgdk-3.so.0 (0xf6e9e000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xf6e99000) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xf6e8b000) libX11.so.6 => /usr/lib/libX11.so.6 (0xf6d59000) libXi.so.6 => /usr/lib/libXi.so.6 (0xf6d47000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xf6d40000) libcairo-gobject.so.2 => /usr/lib/libcairo-gobject.so.2 (0xf6d38000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0xf6c2d000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xf6c09000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xf6be4000) libatk-bridge-2.0.so.0 => /usr/lib/libatk-bridge-2.0.so.0 (0xf6bb4000) libepoxy.so.0 => /usr/lib/libepoxy.so.0 (0xf6ace000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xf6ab8000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xf6a6f000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf6a2d000) libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xf687b000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xf6833000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf6729000) libintl.so.8 => /usr/lib/libintl.so.8 (0xf671a000) libssh2.so.1 => /usr/lib/libssh2.so.1 (0xf66eb000) libssl.so.44 => /lib/libssl.so.44 (0xf669c000) libcrypto.so.42 => /lib/libcrypto.so.42 (0xf64f7000) libz.so.1 => /lib/libz.so.1 (0xf64de000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xf64da000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xf64ce000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xf64c3000) libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xf64bf000) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xf64bb000) libXext.so.6 => /usr/lib/libXext.so.6 (0xf64a8000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf63f3000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0xf63c9000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xf6331000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0xf62fc000) libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0xf62f8000) libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xf62e9000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf62de000) libatspi.so.0 => /usr/lib/libatspi.so.0 (0xf62af000) libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xf625d000) libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0xf61e4000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0xf61c3000) libmount.so.1 => /lib/libmount.so.1 (0xf616c000) libffi.so.6 => /usr/lib/libffi.so.6 (0xf6164000) libpcre.so.1 => /usr/lib/libpcre.so.1 (0xf6104000) libbz2.so.1 => /usr/lib/libbz2.so.1 (0xf60f7000) libXau.so.6 => /usr/lib/libXau.so.6 (0xf60f3000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xf60ec000) libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0xf60c8000) libblkid.so.1 => /lib/libblkid.so.1 (0xf607b000) libbsd.so.0 => /usr/lib/libbsd.so.0 (0xf6063000) libuuid.so.1 => /lib/libuuid.so.1 (0xf605b000) bash-4.4$ ./console-view-musl ** (console-view-musl:8): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-XG4JK9DsTL: Connection refused (console-view-musl:8): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed --== Red 0.6.4 ==-- Type HELP for starting information. >> a: 1 == 1
read %.libc6-compat….red/system/config.r and without *libc6-compat*, 2) unmodified Red sources plus *libc6-compat*.view [
list: text-list data ["John" "Bob" "Alice"]
button "Add" [append list/data "Sue"]
button "Change" [lowercase pick list/data list/selected]
]linux-gui-190111 binary from @rebolek's auto-builds.para. I don’t want to bother the really busy Red team. Could you give me also minimal examples (view mode and VID mode), if I have to test it. Of course, if you have some free time… para object?para it was not implemented yet, so I have to check it. I will let you know today evening (in 2-3 hours, once I finish some duties).para is not a modifier, it's a widget in itself. It's a block of text with specific properties.rcqls/red:GTK, confirmed. Thanks!Runtime Error 1: access violation at execution. I think it can be connected to Gtk, because I've disabled all usb & hardware code.*** Compilation Error: invalid path value: hid/open
*** in file: %/Users/rcqls/tmp/wallet/wallet.red
*** in function: exec/ctx454~open
*** at line: 1
*** near: [1820x1
h: hid/open vendor_id product_id null type
either
]Red [ Title: "wallet" Needs: 'View ] wallet: context [ list-font: make font! [name: get 'font-fixed size: 11] ui: layout compose [ title "RED Wallet" text 50 "Device:" ;dev: drop-list 125 :do-select-device btn-send: button "Send" ;:do-send disabled token-list: drop-list data ["ETH" "RED"] 60 ;select 1 :do-select-token net-list: drop-list data ["mainnet" "rinkeby" "kovan" "ropsten"] ;select 1 :do-select-network btn-reload: button "Reload" ;:do-reload disabled return text bold "My Addresses" pad 280x0 text bold "Balances" right return pad 0x-10 addr-list: text-list font list-font 520x100 return middle info-msg: text 285x20 text right 50 "Page:" tight page-info: drop-list 40 data collect [repeat p 10 [keep form p]] ;select (page + 1) ;:do-page btn-prev: button "Prev" ;disabled :do-prev-addr btn-more: button "More" ;:do-more-addr ] run: does [ ;min-size: ui/extra: ui/size ;setup-actors ;monitor-devices ;do-auto-size addr-list view/flags ui 'resize ] ] wallet/run
LD_PRELOAD but without any success… BTW, do you know that the archlinux image is at least twice larger than the ubuntu one. Archlinux installs a lot of dependencies. Did you give a try with docker-red-gtk ? I did not test it with linux but I guess it would work pretty easily. On macOS, I cross-compile a red-script and I execute the binary inside the container. The workflow would be on linux:## inside the host cd <path> redc <script>.red docker-red run <path>/<script>
~/Github/red with branch GTK activated.R since it is also compiled with gcc.(gdb) run Starting program: /media/vboxsf/wallet2 Program received signal SIGSEGV, Segmentation fault. 0x0804b068 in ?? () (gdb) bt #0 0x0804b068 in ?? () #1 0xb7fee918 in _dl_sysdep_start (start_argptr=0xbffff6c0, dl_main=0xb7fd83d0 <dl_main>) at ../elf/dl-sysdep.c:253 #2 0xb7fd7f8f in _dl_start_final (arg=0xbffff6c0) at rtld.c:415 #3 _dl_start (arg=<optimized out>) at rtld.c:522 #4 0xb7fd70bb in _start () from /lib/ld-linux.so.2
print "test", gets a SIGSEGV under gdb.camera, para and rich-text are not implemented and I am in the process to provide some preliminary resizing stuff and stuff that is related like changing offset and size. That’s why, good minimal examples are good to illustrate missing things. Feel free to send me some examples! vid-wallet.red in my repo rcqls/red-tests is working since the windows is able to be resized. I’ll send a PR.Red []
do %../red-tools/html-tools.red
main: [
tab-panel [
"Chart" [
radio "box" []
]
]
]
main: layout main
view/no-wait main
do-events>> do %d.red root size: 3454, root max: 4874, cycles: 0 *** Runtime Error 98: assertion failed *** in file: /home/sony/Code/red/runtime/datatypes/object.reds *** at line: 69 *** *** stack: red/object/rs-find 00000062h 0808B0ADh *** stack: red/object/rs-find F4CE7154h F4C45A80h *** stack: gui/connect-mouse-events 0A358190h 0A16DEF4h F4CE7154h 1382 *** stack: gui/OS-make-view 0A16DEF4h 171164072 *** stack: ctx371~make-view 0A16DEF4h 0A16DF04h *** stack: show *** stack: show *** stack: show *** stack: show *** stack: view *** stack: red/_function/call 0A16D904h F7F3D884h *** stack: red/interpreter/eval-code 0A16D904h F4A47B98h F4A47BA8h true F4A47B78h F4A47864h F4B452ECh *** stack: red/interpreter/eval-path F4A47B78h F4A47B88h F4A47BA8h false false false false *** stack: red/interpreter/eval-expression F4A47B88h F4A47BA8h false false false *** stack: red/interpreter/eval 0A16D8F4h true *** stack: red/natives/try* true 0 *** stack: do-file *** stack: red/natives/do* false -1 -1 -1 *** stack: red/interpreter/eval-arguments F4B4471Ch F4A43C50h F4A43C50h 00000000h 00000000h *** stack: red/interpreter/eval-code F4B4471Ch F4A43C40h F4A43C50h false 00000000h 00000000h F4B4471Ch *** stack: red/interpreter/eval-expression F4A43C40h F4A43C50h false false false *** stack: red/interpreter/eval 0A16D844h true *** stack: red/natives/catch* true 1 *** stack: ctx471~try-do F4B91D90h *** stack: ctx471~do-command F4B91D90h *** stack: ctx471~eval-command F4B91D90h *** stack: ctx471~run F4B91D90h *** stack: ctx471~launch F4B91D90h *** stack: ***_start
Red [Needs: View] and it seems to work.also with my new (cross-)compiled console-view. do line and by cloning your repo … (actually by pulling it)do %bolek.red works in the console-view repl where boles.red contains your code. Don’t think it is related to my last commit!red-tools is my repo available on GitHub>> load "0.00000152" == 0.0
>> load "0.00000152" == 1.52e-6
--== Red 0.6.4 ==--
Type HELP for starting information.
>> 5 / 2.0
== 2.5
>> load "0.00000152"
== 1.52e-6
>> 0.1
== 0.1
>> zero? 0.1
== false
>> 5 / 2.0
== 2.5
>> os-info
== make object! [
name: "Ubuntu 18.04.1 LTS"
arch: 'x86_64
version...38ebe69d:➜ red git:(38ebe69d) ✗ ./console-view --== Red 0.6.4 ==-- Type HELP for starting information. >> about Red 0.6.4 for Linux built 18-Jan-2019/13:31:43+01:00 >> 5 / 2.0 == 2,5.0
2,5.0 valuercqls/red:GTK branch is close to be up to date with the red/red:master branch… Not the one provided by red/red:GTK is less recent compared with master branch. Is this a possible explanation ? It is weird! I am trying to provide a link to have my last generated console-view...# guaracym @ guaracy-pc in ~/red/gtk/red on git:GTK x [20:03:52] $ red --== Red 0.6.4 ==-- Type HELP for starting information. >> 5 / 2.0 == 2.5 >> about/debug -----------RED & PLATFORM VERSION----------- RED: [ branch: "master" tag: #v0.6.4 ahead: 145 date: 5-Jan-2019/1:37:59 commit: #1c0642eff9a233db8902c9b06730202a1c0f1982 ] PLATFORM: [ name: "Manjaro Linux" OS: 'Linux arch: 'x86_64 version: 4.14.92 build: "#1 SMP PREEMPT Wed Jan 9 16:51:38 UTC 2019" ] -------------------------------------------- >> q # guaracym @ guaracy-pc in ~/red/gtk/red on git:GTK x [20:04:15] $ ./console-view --== Red 0.6.4 ==-- Type HELP for starting information. >> 5 / 2.0 == 2,5.0 >> get-env "LANG" == "pt_BR.UTF-8" >> q # guaracym @ guaracy-pc in ~/red/gtk/red on git:GTK x [20:04:36] $ LC_ALL=C ./console-view --== Red 0.6.4 ==-- Type HELP for starting information. >> 5 / 2.0 == 2.5 >> 0.1 == 0.1 >> zero? 0.1 == false >>
-d option? I compiled console with -d inside Rebol string: echo 'Rebol[] do/args %red.r "-d -r %environment/console/CLI/console.red"' | ./rebol +q -s, but under Arch I still get no debug info:% ./console --== Red 0.6.4 ==-- Type HELP for starting information. >> view [] *** Runtime Error 32: segmentation fault *** Cannot determine source file/line info. ***
-d (debug) option. I've seen output like:mateusz@mateusz-desktop:~/Red/docker-red-gtk/Scripts$ ./wallet root size: 4226, root max: 5308, cycles: 0 root size: 4226, root max: 5308, cycles: 1 root size: 4226, root max: 5308, cycles: 2 root size: 4226, root max: 5308, cycles: 3 root size: 4226, root max: 5308, cycles: 4 root size: 4226, root max: 5308, cycles: 5 root size: 4226, root max: 5308, cycles: 6 root size: 4226, root max: 5308, cycles: 7 root size: 4226, root max: 5308, cycles: 8 *** Runtime Error 98: assertion failed *** in file: /home/user/red/red/runtime/datatypes/object.reds *** at line: 69 *** *** stack: red/object/rs-find 00000062h 080909E9h *** stack: red/object/rs-find F3835A80h F5254A80h *** stack: gui/connect-mouse-events 08E8C1A0h 08C7FF9Ch F3835A80h 108 *** stack: gui/OS-make-view 08C7FF9Ch 0 *** stack: ctx371~make-view 08C7FF9Ch 08C7FFACh *** stack: show *** stack: view *** stack: ctx573~run F7FA1A90h *** stack: ***_start
docker-red-gtk. What OS do you have? And what repo did you clone in your ~/Github/red since you need to have the latest development to compile the wallet as in the repo from @loziniak. All my PR are not accepted yet in the official repo red/red:GTK. So you should use temporarily my repo rcqls/red:GTK including some resizing stuff missing in the official repo but not for long I hope. Eventhough, I already gave a try and if I remember correctly I managed to compile but with an error violation just normal since the wallet is a very complete application thanks to the Red team. _on-over value in *gtk3/gui.reds*, and it's set only in line 53. So, maybe it's connected with Garbage Collector? Perhaps we could try to compile things with recycle/off, and see what happens?Ubuntu 16.04.1 LTS (4.15.0-43-generic) 64-bit.docker-red-gtkdocker-red-init.sh (deleting > /dev/null in searching for IP address of docker0, because this command caused "Error in docker-red: no IP address!").docker-red-init.sh to .bash_profiledocker-red builddocker run --rm -ti -v ~/:/home/user/work -e DISPLAY=$(/sbin/ip -o -4 addr list docker0 | awk '{print $4}' | cut -d/ -f1):0 rcqls/red-gtk-ubuntured-compile to compile wallet.red with debugRUN git clone -b GTK https://github.com/red/red.git so it wasn't rcqls/red:GTK. Ubuntu was setted as docker image distrib (by default).rcqls/red:GTK. And these errors are just normal. rcqls/red:GTK instead, so I've change that inside your bash scripts and Dockerfile. rcqls/red:GTK in Dockerfiledocker-red --build-dir local buildred/red.docker-red-gtkto a linux box. IAs mentionned in the README, you don’t need to change the repo inside the Dockerfile, you just have to clone red/red:GTK or rcqls/red:GTK in ~/Github. The red-compile script would then take this folder to compile red script. BTW, if you are on Ubuntu, you could simply install the red as usual and if you want to use the latest GTK repo to compile use my reds script to compile directly on yopur system. In such case, docker-red-gtk is only useful to test another distribution. Just as a comment red binary (which does not include View for linux) could be simply replace with reds which is a bash-script (like red-compile) from the source. If you avec ~/Github/red folder (red/red:GTK or rcqls/red:GTK), reds ~/Github/red/environment/console/CLI/console-view.red should compile the red script to build the expected console-view binary. To get the wallet binary reds wallet.red (after cd to wallet.red folder). reds bash script: if you clone red in a path ~/tmp/red (for instance), you can compile console-view:reds —root ~/tmp/red ~/tmp/red/environment/console/CLI/console-view.red
/console-view cd ~/tmp/red reds —root . environment/console/CLI/console-view.red
~/tmp/red/console-view-t Linux to cross-compile.LC_ALL=C ./console-view ?get-env "LANG " ?cs_CZ.UTF8or something like that, let me check.GTK branch?code/Scripts/resize-image.red. But it works with my repo rcqls/GTK. Many other works already… resize-imager.ed is a nice red port...code/Scripts/tiger.red is working using my repo rcqls/red:GTK. However, I have a bug with the timer …. stopping it by closing the window fails… vid-base.red in my repo rcqls/red-tests is such a weird case where access violation occurs after I uncomment 1 more case and when I click one of them …. recycle/off makes the gobang game or Recode working…. Good news…. recycle/off was needed on linux for many examples. The fix was first proposed by @qtxie on macOS for image in runtime/collector.reds. Really happy to have found this fix. Tell me if this fix your problem (only on my repo form now). It was related to image. Good news, code/Scripts/mandelbrot.red is working now and Gobang.red, view-test.red no more need recycle/off.tiger.red, particules.red works properly.Compiling to native code...
*** Compilation Error: undefined symbol: g_application_quit
*** in file: %/home/sony/Code/red/modules/view/backends/gtk3/gui.reds
*** in function: exec/gui/OS-destroy-view
*** at line: 1906
*** near: [
g_application_quit GTKApp
](console-view:23040): Gtk-CRITICAL **: 10:38:18.170: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:23040): Pango-CRITICAL **: 10:38:18.170: pango_layout_new: assertion 'context != NULL' failed (console-view:23040): Gtk-WARNING **: 10:38:18.182: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg. This may indicate that pixbuf loaders or the mime database could not be found.
g_object_unref to gtk objects. 24 lay: [ 25 below 26 p: base 400x200 27 f: field 400 28 across 29 button "Test" [ 30 draw-chart 31 ] 32 button "Synth" [ 33 get-wave 34 ] 35 return 36 text "Cuttof" slider [bafl/frequency: to float! face/data get-wave] 37 text "resonance" slider [bafl/resonance: to float! face/data get-wave] 38 return 39 radio "Line" [chart-line?: true chart-style: 'line draw-chart] 40 radio "Spline" [chart-line?: true chart-style: 'spline draw-chart] 41 radio "Box" [chart-line?: false chart-style: 'box draw-chart] 42 radio "Circle" [chart-line?: false chart-style: 'circle draw-chart] 43 radio "Cross" [chart-line?: false chart-style: 'cross draw-chart] 44 ]
recycle/off at the beginning and recycle/on at the end… I think it is no more necessary but for view-test.red it is still necessary (otherwise refresh of the window is incomplete) meaning that something weird is occurring…. I am also working on resizing that I think weirdly very slow...rcqls/red:GTK is now my branch to submit PR and rcqls/red:GTK-dev my development branch.console-view from latest *rcqls/GTK* branch, and I've got these errors on first run:>> do %tests/react-test.red (console-view:621): Gtk-CRITICAL **: 13:40:06.059: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:621): Pango-CRITICAL **: 13:40:06.060: pango_layout_new: assertion 'context != NULL' failed free(): invalid pointer Aborted
*** Runtime Error 1: access violation errors on last two lines instead. *Gtk-CRITICAL* and *Pango-CRITICAL* sequence was repeated 6 times.$ ./console-view --== Red 0.6.4 ==-- Type HELP for starting information. >> view [] *** Runtime Error 32: segmentation fault *** Cannot determine source file/line info. ***
react-test.red also and got this:>> do %react-test.red (console-view:8427): Gtk-CRITICAL **: 13:57:51.776: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.777: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.856: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.856: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.861: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.861: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.862: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.862: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.862: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.862: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.867: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.867: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.868: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.868: pango_layout_new: assertion 'context != NULL' failed (console-view:8427): Gtk-CRITICAL **: 13:57:51.873: gtk_widget_get_pango_context: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:8427): Pango-CRITICAL **: 13:57:51.873: pango_layout_new: assertion 'context != NULL' failed *** Runtime Error 16: invalid virtual address *** at: F6A31E10h
style is now buggy when considering font in the style. I will try to consider it soon … But just to prove my purpose: change the line 20 in react-test.red style value: text "0" 30 right bold with style value: text "0" 30 right ;bold and everything would be fine. Gtk-critical… It reminds us that nothing is perfect yet!red code. I really tried for a while but without any success. tests/vid.red not working anymore. The bug on style was related to change on font. Everything is fine again for these two issues as in rcqls/red:GTK branch. code/Scripts/mandelbrot.red is then working because of the fix on style. win: [
below
p: base 400x200
button "Test" [get-wave]
]recycle/off did not solve the problem… Red/GTK is not in its phase on stabilization even things get better and better...red uses different native OS skill first. Also markup in richtext looks like similar to markup of pango which is more simple than using atrributes directly (Pango markup is not directly related to css styles).~/Desktop/releases/rebol-core$ cp rebol-core/rebol red/ cp: 无法获取'rebol-core/rebol' 的文件状态(stat): 没有那个文件或目录
~/Desktop/releases/rebol-core$ cp rebol-core/rebol red/ cp: 无法获取'rebol-core/rebol' 的文件状态(stat): 没有那个文件或目录
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libcurl3:i386>> Rebol[] do/args %red.r "-r %console.red" ** Access Error: Cannot open /home/zptian/Desktop/red-GTK/environment/console/CLI/red.r ** Near: do/args %red.r "-r %console.red"
>> Rebol[] do/args %red.r "-r %console.red" ** Access Error: Cannot open /home/zptian/Desktop/red-GTK/environment/console/CLI/red.r ** Near: do/args %red.r "-r %console.red"
view [button "Hello"] then the advantage of using Red is pretty obvious :smile: git?rebol executable into that folder, run it and compile in Rebolrebolfile is enough, so you won't have troubles with pathsrebol executable file and nothing elsedo/args %red.r "arguments here">> do/args %red.r "-r %environment/console/CLI/console.red" ** Access Error: Cannot open /home/zpt/red.r ** Near: do/args %red.r "-r %environment/console/CLI/console.red"
red-GTK/console: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory
sudo apt-get install libgtk-3-bin:i386view [button "Test"] for exampleTry running the command gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being.
view [button "test"] in Red console?code/Scripts/gradient-lab.red, you’ll see gradient but maybe there is some fix to do… (linear and radiant gradients are implemented but I suspect a radiant is not perfect)...Try running the command gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being.
zpt@zpt-PC:~/Desktop/red-GTK$ ./console (console:4617): GdkPixbuf-WARNING **: 01:18:46.831: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': 没有那个文件或目录 This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. --== Red 0.6.4 ==-- Type HELP for starting information. >>
gdk-pixbuf-query-loaders ...ls /usr/lib/i386-linux-gnu/alsa-lib libogg.so.0.8.2 audit libopenal.so.1 avahi libopenal.so.1.18.2 deepin-wine libOpenCL.so.1 dri libOpenCL.so.1.0.0 gconv libopenjp2.so.2.3.0 gdk-pixbuf-2.0 libopenjp2.so.7 gio libopus.so.0 glib-2.0 libopus.so.0.6.1 gtk-3.0 libOSMesa.so.6 i686 libOSMesa.so.8 krb5 libOSMesa.so.8.0.0 libasound.so.2 libp11-kit.so.0 libasound.so.2.0.0 libp11-kit.so.0.3.0 libasyncns.so.0 libpanel.so.5 libasyncns.so.0.3.1 libpanel.so.5.9 libatk-1.0.so.0 libpanel.so.6 libatk-1.0.so.0.22810.1 libpanel.so.6.1 libatk-bridge-2.0.so.0 libpango-1.0.so.0 libatk-bridge-2.0.so.0.0.0 libpango-1.0.so.0.4200.1 libatomic.so.1 libpangocairo-1.0.so.0 libatomic.so.1.2.0 libpangocairo-1.0.so.0.4200.1 libatspi.so.0 libpangoft2-1.0.so.0 libatspi.so.0.0.1 libpangoft2-1.0.so.0.4200.1 libavahi-client.so.3 libpcap.so.0.8 libavahi-client.so.3.2.9 libpcap.so.1.8.1 libavahi-common.so.3 libpciaccess.so.0 libavahi-common.so.3.5.3 libpciaccess.so.0.11.1 libavcodec.so.57 libpcreposix.so.3 libavcodec.so.57.107.100 libpcreposix.so.3.13.3 libavresample.so.3 libpixman-1.so.0 libavresample.so.3.7.0 libpixman-1.so.0.34.0 libavutil.so.55 libpng16.so.16 libavutil.so.55.78.100 libpng16.so.16.34.0 libcairo-gobject.so.2 libproxy.so.1 libcairo-gobject.so.2.11510.0 libproxy.so.1.0.0 libcairo.so.2 libpsl.so.5 libcairo.so.2.11510.0 libpsl.so.5.3.0 libcolordprivate.so.2 libpulse-simple.so.0 libcolordprivate.so.2.0.5 libpulse-simple.so.0.1.0 libcolord.so.2 libpulse.so.0 libcolord.so.2.0.5 libpulse.so.0.20.1 libcroco-0.6.so.3 librest-0.7.so.0 libcroco-0.6.so.3.0.1 librest-0.7.so.0.0.0 libcrypto.so.1.0.2 librsvg-2.so.2 libcrystalhd.so.3 librsvg-2.so.2.40.20 libcrystalhd.so.3.6 librtmp.so.1 libcups.so.2 libsamplerate.so.0 libcurl.so.3 libsamplerate.so.0.1.8 libcurl.so.4 libsasl2.so.2 libcurl.so.4.5.0 libsasl2.so.2.0.25 libdatrie.so.1 libsensors.so.4 libdatrie.so.1.3.4 libsensors.so.4.4.0 libdb-5.3.so libshine.so.3 libdrm_amdgpu.so.1 libshine.so.3.0.1 libdrm_amdgpu.so.1.0.0 libSM.so.6 libdrm_intel.so.1 libSM.so.6.0.1 libdrm_intel.so.1.0.0 libsnappy.so.1 libdrm_nouveau.so.2 libsnappy.so.1.1.7 libdrm_nouveau.so.2.0.0 libsndfile.so.1 libdrm_radeon.so.1 libsndfile.so.1.0.28 libdrm_radeon.so.1.0.1 libsndio.so.6.1 libdrm.so.2 libsoup-2.4.so.1 libdrm.so.2.4.0 libsoup-2.4.so.1.8.0 libedit.so.2 libsoup-gnome-2.4.so.1 libedit.so.2.0.56 libsoup-gnome-2.4.so.1.8.0 libelf-0.170.so libsoxr.so.0 libelf.so.1 libsoxr.so.0.1.1 libepoxy.so.0 libspeex.so.1 libepoxy.so.0.0.0 libspeex.so.1.5.0 libexpatw.so.1 libsqlite3.so.0 libexpatw.so.1.6.7 libsqlite3.so.0.8.6 libexslt.so.0 libssh2.so.1 libexslt.so.0.8.20 libssh2.so.1.0.1 libffi.so.6 libssl.so.1.0.2 libffi.so.6.0.4 libstdc++
view [button {hello}] is it working?rcqls/red:GTK-dev branch. That why maybe it does not work for you!git clone -b GTK-dev https://github.com/rcqls/redgit clone -b GTK-dev https://github.com/rcqls/redgit clone -b GTK-dev https://github.com/rcqls/red in some folder and that’s all!pen gradient, where gradient is done with simple pen linear red green blue - it doesn't work and that'đ actually what I've been trying - just simple gradient with fill-pen linear 10.20.30 100.150.200. So it works only with all values and looking at the [docs](https://doc.red-lang.org/en/draw.html#_linear_gradient_pen) the values are in different order than in the docs and I'm not sure how to make gradient that from top to bottom, only left to right as in the example.(console:4617): GdkPixbuf-WARNING **: 01:18:46.831: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': 没有那个文件或目录 This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being.
>> load "0.00000152" == 1.52e-6 >> 5 / 2.0 == 2.5
>> draw 10x10 [fill-pen black] *** Runtime Error 1: access violation *** at: B64EDD1Ch
>> draw 10x10 [fill-pen 0.0.0] *** Runtime Error 1: access violation *** at: B645FD1Ch
>> draw 10x10 []
== make image! [10x10 #{
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF...rcqls/red:GTK-dev on red/red:GTK. Thanks for reporting.view [base 200x200 draw [translate 10x0 [line 0x0 10x10] translate 20x0 [line 0x0 10x10] translate 30x0 [line 0x0 10x10] translate 40x0 [line 0x0 10x10]]]
rcqls/red:GTK-dev. New segment7 stuffs are then working. stylize, so will check it once I've got it ready.mv works differently than mv in BusyBox... :smile: )mv!Function pointer in the red/system documentation and actually I am using this kind of function pointer to sort glist. But maybe it is not what you want….Red/System [] add-func!: alias function! [ a [integer!] b [integer!] ] my-add: func [a [integer!] b [integer!]][probe a + b] return-func: func [return: [int-ptr!]][as int-ptr! :my-add] call-func: func [ f [int-ptr!] /local add-f [add-func!] ][ add-f: as add-func! f add-f 3 4 ] call-func return-func
GTK VERSION: 3.24.2 is for archlinux when GTK VERSION: 3.22.30 (or around) is used for other Linux distributions. Maybe, this is an explanation of the specific issue for the Archlinux distribution. I hope it is not the reason otherwise, we will have to fix that when GTK would migrate to GTK 4. I need to find a docker installation with GTK 4 and test all the current development.red/GTK with GTK version at least 3.24 it would be good to know. do/args %red.r "%../code/Scripts/clock.red"red binary but I need to have a source repo (for me ~/Github/red but you can specify another root)ubuntu:disco and GTK VERSION: 3.24.5 (latest). All the few examples I launch, were working...undefined symbol: gtk_list_box_new and ListBox was implemented in 3.10.Mandelbrot.red and raytracer.red have the proper colors. It was far from obvious (at least for me).rich-text.beginner3 is then working. Actually the size of font in linux are different from windows and macOS. Something to look at later.size-text return a correct size?size-text is not yet implemented for richtext from now. I’ll do it soon. docker-red bash script can be adapted to have it useable in the 3 main OS…. shrinkable.red example provided by the artist @toomasv. I simply replaced gtk_fixed with gtk_layout which is much more flexible than the first one. As a direct consequence, panel is clickable (I never managed to have it with gtk_fixed). gtk_layout seems to be promissing too since it embeds automatic scroller….red/red:GTK but you could always use my development repo rcqls/red:GTK-dev. I will send a PR when I have done most of the important things. When this done, the branch would still be unstable and a period of stabilization (with in particular memory leaks fixes) would then come. I am working on menu BTW. There is still some issue on richtext, but overall is not so bad from now. Examples in the doc mostly work. richtext.medium2… So it’s my use case hoping that it is not not too hard!offset-to-caret for edit and not face/selected. @toomasv rich text.medium2 is now (mostly) working. I know there is still an issue in my development if markup blocks are not embedded...draw 2x2 [fill-pen red] draw 2x2 [fill-pen black] draw 2x2 []
view[ base 100x50 draw [fill-pen red box 10x10 80x40] ]
make image! 2x2 in order to have the same result. Tell me if you have some other use cases in such vein that do not work.para. Let me sit on it a bit.odroid@xu4-bo:~$ ./rpi-gui-190226 --== Red 0.6.4 ==-- Type HELP for starting information. >> draw 50x50 [fill-pen black box 0x0 50x50] *** Runtime Error 1: access violation *** at: B64D3D1Ch
>> draw 50x50 [fill-pen black box 0x0 50x50]
== make image! [50x50 #{
24242400000000000000000000000000000000000...
>>rcqls/red:GTK-dev branch since it is now far from being in advance compared to the official repo.>> draw 2x2 [fill-pen red fill-pen black box 0x0 2x2]
== make image! [2x2 #{242424000000000000000000}]
>> layout [i: image 2x2 draw [fill-pen red fill-pen black box 0x0 2x2]]
== make object! [
type: 'window
offset: none
size: 22x22...
>> i/image
== make image! [2x2 #{FFFFFFFFFFFFFFFFFFFFFFFF}]rcqls/red:GTK-dev would not solve the problem since development is required. Except if @Respectech needs console-view for Rasperry Pi, I think it is not necessary since I can also provide a link to my last generated [console-view](https://toltex.u-ga.fr/users/RCqls/Red/console-view). It can also be useful for you if you don’t want to pull my repo. Maybe it could be good to add it to wiki page related to GTK.console-view. In fact I use syncthing to synchronize some files of my computer and my server. LOCALE bug to wikitext-table style with your latest build, but it still crashes. It's probably too complex for current version.text style. So now text-lists have no labels, but it works.>> draw 50x50 [fill-pen black box 0x0 50x50]
== make image! [50x50 #{
000000000000000000000000000000...
>>Red[] img: make image! 100x50 random/seed now/time/precise color-choice: 'random color: does [ case [ color-choice = 'random [random 255.255.255.0] color-choice = 'red [255.0.0] color-choice = 'green [0.255.0] color-choice = 'blue [0.0.255] ] ] draw_box: does [ draw_blk: compose [fill-pen (color) box 10x10 80x40] draw img draw_blk ] view compose [ below i: image (draw_box) rate 32 on-time [ i/image: draw_box show i ] button "red" [color-choice: 'red] button "green" [color-choice: 'green] button "blue" [color-choice: 'blue] button "rand" [color-choice: 'random] ]
REBOL/Core 2.7.8.4.8 (16-Jan-2016) Copyright 2016 REBOL Technologies REBOL is a Trademark of REBOL Technologies All rights reserved. Finger protocol loaded Whois protocol loaded Daytime protocol loaded SMTP protocol loaded ESMTP protocol loaded POP protocol loaded IMAP protocol loaded HTTP protocol loaded FTP protocol loaded NNTP protocol loaded Script: "Red command-line front-end" (none) Script: "Encap virtual filesystem" (21-Sep-2009) -=== Red Compiler 0.6.4 ===- Compiling /home/odroid/red/environment/console/CLI/console.red ... ...compilation time : 6362 ms Target: RPI Compiling to native code... Script: "Red/System ELF format emitter" (none) ...compilation time : 151424 ms ...linking time : 2543 ms ...output file size : 2142820 bytes ...output file : /home/odroid/red/console
odroid@xu4-bo:~/red$ sudo chmod 777 console odroid@xu4-bo:~/red$ ./console *** Runtime Error 1: access violation *** at: 0008717Ch
wget http://video.respectech.com:8080/a.com/r2
git clone -b GTK-dev https://github.com/rcqls/red.git
console.red just compile console-view.red which has the View characteristics.recycle/off fix the issue too!prints in my code, but I found that really small seemingly random changes (like print) can make it working.rcqls/red:GTK-dev branch. console-view (as I used to do), I finally wrote a very simple plugin for red/system which only gathers the two main files that plug gtk stuff inside red. I create a repo https://github.com/rcqls/gtk.reds. Red/system is just amazing since it is so simple to generate binary for any platform from one platform. gtk.reds plugin. I checked and it fails just before gtk_init. My bet is that the issue comes from the archlinux side maybe a setting in the dbus setting. system/config.r something like that first :BSD-GTK [
OS: ‘Linux
format: 'ELF
type: 'exe
dynamic-linker: "/usr/libexec/ld-elf.so.1"
syscall: 'BSD
target: 'IA-32
]system/config.r file and there is cleverly a GUI-engine option to specify GTK option instead of native. So I will try soon to add WinGTK target and test it. I think it is more difficult than BSD… A second part is the image management. BTW, for windows, it is not clear that GTK will work for Windows directly for this reason.console.red and console-view.red generates binaries that fail with a runtime error. I tried to compile with debug mode and I had an access violation in line 1307 of file runtime/datatypes/objects.reds…. Weird! Maybe I miss something but I guess @dockimbel should know if this is an expected error. The good news is that you tried to cross-compile console.red to get rpi-gui and it was a good attempt since now we know that cross-compilation is really powerful! -t RPi. From macOS, it is working. rpi-gui-dev (which is console-view in your naming convention) could be useful for people wanting to test my repo rcqls/GTK-dev. Pretty recent console-view for RPi (or ODROID) is available on my server https://toltex.u-ga.fr/users/RCqls/Red/RPI/console-view but it is not automatic as you do. console-view (cross-compiled for for RPi), it seems that everything is working. Everything is tested with ssh -Y connection. Good news! P.S.: As a reminder, I only needed to do: ln -s libcrypto.so.1.0.2 libcrypto.so.1.0.0 -r mode is required.do-events function makes the example of Hex-pave.red working. So I think that the event loop is something difficult to master… not only leaks of memory. I am trying to work on that…Redquire: init Redquire: load-list Redquire: load-package json Redquire: download-package json Redquire: load-package http-tools Redquire: download-package http-tools Redquire: load-package json *** Script Error: first does not allow map! for its s argument *** Where: first *** Stack: first
*** Script Error: path reply/2/Content-Type is not valid for char! typethat goes away every time I want to investigate it. I'll add probe and it's gone.hash!: to the token in the options.red. Now I have both in macOS and Linux an Runtime error 1: access violation just after selecting a room in the text-list. BTW, very interesting tool! P.S.: I made a git pullview [base draw [translate 0x0 [pen red line 0x0 50x50] translate 10x0 [pen red line 0x0 50x50]]]
gtk.reds to debug this stuff more easily…. cairo_set_source_rgba is required even if already initialized after a cairo_stroke). BTW, colors on image are temporarily unstable on GTK-dev since I'm trying to do better job. BTW, you were right this morniong about platform dependencies on make image!. It was different on Linux. Now it is the same but a lot of stuff needs to be done. I am trying to have redCV working in a better way… linux-cli-190328 --help. Do you think it would be a big task to build full Red binary, as in official builds: https://www.red-lang.org/p/download.html ?red binary. It only requires as usual rebol and source repo...fluid.red from learning repo of @toomasv. Combined with developement of @rebolek, I think it would lead to awesome tools. fluid style to system styles.>> #"^(2B05)" == #"⬅" >> #"^(2906)" == #"⤆"
view [panel blue [text "a"] panel green [text "b"]]
GTK branch I see two colorless panels with "a" and "b"GTK-dev branch, I see one green panel with "b"red/gui-branch. I’ll work on that soon… I guess (and pretty sure) that putting transparency you could see both color. view [panel 255.0.0.128 [text "a"] panel 0.255.0.128 [text "b"]]view [backdrop 0.0.0]. Instead black background I get default system color. Under Windows (wine, console-view.exe from 8 feb), background is black.view [text "test" yellow]rcqls/GTK-dev...red/GTK...red/GTK for now. I was migrating build server from one machine to other, that's almost done, building works, I just need to solve some https certificates problems (I believe. Server is accessible over IP address, but not with name) and once everything is ready, I'll add building of rcqls/GTK-dev branch.gtk.reds project I could reproduce the same problem and then fix it in 2 hours when I would be discouraged to find the solution otherwise. Example given in gui-branch mostly works now too …. base, but how to it for multiplatform OS-based GUI...that I don't know.base and panel, stuff that is OS-independent. And @hiiamboris has something like that I believe (I haven't tested it yet, unfortunately). to-image can be tested. Combine it with cross platform KB/mouse input synthesis and you can even test interactive part of the GUI (which really sucks right now).base, but I can't imagine testing button that way. Not only it seems different on every platform, but it can look very different on same platform also./flags [] 'resize). Also origin 0x0 does not work in Windows (wine). In GTK it works, but gets reset when resizing.view [ on-resizing [ xmenu/size/y: face/size/y ] xmenu: panel 100.100.100 [ origin 0x0 button "test" ] ]
on-resizing, so the bottom one, under Wine, is correct.view [
on-resizing [
print 'resizing
xmenu/size/y: face/size/y
]
xmenu: panel 100.100.100 [
origin 0x0
button "test"
]
do [print 'creating]
]view/tight.layout. What you have now sets the origin for things *inside* the panel.view [
on-resizing [
xmenu/size/y: face/size/y
]
origin 0x0
xmenu: panel 100.100.100 [
button "test"
]
]base and create everything from scratch. Is there a way to start with some existing facet, eg. button and just add to it, for example draw a line on button's border in it's redraw function?button, you're using a native widget and can't draw on it. If you start from base, you can do anything you want. field also cannot be styled?rich-text style.base?view compose/deep [
button "OK" 50x25 with [
image: (draw 50x25 [circle 25x12 10])
][unview]
]draw and image facets are processed for every face out there. There is absolutely no trouble in painting over a button or anything at least in Windows on API level, but in Red so far some parts might not work (like bare draw with a button). You just can't un-draw the native part ☺base when I don't like not how the native control looks, but rather how buggy it is working.base if you need full control and more visible interaction. This is where @rebolek may be the most help, with his work and docs on creating styles from scratch. Once we have a template for people to use, it will be easier. Getting an effect pipeline in place will be nice, too, for things like a disabled look and nice visuals. R2 had an extend effect, which let you create very small image resources that it would "stretch" at runtime. Just create the borders you want, and a solid or gradient center, and you can do great stuff. @rgchris was the king at creating those images.info.red is also renewed.git pull so I guess I have your new info.red too! I tried to compile a test code with your ast but default? is not defined and I don’t know where it is in my repo that I « grepped ».environment/console/help.red to have help-string.ctrl-dragging from a node and releasing mouse over canvas does not seem to work for macOS at all and on Linux releasing on canvas does not create a new node eventhough the edge is created.image/clone was infirectly used in redCV…. (BTW, I have already redCV git repo on my computer only need to git pull).dpkg --add-architecture i386 apt-get update apt-get install libc6:i386 libcurl4:i386
... libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 (0xf51f3000) libpng12.so.0 => not found libtiff.so.5 => /usr/lib/i386-linux-gnu/libtiff.so.5 (0xf5174000) libjasper.so.1 => not found libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 (0xf4c7f000) libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 (0xf4bbe000) libdc1394.so.22 => not found libavcodec.so.54 => not found libavformat.so.54 => not found libavutil.so.52 => not found libswscale.so.2 => not found ...
libpng16.so.16.34.0 installed…. So maybe it is easier for me to idrectly install opencv in my docker container. BTW,, if you are on macOS instead of VB you can also try my project [https://github.com/rcqls/docker-red-gtk](https://github.com/rcqls/docker-red-gtk) which combined with the reds project provide workflow :vagrant ssh and it works well on macOS. Don’t know if you’ll need to adapt vagrantfile for windows ssh connection. Hope it works as is on windows too since it is also the goal. I did not find more recent ubuntu linux i3!6 box. Maybe I’ll try to create more vagrantfiles with 64bits ubuntu/debian box.red-gtk](https://toltex.u-ga.fr/users/RCqls/Red/red-gtk) binary to complete the console-view. The red-gtk binary provides compilation of red and reds script without the need of compilation from sourcevagrant ssh is a really nice feature. Can’t test on Windows…. But I am pretty sure there is a slight change to apply to make it working. Thanks for giving a try!red-gtk binary link and info about the requirements for linux/GTK.red-gtk (I have a script that do that in less than 30 sec). Let's notice that console-view binary from my website is more unstable since it is updated at every compilation of new development (which can introduce bad regressions) when red-gtk is not automated (and then more stable eventhough not perfect yet). red-gtk provides compilation of red and R/S scripts when console-view don’t. Also like the red binary, the console is compiled at the first use of red-gtk allowing it to be used as the console.apt install red-lang on the Debian servers I use. All dependencies solved. Same for Red Hat or any other distro, of course.</dream>gstreamer since it provides a lot of multimedia very quickly. From now, additional dependency is libgstreamer-1.0.so.0. On my Debian virtual box, I installed the following packages (even though, the two or three first should be enough):apt-get install libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly gstreamer1.0-libav gstreamer1.0-tools gstreamer1.0-x gstreamer1.0-alsa gstreamer1.0-pulseaudio
vagrant-red-gtk project. The vagrant files (bento-???) include the dependencies on gstreamer to make camera stuff available.
(gtkcam:11999): GStreamer-CRITICAL **: 08:12:38.397: gst_bin_add_many: assertion 'GST_IS_ELEMENT (element_1)' failed
(gtkcam:11999): GStreamer-CRITICAL **: 08:12:38.397: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed
(gtkcam:11999): GStreamer-CRITICAL **: 08:12:38.397: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed
(gtkcam:11999): GLib-GObject-CRITICAL **: 08:12:38.414: g_object_get: assertion 'G_IS_OBJECT (object)' failed
(gtkcam:11999): Gtk-CRITICAL **: 08:12:38.414: gtk_widget_set_size_request: assertion 'GTK_IS_WIDGET (widget)' failed
(gtkcam:11999): Gtk-CRITICAL **: 08:12:38.414: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(gtkcam:11999): Gtk-CRITICAL **: 08:12:38.414: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
apt search gstreamer? What it is true, I have to provide better messages output when plugins are not installed.v4l2src has to be enable with export GST_V4L2_USE_LIBV4L2=1 in the .bash_profile (for instance). But it is not enough, gtksink is now supposed to be in libgstreamer-plugins-bad when it was before in libgstreamer-plugins-good. However iin ubuntu based distribution, it is in gstreamer1.0-gtk3, so sudo apt install gstreamer1.0-gtk3 is required. In my VBox with linuxmint, it works now. (gtkcam:310): GStreamer-CRITICAL **: 08:44:55.844: gst_bin_add_many: assertion 'GST_IS_ELEMENT (element_1)' failed
(gtkcam:310): GStreamer-CRITICAL **: 08:44:55.844: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed
(gtkcam:310): GStreamer-CRITICAL **: 08:44:55.844: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed
gst-launch-1.0 v4l2src ! videoconvert ! gtksink ?gst-launch-1.0 v4l2src ! videoconvert ! gtksink or gst-launch-1.0 v4l2src ! gtksink… Ok, indeed, it looks like your camera is not recognized by your Linux. The command is supposed to launch the webcam. gst-launch-1.0 v4l2src ! videoconvert ! gtksink could be tested in 64bits mode too after installing it (of course).export RED_GTK_CAMERA=YES. I’ll push it in rcqls/red:GTK-dev soon./dev/video0): .bah_profile (or equivalent):export RED_GTK_CAMERA=YES export GST_V4L2_USE_LIBV4L2=1
# for gstreamer installation apt-get install libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good # optional installation for further apt-get install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-tools gstreamer1.0-x gstreamer1.0-alsa gstreamer1.0-pulseaudio # In case plugin gtksink is not already installed in standard plugins above: apt-get install gstreamer1.0-gtk3 # for detection of webcam apt-get install libgudev-1.0-0
gst-launch-1.0 v4l2src ! videoconvert ! gtksink which launchs a camera viewer. Normally if this test passes camera is supposed to work inside red.red/tests/view-test.red debug mode needs to be deactivated (issue nothing related to camera).gst-launch-1.0 v4l2src ! videoconvert ! gtksink as a first set.# pierre@latitude: ~ < 2019_05_21__21:57:13 > wget https://toltex.u-ga.fr/users/RCqls/Red/gtkcam --2019-05-21 21:57:20-- https://toltex.u-ga.fr/users/RCqls/Red/gtkcam Résolution de toltex.u-ga.fr (toltex.u-ga.fr)… 129.88.13.66 Connexion à toltex.u-ga.fr (toltex.u-ga.fr)|129.88.13.66|:443… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 22556 (22K) [text/plain] Sauvegarde en : « gtkcam » gtkcam 100%[========================================================================================================>] 22.03K 124KB/s ds 0.2s 2019-05-21 21:57:21 (124 KB/s) — « gtkcam » sauvegardé [22556/22556] # pierre@latitude: ~ < 2019_05_21__21:57:21 > chmod +x gtkcam # root@latitude: ~ < 2019_05_21__22:47:37 > apt install libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly gstreamer1.0-libav gstreamer1.0-tools gstreamer1.0-x gstreamer1.0-alsa gstreamer1.0-pulseaudio ... # pierre@latitude: ~ < 2019_05_21__22:57:15 > vi_bkp_diff .bashrc 239a240,243 > # Pour faire tourner gtkcam > export RED_GTK_CAMERA=YES > export GST_V4L2_USE_LIBV4L2=1 > # pierre@latitude: ~ < 2019_05_21__23:13:51 > gst-launch-1.0 v4l2src ! videoconvert ! gtksink Définition du pipeline à PAUSED... Le pipeline est actif et n’a pas besoin de phase PREROLL… Passage du pipeline à la phase PLAYING… New clock: GstSystemClock ERREUR : de l’élément /GstPipeline:pipeline0/GstGtkSink:gtksink0 : Output widget was destroyed Information de débogage supplémentaire : gstgtkbasesink.c(486): gst_gtk_base_sink_show_frame (): /GstPipeline:pipeline0/GstGtkSink:gtksink0 Execution ended after 0:00:07.269765264 Définition du pipeline à PAUSED... Définition du pipeline à READY (prêt)… Définition du pipeline à NULL… Libération du pipeline… # pierre@latitude: ~ < 2019_05_21__23:15:55 > # Test worked: I saw my face. But 32 bits packages were necessary: # root@latitude: ~ < 2019_05_21__23:45:37 > apt install libgstreamer1.0-0:i386 gstreamer1.0-plugins-base:i386 gstreamer1.0-plugins-good:i386 gstreamer1.0-tools:i386 gstreamer1.0-x:i386 gstreamer1.0-pulseaudio:i386 gstreamer1.0-gtk3:i386 libmjpegutils-2.1-0:i386 libmpeg2encpp-2.1-0:i386 libmplex2-2.1-0:i386 ... # pierre@latitude: ~ < 2019_05_21__23:47:35 > ./gtkcam
# pierre@latitude: ~ < 2019_05_21__23:57:28 >
wget https://toltex.u-ga.fr/users/RCqls/Red/red-gtk
--2019-05-21 23:57:31-- https://toltex.u-ga.fr/users/RCqls/Red/red-gtk
Résolution de toltex.u-ga.fr (toltex.u-ga.fr)… 129.88.13.66
Connexion à toltex.u-ga.fr (toltex.u-ga.fr)|129.88.13.66|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 1378982 (1.3M) [text/plain]
Sauvegarde en : « red-gtk »
red-gtk 100%[===================>] 1.31M 127KB/s ds 9.9s
2019-05-21 23:57:41 (136 KB/s) — « red-gtk » sauvegardé [1378982/1378982]
# pierre@latitude: ~ < 2019_05_21__23:57:41 >
chmod +x red-gtk
# pierre@latitude: ~ < 2019_05_21__23:57:50 >
./red-gtk
Compiling compression library...
Compiling Red console...
GTK VERSION: 3.24.5
Experimental camera initialized!
--== Red 0.6.4 ==--
Type HELP for starting information.
>>
# pierre@latitude: ~ < 2019_05_22__00:00:17 >
cd dev/red_rcqls/tests
# pierre@latitude: ~/dev/red_rcqls/tests < 2019_05_22__00:33:08 >
vi_bkp_diff view-test.red
6c6
< system/view/debug?: yes
---
> system/view/debug?: no
# pierre@latitude: ~/dev/red_rcqls/tests < 2019_05_22__00:33:19 >
~/red-gtk view-test.red
GTK VERSION: 3.24.5
Experimental camera initialized!
Type: window Style: none Offset: none Size: 1100x800 Text: "Red View"
Type: button Style: none Offset: 10x10 Size: 60x40 Text: "Hi"
Type: button Style: none Offset: 100x10 Size: 60x40 Text: "Hello"
Type: button Style: none Offset: 180x10 Size: 60x40 Text: "Change"
Type: check Style: none Offset: 300x270 Size: 80x24 Text: "Debug?"
Type: check Style: none Offset: 300x300 Size: 80x24 Text: "Big/small font"
...red-gtk for ODROID is not possible but console-view would be buildable for ARM by cross-compilation. If gst-launch above is working for you I would be able a try to crosscompile a console-view for ODROID. But before, gst-launch would be the first step to test after completing gstreamer installation.view-test.red is not working. Only a simple test I have prepared on my red-tests repo is working from now. The link of the binary console-odroid (in fact RPi arch) is [here](https://cqls.dyndoc.fr/users/RCqls/Red/console-odroid). Dependencies are mostly the same than for linuxmint….qt@dkPI3:~$ ./console-view GTK VERSION: 3.22.30 No protocol specified Unable to init server: Could not connect: Connection refused (console-view:7416): Gtk-WARNING **: 16:52:17.431: cannot open display: :0
sudo ./console-view, then works fine../console-view: symbol lookup error: ./console-view: undefined symbol: gtk_menu_popup_at_pointer
xhost + should solve the issue about display.gnome-calculator or anything like that; if yes and it works, check with ldd if it's linking to the same libs as Red; if they're the same then I don't know what it could be :)*** Compilation Error: undefined word ask. I guess some include files are required. BTW, Great Job!ask is needed only for inputting Gitter token, I can replace it with View dialog.ask*** Compilation Error: undefined word input-gitter-token.input-gitter-token before using it :DNeeds: View in order to compile…. Of course I can do it by myselfdo with #include but ….redquire... I never tried to compile it, so thanks for the testing. I guess I should try it and fix all these problems.#include...http-toolsthere. I need to think about it.xhost + does not work for you?xhost +?%config.r.stack-align-16?: yes entry in Linux target in %config.r file on an ArchLinux instance, and the GTK backend then seems to work fine, no segfault on calling view.-d. > red.exe -d
> red.exe --cli -d
Red [Needs: 'View] view/flags [on-resize [print "resize"] button "test"] 'resize does not print anything.on-resizing instead of on-resize works for me. I have tried to implement on-resize with configure-event but nothing perfect yet…. free(): invalid pointer [1] 8827 abort (core dumped) ./console-view-latests
*** Script Error: PARSE - matching by datatype not supported for any-string! input *** Where: parse *** Stack: layout layout
red/tests/gtk3/view-test.redcode/Scripts/mandelbrot.redmalloc/free in Gritter?red/tests/gtk3/view-test.red seems to have the same issue, I try to find a minimal example…. handlers.reds.Red[Needs: View] f: make font! [name: "Arial" size: 120] view [base 140x140 draw [font f text 10x10 "A"]]
gritter.red is one of them) using make font! fail with the same error message:free(): invalid pointer Aborted
make font! related to cairo_font_options_destroy. Commenting the related line makes all the code working. However I need to fix it. There is another bug on image that does not show anymore.cairo_font_options_destroy argument was badly declared.view-test.red work? I got a crash when running it on ArchLinux.*** Runtime Error 1: access violation *** in file: /home/qt/dev/red/runtime/datatypes/block.reds *** at line: 92 *** *** stack: red/block/rs-clear 0814CAF4h *** stack: gui/get-event-flags 09A046D4h *** stack: event/eval-path 09A046D4h F524D69Ch 00000000h F524D588h false *** stack: red/actions/eval-path 09A046D4h F524D69Ch 00000000h F524D588h false *** stack: red/interpreter/eval-path F524D69Ch F524D598h F524D598h false false true false *** stack: red/interpreter/eval-expression F524D598h F524D598h false true false *** stack: red/interpreter/eval-arguments F534F450h F524D588h F524D598h 00000000h 00000000h *** stack: red/interpreter/eval-code F534F450h F524D588h F524D598h true 00000000h 00000000h F534F450h *** stack: red/interpreter/eval-expression F524D588h F524D598h false true false *** stack: red/interpreter/eval-next F524D578h F524D598h true *** stack: red/natives/reduce* false 1 *** stack: red/natives/do-print false true *** stack: red/natives/print* false *** stack: red/interpreter/eval-arguments F534FBF0h F524D4C4h F524D4C4h 00000000h 00000000h *** stack: red/interpreter/eval-code F534FBF0h F524D4B4h F524D4C4h false 00000000h 00000000h F534FBF0h *** stack: red/interpreter/eval-expression F524D4B4h F524D4C4h false false false *** stack: red/interpreter/eval 09A04704h true *** stack: red/natives/if* false *** stack: red/interpreter/eval-arguments F534EFF0h F524D1B8h F524D1C8h 00000000h 00000000h *** stack: red/interpreter/eval-code F534EFF0h F524D188h F524D1C8h false 00000000h 00000000h F534EFF0h *** stack: red/interpreter/eval-expression F524D188h F524D1C8h false false false *** stack: red/interpreter/eval F524D114h true *** stack: red/interpreter/eval-function 09A046B4h F524D114h *** stack: red/_function/call 09A046B4h F7F4813Ch *** stack: red/interpreter/eval-code 09A046B4h F51D7E30h F51D7E30h false 00000000h 00000000h 09A04624h *** stack: red/interpreter/eval-expression F51D7E10h F51D7E30h false false false *** stack: red/interpreter/eval 09A046A4h true *** stack: red/natives/try* true 0 *** stack: do-safe *** stack: ctx400~awake F7F481A4h *** stack: gui/make-event 09B35308h 2 25 *** stack: gui/combo-selection-changed 09B35308h F498A978h
view-test.red is inside tests/gtk3. I just found a fix for image issue and I’ll send a PR in a few minutes. After this PR, everything is working fine now. gritter is back!field which shows unicode supported in the view-test window, the window crashes...Change button...unicode supported issue is known for me. Clicking on Change button works for me both inside my docker archlinux and ubuntu containers.set-textadapted from macOS to update text that only fails with unicode characters.unicode/load-utf8-buffer is more precisely the line where the error occurs. I spent lot of time to try to fix it but without any success.set-text: func [ obj [handle!] ctx [node!] text [c-string!] /local size [integer!] str [red-string!] face [red-object!] out [c-string!] ][ size: length? text if size >= 0 [ str: as red-string! get-node-facet ctx FACE_OBJ_TEXT if TYPE_OF(str) <> TYPE_STRING [ string/make-at as red-value! str size UCS-2 ] if size = 0 [ string/rs-reset str exit ] ;; TODO: bug with unicode characters just below unicode/load-utf8-buffer text size GET_BUFFER(str) null yes face: push-face obj if TYPE_OF(face) = TYPE_OBJECT [ ownership/bind as red-value! str face _text ] stack/pop 1 ] ]
text ? Are you sure it's UTF-8 string?c-string!. There is no bug when no unicode is initially set. But the weird point is that when text contains only regular characters (i.e. replacing all unicode characters), it fails too… str with the content of text...at-spi2-core:i386 was ok on Buster?# root@latitude: ~ < 2019_07_06__20:04:01 > apt install libgtk-3-bin:i386 Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : libgtk-3-bin:i386 : Dépend: libgtk-3-0:i386 (>= 3.24.5-1) mais ne sera pas installé E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ». # root@latitude: ~ < 2019_07_06__20:04:12 >
# root@latitude: ~ < 2019_07_06__20:11:03 > dpkg --list 'libgtk-3*' Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-==================-============-============-=========================================================== ii libgtk-3-0:amd64 3.24.5-1 amd64 GTK+ graphical user interface library rc libgtk-3-0:i386 3.24.5-1 i386 GTK+ graphical user interface library ii libgtk-3-bin 3.24.5-1 amd64 programs for the GTK+ graphical user interface library ii libgtk-3-common 3.24.5-1 all common files for the GTK+ graphical user interface library ii libgtk-3-dev:amd64 3.24.5-1 amd64 development files for the GTK+ library ii libgtk-3-doc 3.24.5-1 all documentation for the GTK+ graphical user interface library
# root@latitude: ~ < 2019_07_06__20:12:03 >
apt install libgtk-3-0:i386
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :
Les paquets suivants contiennent des dépendances non satisfaites :
libgtk-3-0:i386 : Dépend: libatk-bridge2.0-0:i386 (>= 2.5.3) mais ne sera pas installé
Dépend: libcups2:i386 (>= 1.6.0) mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».
# root@latitude: ~ < 2019_07_06__20:12:09 >dpkg --get-selections > something before switching to Devuan: I did the same again, I'm browsing through the diff, see what I can try.apt-get install libc6 libcurl4 apt-get install libelementary1 apt-get install dbus-x11
:i386 on 64 bits machine...# root@latitude: ~ < 2019_07_06__20:47:33 >
apt install libc6:i386 libcurl4:i386 libelementary1:i386 dbus-x11:i386
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :
Les paquets suivants contiennent des dépendances non satisfaites :
dbus-x11:i386 : Dépend: libdbus-1-3:i386 (= 1.12.12-1+devuan2) mais ne sera pas installé
libelementary1:i386 : Dépend: libecore-con1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-drm2-1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-evas1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-fb1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-file1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-imf1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-input1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-wl2-1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore-x1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libecore1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libedje1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libeeze1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libefreet1a:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libeio1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libelocation1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libemotion1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libethumb-client1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libethumb1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
Dépend: libevas1:i386 (>= 1.21.1-0~eo) mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».
# root@latitude: ~ < 2019_07_06__20:47:39 >:i3!6 packages it is safe I hope apt search libelementary1:i386 ?# root@latitude: ~ < 2019_07_06__20:47:39 > apt search libelementary1:i386 En train de trier... Fait Recherche en texte intégral... Fait # root@latitude: ~ < 2019_07_06__20:49:22 >
:i386view-test.red app crashes on clicking the [Change] button. Do you know what's wrong there?Change button that does a lot of thing when clicking it. *** Script Error: json has no value *** Where: post-data *** Stack: do-file do-events do-actor do-safe
>> about Red 0.6.4 for Windows built 5-Jul-2019/19:00:59+03:00 commit #446550a
*** Runtime Error 1: access violation *** at: 9EC40514h
Change button is an assert failed (In debug mode). I merged master branch into GTK branch, it's fixed now.useR Toulouse.recycle/off required to make view-test.red working. Great stabilization of the code! Nice!!!! --== Red 0.6.4 ==-- Type HELP for starting information. *** Runtime Error 1: access violation *** at: 0812C996h
gitter client does not show properly for the las few days (only the electron-based application). Do yon think gritter and gitter client could interact together? I don't think so but gitter client starets to get messy (bad layout: the textarea for typing the message is located almost on top and no more at the bottom) few days after I tested gritter. But to be clear, I don't think it is related but maybe you have a better understanding. BTW, I have to use gitter inside the browser since the electron-based client is too messy. Everything is fine on gitter mobile too. Really weird and I have already try to reinstall gitter several times. We really need gritter :smile: (console-gui:1614): Gdk-CRITICAL **: 01:18:36.795: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed (console-gui:1614): Gdk-CRITICAL **: 01:18:36.798: gdk_cursor_new_from_name: assertion 'GDK_IS_DISPLAY (display)' failed set cursor: 09E3F348 (console-gui:1614): Gdk-CRITICAL **: 01:18:36.800: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed (console-gui:1614): Gdk-CRITICAL **: 01:18:36.800: gdk_cursor_new_from_name: assertion 'GDK_IS_DISPLAY (display)' failed
*** Runtime Error 1: access violation *** in file: /Users/rcqls/Github/red/modules/view/backends/gtk3/draw.reds *** at line: 142 *** *** stack: gui/OS-draw-pen 00000000h 0 false false *** stack: check-pen 00000000h 098400C4h F48934E8h F4893528h F48934E8h 1618 true *** stack: parse-draw 00000000h 098400C4h true *** stack: gui/OS-draw-face 00000000h 098400C4h *** stack: ctx408~draw-face 098400B4h 098400C4h *** stack: ctx559~paint F4A23120h *** stack: ctx539~on-drawing F4A232F0h *** stack: red/_function/call 0983FFB4h F4A232F0h *** stack: red/interpreter/eval-code 0983FFB4h F488541Ch F488541Ch false 00000000h 00000000h 0983FF14h *** stack: red/interpreter/eval-expression F48853FCh F488541Ch false false false *** stack: red/interpreter/eval 0983FFA4h true *** stack: red/natives/do* false -1 -1 -1 *** stack: red/interpreter/eval-arguments F4AE4414h F48853D8h F48853D8h 00000000h 00000000h *** stack: red/interpreter/eval-code F4AE4414h F48853C8h F48853D8h false 00000000h 00000000h F4AE4414h *** stack: red/interpreter/eval-expression F48853C8h F48853D8h false false false *** stack: red/interpreter/eval 0983FF84h true *** stack: red/natives/try* true 0 *** stack: do-safe *** stack: do-actor *** stack: ctx400~awake F4A267F8h *** stack: gui/make-event 09A17240h 0 34 *** stack: gui/base-draw 09A17240h 099BAC00h F4A23314h
-d (what I. call debug mode)....as draw-ctx! int/value returns null with int: as red-integer! (object/get-values face) + gui/FACE_OBJ_DRAW.on-drawing event, scroller, etc. Maybe them haven't been implemented in the GTK backend.on-drawing eventJulia is already).gui-console.red compiles properly but not running even though some missing GTK parts of code is not implemented. do [...]) or use encapping mode, which basically just pack everything into Redbin and feds it to interpreter.an automated fuzzer (), which will test also the otherwise inaccessible "dynamic" parts of code."functional" symbol is not a concept in Redbol languages. All values are anonymous, including functions. You can reference other values directly using one word or several words, or indirectly using path accessors, actions or natives.an automated fuzzer (), which will test also the otherwise inaccessible "dynamic" parts of code() is a typo. "dynamic" parts of code are those which can't be statically compiled (because there is some homoiconic manipulation)."functional" symbol is not a concept in Redbol languages. All values are anonymous, including functions. You can reference other values directly using one word or several words, or indirectly using path accessors, actions or natives.symbol is the most general term from parsing (https://en.wikipedia.org/wiki/Parsing ) and corresponding formalism (https://en.wikipedia.org/wiki/Symbol_(formal) ). A functional symbol is a symbol which refers to *something taking an input and producing some output*. Nothing more, nothing less.view function in Red runtime. word! values, the ones you call "symbols"), but, to do any kind of fuzz-testing, these Red/System scripts need to be statically compiled, and what needs to be fuzzed in such case is the native code or library calls.block!s of View dialect) which contain "functional symbols" (word! and any other values), using automated "null" backend. This can uncork many hidden bugs, and can potentially scale up to general-purpose Red code.gui-console. Now I need to understand what it needs to be drawn.... Lot of work remaining but it is more fun to not have failures.gui-console is not a priority!tips!, console-gui looks better even though it does not work from now!debug-print in gui-console.redexit-ask-loop ending in such a way to have eval-command running. When typing Enter, exit-ask-loop is executed but nothing is really stopped staying in the ask command related to eval-command. I see post-quit-msg in the other backends but I really don't know what to put inside this function to stop ask command. If you have any tips, I will appreciate.ask. The exit-ask-loop is used to exit the loop. In GTK backend, we need to force g_main_context_iteration return false in order to exit the loop. https://github.com/red/red/blob/GTK/modules/view/backends/gtk3/events.reds#L451exit-loop: exit-loop - 1 inside post-quit-msg seems to work! I quickly tested console-view and it seems to still work. % ~/prj/red/linux-gui-190724 GTK VERSION: 3.24.8 --== Red 0.6.4 ==-- Type HELP for starting information. >> view [panel [] on-down [append face/pane layout/only [text "aaa"]]] (linux-gui-190724:16004): Gtk-WARNING **: 22:15:31.443: Attempting to add a widget with type GtkLabel to a container of type GtkLayout, but the widget is already inside a container of type GtkEventBox, please remove the widget from its existing container first. (linux-gui-190724:16004): Gtk-CRITICAL **: 22:15:31.447: gtk_layout_move: assertion 'gtk_widget_get_parent (child_widget) == GTK_WIDGET (layout)' failed (linux-gui-190724:16004): GLib-GObject-WARNING **: 22:15:31.447: instance with invalid (NULL) class pointer (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:31.447: g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:31.448: g_object_set_qdata: assertion 'G_IS_OBJECT (object)' failed (linux-gui-190724:16004): GLib-GObject-WARNING **: 22:15:31.448: instance with invalid (NULL) class pointer (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:31.448: g_signal_handlers_destroy: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (linux-gui-190724:16004): GLib-GObject-WARNING **: 22:15:31.448: instance with invalid (NULL) class pointer (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:31.448: g_signal_handlers_destroy: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:31.448: g_object_unref: assertion 'old_ref > 0' failed (linux-gui-190724:16004): Gtk-CRITICAL **: 22:15:52.427: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed (linux-gui-190724:16004): Gtk-CRITICAL **: 22:15:52.427: gtk_layout_move: assertion 'GTK_IS_WIDGET (child_widget)' failed (linux-gui-190724:16004): GLib-GObject-CRITICAL **: 22:15:52.427: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
text by button everything was fine, I realized that I added this feature longtime ago when considering update-z-order used in the view-test.red. I renamed it change-pane (that's why I couldn't remember this feature) vhich is more explicit. I also updated it to fix your issue but it is still in the last PR I have submitted but nit yet accepted.... You can test it to rcqls/red:GTK.&, <, >.... . Soon I'll propose a function to escape only & and < which are the only characters needed to escape. For selection caret-to-offset needs to be improved for GTK.& and < written in red/system. As a direct consequence, selection is much more useable even though not perfect yet :caret-to-offset.rcqls/red:GTK since PR not yet accepted), here a link [gui-console](https://cqls.dyndoc.fr/users/RCqls/Red/gui-console).makedoc/easy-VID-rt.red is very helpful to test rich-text widget in combination now with the gui-console.makedoc/easy-VID-rt.red on my VB win7, there is no scroller like in GTK. Do you confirm it?red-GTK and builded, but;>> view[] *** Script Error: view has no value *** Where: catch *** Stack:
console.red script to compile needs Needs: 'View. You should compile console-view.red instead. You can also directly use the gui-consolebinary (see link above).sony➜~/code/red(GTK-dev✗)» ./gui-console [11:59:12] GTK VERSION: 3.24.10 *** Runtime Error 32: segmentation fault *** at: F7582628h
gui-console binary or are you compiling from source?red/GTKgui-console on my archlinux container then...GTK VERSION: 3.24.2sony➜~/code/red(GTK✗)» ./gui-console [12:04:34] GTK VERSION: 3.24.10 (gui-console:23725): Gdk-CRITICAL **: 12:08:51.772: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed (gui-console:23725): Gdk-CRITICAL **: 12:08:51.772: gdk_cursor_new_from_name: assertion 'GDK_IS_DISPLAY (display)' failed (gui-console:23725): Gdk-CRITICAL **: 12:08:51.773: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed (gui-console:23725): Gdk-CRITICAL **: 12:08:51.773: gdk_cursor_new_from_name: assertion 'GDK_IS_DISPLAY (display)' failed --== Red 0.6.4 ==-- Type HELP for starting information.
-r mode since -u and -c works now at compilation but not at execution time.console-view.red in release mode from my GTK branch and then execute tests/cursor.red which is supposed to work from this morning....gui-console.red for odroid (RPi target), it works on odroid... (Except the wheeling....) test/cursor.red is working too.gui-console.redsvs: system/view/screens/1 svs/pane: next svs/pane
tests/cursor.red, is it working after compiling it?i3 window manager could also be an explanation.....gui-console on Odroid and :help and what that work once but then no more instruction is validated by enter key.wheel is not responding whereas it is working on browser (and tested on macOS with the same mouse). Good news ctrl+arrows work (not on macOS since these shortcuts are intercepted by the system first).gui-console everything is fine but when closing the window there is a fail: Runtime Error 95: no CATCH for THROW.gui-console and console-view which create binaries but fail at execution (related to objects.reds when compiled in debug mode).? command with no arguments I cannot run any other command, Enter key does not have effect. Scrolling a mouse wheel over a console window kinda releases frozen events, and unsuccessful commands are run. The same with help command.GTK VERSION: 3.24.83.24.2red/GTK branch with target RPi or maybe linux-ARM (depending on the model but not sure) as mentionned by @Respectech. I can provide binaries on my server if you ask for it. chmod u+x.GTK-dev branch, or is it moved to official GTK branch entirely? It seems to be the most up to date branch.red/red:GTKis the official branch now since @bitbegin is now contributing too. So rcqls/red:GTK is very often synchroniezd with the official red:GTK branch. My GTK-dev is still there since there is the camera development which require a lot of dependencies that’s why I did not merge this work inside the official branch.text face is not clickable. Compare effects of running this code on Windows and Linux (latest github version):view [text "click me" white [print "CLICKED"]]
(console-view:6157): GLib-GObject-CRITICAL **: 15:05:33.538: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed (console-view:6157): Gtk-CRITICAL **: 15:05:33.538: gtk_widget_set_size_request: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:6157): Gtk-CRITICAL **: 15:05:33.538: gtk_widget_queue_resize: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:6157): Gtk-CRITICAL **: 15:05:33.538: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:6157): Gtk-CRITICAL **: 15:05:33.538: gtk_widget_show_all: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:6157): Gtk-CRITICAL **: 15:05:33.539: gtk_widget_grab_focus: assertion 'GTK_IS_WIDGET (widget)' failed (console-view:6157): GLib-GObject-CRITICAL **: 15:05:33.539: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed *** Runtime Error 1: access violation *** in file: red-github/modules/view/backends/gtk3/gui.reds *** at line: 1618 *** *** stack: gui/OS-show-window 141493808 *** stack: gui/OS-refresh-window 141493808 *** stack: ctx408~refresh-window 08501BC4h *** stack: show *** stack: show *** stack: show *** stack: red/_function/call 085016B4h F7F0E884h *** stack: red/interpreter/eval-code 085016B4h F541CBA8h F541CBA8h false 00000000h 00000000h F3C18D38h *** stack: red/interpreter/eval-expression F541CB98h F541CBA8h false false false *** stack: red/interpreter/eval 085016A4h true *** stack: red/natives/if* false *** stack: red/interpreter/eval-arguments F3C18078h F541C984h F541C984h 00000000h 00000000h *** stack: red/interpreter/eval-code F3C18078h F541C954h F541C984h false 00000000h 00000000h F3C18078h *** stack: red/interpreter/eval-expression F541C954h F541C984h false false false *** stack: red/interpreter/eval 08501664h true *** stack: red/natives/either* false *** stack: red/interpreter/eval-arguments F3C18A78h F541B634h F541B634h 00000000h 00000000h *** stack: red/interpreter/eval-code F3C18A78h F541B604h F541B634h false 00000000h 00000000h F3C18A78h *** stack: red/interpreter/eval-expression F541B604h F541B634h false false false *** stack: red/interpreter/eval 08501634h true *** stack: red/natives/if* false *** stack: red/interpreter/eval-arguments F3C18078h F541B1D4h F541B1D4h 00000000h 00000000h *** stack: red/interpreter/eval-code F3C18078h F541B1A4h F541B1D4h false 00000000h 00000000h F3C18078h *** stack: red/interpreter/eval-expression F541B1A4h F541B1D4h false false false *** stack: red/interpreter/eval F541B0F0h true *** stack: red/interpreter/eval-function F541B098h F541B0F0h *** stack: red/_function/call F541B098h F7EF4F48h *** stack: red/object/fire-on-set 08501544h F3B58898h 08501584h 08501574h *** stack: red/object/eval-path 08501544h F3B58898h 08501574h F3B58574h false *** stack: red/actions/eval-path 08501544h F3B58898h 08501574h F3B58574h false *** stack: red/interpreter/eval-path F3B58898h F3B58594h F3B58684h true true false false *** stack: red/interpreter/eval-expression F3B58594h F3B58684h false false false *** stack: red/interpreter/eval F3B58400h true *** stack: red/interpreter/eval-function 08501514h F3B58400h *** stack: red/_function/call 08501514h F7F0E884h *** stack: red/interpreter/eval-code 08501514h F540FCBCh F540FCBCh false 00000000h 00000000h F3C20308h *** stack: red/interpreter/eval-expression F540FC9Ch F540FCBCh false false false *** stack: red/interpreter/eval F540FC28h true *** stack: red/interpreter/eval-function 085014E4h F540FC28h *** stack: red/_function/call 085014E4h F7EF9984h
no-border in GTK. In my case this code still makes fields with borders:view [field no-border field no-border]
panel-face/size: 200x200.red:GTK branch. I think that all what you mentionned could be fixed by small PR. My original goal was only to propose a first useable version to be improved by community since., as mentionned by @dockimbel very often, the red:GTK branch development is a community effort. Now I think it is time to enlarge the community….GTK tag in red/red repo for GTK-related bugs/prs?modules/view/backends/gtk3 folder the related reds files (main ones are gui.reds, gtk.reds, events.reds and handlers.reds). User Error: Bad face in screen pane! is a font problem, see http://rebol.com/article/0545.htmlroot@antix1:/home/demo/red# echo 'Rebol[] do/args %red.r "-r %environment/console/CLI/console.red"' | rebol +q -s bash: rebol: command not found
ls shows the REBOL executable is there. I ran a ./rebol and can see it is the core version REBOL/Core 2.7.8.4.3 (6-Jan-2011)'Rebol[] do/args %red.r "-r %environment/console/CLI/console.red"' | ./rebol +q -s
'Rebol[] do/args %red.r "-r %environment/console/CLI/console.red"' | rebol +q -s
./reboldo/args %red.r "-r %environment/console/CLI/console.red" in Rebol console. That's how I do it../rebol. What happens?call were paid features, etc, etc, ...GTK: [like that](https://github.com/red/red/issues/4039)Red [File: %a.red Needs: 'View] print "s"
echo 'Rebol[] do/args %~/red-github/red.r "-d -c %a.red"' | ~/rebol +q -sTarget: Linux
Compiling to native code...
*** Compilation Error: unknown path root variable: red/collector
*** in file: %/work/a.red
*** at line: 206
*** near: [
red/collector/active?: true
get-event-type: func [
evt [red-event!]
return: [cell!]
] [
as cell! switch evt/type [
EVT_TIME [_time]
EVT_DRAWING [_drawing]
EVT_SCROLL [_scroll]
EVT_LEFT_DOWN [_down]
EVT_LEFT_UP [_up]
EVT_MIDDLE_DOWN [_mid-down]
EVT_MIDDLE_UP [_mid-up]
...master branch...using libRedRT built on 15-Oct-2019/3:06:53+2:00 ...compilation time : 1740 ms Target: Linux Compiling to native code... *** Compilation Error: undefined symbol: red/unicode/utf8-next-char *** in file: %/home/devel/prj/red/gtk/red-github/modules/view/backends/gtk3/text-box.reds *** in function: exec/gui/utf8-to-bytes *** at line: 47 *** near: [unicode/utf8-next-char end]
-c with new libRedRT.-r it's OK.-c compilation. Following code works only with -r, and when compiled with -c -u it does not respond to clicking the button:Red [Needs: 'View] view [ button "test" [print "test"] ]
GTK branch sources with patch from PR 4090.face! has no value or path system/view/debug?: is not valid for none! type errors. Is it possible that console is compiled without view support for GTK branch?>> system/build/config/modules == [] >> print system/build/git branch: "GTK" tag: #v0.6.4 ahead: 1051 date: 28-Oct-2019/9:24:16+01:00 commit: #2fbd3a7fcd696f54ace5560a0f83c83da8d9c7a6 message: "FIX: GTK: compiling error."
$ ~/prj/red/gtk/red-github/console-view GTK VERSION: 3.24.10 --== Red 0.6.4 ==-- Type HELP for starting information. >> probe system/build/date 28-Oct-2019/10:37:45+01:00 == 28-Oct-2019/10:37:45+01:00
panel1: make face! [ type: 'panel contents: [ below text "Panel 1" button "Switch" [ print "1 -> 2" remove find window/pane panel1 append window/pane panel2 ] ] ] panel2: make face! [ type: 'panel contents: [ below text "Panel 2" button "Switch" [ print "2 -> 1" remove find window/pane panel2 append window/pane panel1 ] ] ] window: layout [] append window/pane layout/parent panel1/contents panel1 none layout/parent panel2/contents panel2 none view window
echo 'Rebol[] do/args %~/prj/red/gtk/red-github/red.r "-d -r %~/prj/red/gtk/red-github/environment/console/GUI/gui-console.red"' | ~/prj/red/gtk/rebol +q -s-d switch./rebol -qws red.r -r -d environment/console/GUI/gui-console.red to test it again?$ git log --oneline | head 2fbd3a7fc FIX: GTK: compiling error. f04488cda Merge pull request #4105 from loziniak/GTK 390da1d5b Merge branch 'GTK' into GTK cbd6f8fad Merge pull request #4107 from bitbegin/refactor 6806c931b Merge remote-tracking branch 'origin/GTK' into draw 704353eea FIX: window no need connect `key event` as it be done by `view` 95178e734 FIX: change face offset issues 4915e8ff1 FIX: slider data 2228bdbd0 CHORE: whitespace cleaning c24d0f483 FEAT: field's no-border flag
gui-console?gui-console compiled from GTK branch and the binary provided by @bitbegin and I have the same results: it works for @bitbegin binary and it fails for the binary compiled from GTK branch … @bitbegin are you sure to compile the binary from the last GTK branch taking into account the last commits?4940004 for @bitbegin’s binary and 4942028 for latest GTK (compiled in debug mode).easy-VID-rt.redin the makedoc repo of @toomasv is not working anymore. It was one of my favorite red tests. As mentioned before, styles/shrinkable.red in the learning repo of @toomasv is not working properly. Red [needs: view]
renderdata: function [] [
print[" renderdata: ... "]
o: copy []
foreach r sampledata [
rr: copy/deep r
append o rejoin [
pad rr/1 10
pad rr/2 10
pad rr/3 10
]
]
o
]
sampledata: [["one" "fn1" "100"] ["two" "fn2" "200"] ["three" "fn3" "300"]]
fndata: ["fn1" "fn2" "fn3"]
amsetting: true
view [
Title "test"
across
text "tl" 20x20 right
tl: text-list data renderdata
on-change[
amsetting: false
print["tl on-change triggered..."]
row: pick sampledata tl/selected
tf/text: row/1
td/selected: index? find fndata row/2
amsetting: true
]
return
text "tf" 20x20 right
tf: field
on-change[
if amsetting [
print["tf on-change triggered..."]
x: tl/selected
sampledata/:x/1: tf/text
tl/data: renderdata
tl/selected: x
]
]
return
text "td" 20x20 right
td: drop-down data fndata select 1
on-change [
if amsetting [
print["td on-change triggered..."]
x: tl/selected
sampledata/:x/2: td/text
tl/data: renderdata
tl/selected: x
print[ "tl/selected should be: " tl/selected ]
]
]
]FEAT: code refactoring for font and draw) makes all the rich-text examples not working anymore. Hope it helps! console-view:view compose [image (draw 10x10 [circle 10x10 5])]
gui-console it shows ok.draw size argument from 10x10 to 20x20, I get a responsive window in console-view also.view compose [image (draw 20x20 [])]
view compose [image (draw 10x10 [])]
view [].rich-text (which is already better but not perfect) and on toomasv/learning/styles/shrinkable.red. :clap: @bitbegin !rich-text ?richtext which is seen with toomasv/makedoc/easy-VID-rt.red and one on toomasv/learning/styles/shrinkable.red. The following is not complete!Red[Needs: View]
view compose/deep [
rich-text 200x200 draw [
text 10x10 (rt1: rtd-layout ["Some^/" b "text^/" /b "here"] rt1/size: 50x80 rt1)
text 100x90 (rt2: rtd-layout [red "Other^/" b "text^/" /b "there"] rt1/size: 50x80 rt2)
pen gold box 90x80 160x180
]
]toomasv/learning/styles/shrinkable.red. Last time, you told me it was easy to fix!view [] second time, don't know why.view [button "abc" field "test"], a button doesn't get a focus. Like about one in five executions.code and community repos were ok) but now a lot of code don’t work properly. You should try these codes! f-box and page-border provides the click event:…..
panel page-size [
origin 0x0
page-border: box with [
size: page-size
draw: compose [pen gray box 0x0 (page-size - 1)]
]
at 0x0 f-box: rich-text page-size white draw []
on-down [
parse face/draw [some [
bx: 'box pair! pair! if (within? event/offset bx/2 sz: bx/3 - bx/2) (
code: select first find bx object! 'text
either event/ctrl? [show-edit-box code sz][show-example code]
)
| skip
]]
]
]
….easy-VID-rt.red is really slow now to show the window….gui-console fails because of eol (I guess).to-image couple months ago. easy-VID-rt.red work noweasy-VID-rt.red that I mentionned last time.easy-VID-rt.red working ?draw box still need to be fixedview [] in *console-view* on Linux/GTK, the process takes 100% of processor. When I ran *gui-console* before updating to last changes, without any script it took 30% of processor (Core 2 Duo 1.8 GHz). When I entered view [] in *gui-console*, processor dropped to 0%, but when I closed window created by script, went back to 30%. Now, after compiling with latest sources, *gui-console* is also at 100% from the start. Can anybody reproduce that?renderdata: function [] [
print[" renderdata: ... "]
o: copy []
foreach r sampledata [
rr: copy/deep r
append o rejoin [
pad rr/1 10
pad rr/2 10
pad rr/3 10
]
]
o
]
sampledata: [["one" "fn1" "100"] ["two" "fn2" "200"] ["three" "fn3" "300"]]
fndata: ["fn1" "fn2" "fn3"]
amsetting: true
view [
Title "test"
across
text "tl" 20x20 right
tl: text-list data renderdata
on-change[
amsetting: false
print["tl on-change triggered..."]
row: pick sampledata tl/selected
tf/text: copy row/1
td/selected: index? find fndata row/2
amsetting: true
]
return
text "tf" 20x20 right
tf: field
on-change[
if amsetting [
print["tf on-change triggered..."]
x: tl/selected
sampledata/:x/1: copy tf/text
tl/data: renderdata
tl/selected: x
]
]
return
text "td" 20x20 right
td: drop-down data fndata select 1
on-change [
if amsetting [
print["td on-change triggered..."]
x: tl/selected
sampledata/:x/2: copy td/text
tl/data: renderdata
tl/selected: x
print[ "tl/selected should be: " tl/selected ]
]
]
]code/Showcase/picosheet.red that was working… Good news, code/Showcase/livecode.red has been fixed with your last developement :thumbsup: (wallet2_r:14959): GdkPixbuf-CRITICAL **: 19:05:55.219: gdk_pixbuf_scale_simple: assertion 'GDK_IS_PIXBUF (src)' failed (wallet2_r:14959): GdkPixbuf-CRITICAL **: 19:05:55.219: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed (wallet2_r:14959): GdkPixbuf-CRITICAL **: 19:05:55.219: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed (wallet2_r:14959): GdkPixbuf-CRITICAL **: 19:05:55.219: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed (wallet2_r:14959): GLib-GObject-CRITICAL **: 19:05:55.219: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (wallet2_r:14959): Gtk-WARNING **: 19:05:55.219: drawing failure for widget 'GtkLayout': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (wallet2_r:14959): Gtk-WARNING **: 19:05:55.219: drawing failure for widget 'GtkLayout': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (wallet2_r:14959): Gtk-WARNING **: 19:05:55.219: drawing failure for widget 'GtkLayout': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (wallet2_r:14959): Gtk-WARNING **: 19:05:55.220: drawing failure for widget 'GtkLayout': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (wallet2_r:14959): Gtk-WARNING **: 19:05:55.220: drawing failure for widget 'GtkBox': invalid value (typically too big) for the size of the input (surface, pattern, etc.) (wallet2_r:14959): Gtk-WARNING **: 19:05:55.220: drawing failure for widget 'GtkWindow': invalid value (typically too big) for the size of the input (surface, pattern, etc.)
-r switch.system/view/debug?: true and every set of GTK errors has an accompanying debug line face> type: panel event> type: drawing offset: none key: none flags: []Red [Needs: 'View] probe draw-commands: reduce [ 'image load %img.png 10x10 30x30 ] view compose/deep/only [ base draw (draw-commands) ]
%img.png is missing, you get errors. But not from Red saying that file not found, but from GTK saying some strange things about pixbufs. I think there should be some error checking when an image cannot be loaded.*** Access Error: cannot open: %img.png *** Where: decode *** Stack: probe load
debug line is a bugload image issue have been fixedCompiling to native code...
*** Warning: OS_TYPE macro in R/S is redefined
*** Compilation Error: invalid path value: image/extract-data
*** in file: %/c/dev/greggirwin/red/tests/android/datatypes/binary.reds
*** in function: red/binary/to
*** at line: 1
*** near: [1030x7
proto: image/extract-data as red-image! spec EXTRACT_ARGB
]musl as libc won’t work with Red. That means Alpine Linux, OpenWRT and derivates like TurrisOS and probably other distros. That may be a bit unfortunate for your use case as musl is heavily used in embedded world for its small size. BSo you need to either choose different distro or wait until Red supports musl.on-wheel [print type? event/picked] I get float and in Windows (Wine) I get integer. Does it mean it needs fixing?text that is on the pane, pane's event handler is not executed. Unlike in Windows.float!? Scroll is not supported – what do you mean? Not supported by Red? Not supported by GTK?scroll featureon-wheel handler.view [panel red on-wheel [probe event/picked]]
Red [Needs: 'View] menu-button-style: [ default-actor: on-down template: [type: 'base size: 100x100] ] styles: reduce ['menu-button menu-button-style] window: layout/styles [ panel [ below menu-button "1" [print "1"] ;prints "1" menu-button "22" [print "22"] ;prints "22^/1" menu-button "333" [print "333"] ;prints "333^/22^/1" ] ] styles view window
space 0x0 gives errors also on current build:Red [Needs: 'View] menu-button-style: [ default-actor: on-down template: [type: 'base size: 100x100] ] styles: reduce ['menu-button menu-button-style] window: layout/styles [ panel [ space 0x0 ;-- adding this makes the code misbehave ;space 1x1 ;-- this is ok in recent build, but fails on commit f8d2a3629 below menu-button "1" [print "1"] menu-button "22" [print "22"] menu-button "333" [print "333"] ] ] styles view window
https://doc.red-lang.org/en/view.html#_panel to check if the event be supportedwindows, the 333 layer is on top of all these layers, so the other layers will not response click event. with GTK backend, the top layer will check if it's background layer and then resend the click event.https://github.com/red/red/pull/4185 will fix the issuewheel event is officially supported, so I base on that. It's good that it's finally settled what type on-wheel's picked will return. Is Windows 7 supported by Red?wheel event is officially supported, so I base on that. *** Runtime error 98: assertion failed?Red [Needs: 'View] a: make face! [ type: 'base color: red size: 20x20 showw: function [ parent [object!] offs [pair!] ] [ self/offset: offs self/parent: parent append parent/pane self ] ] view [ panel 500x500 [ button "show a" [a/showw face/parent 30x30] ] ]
*** Runtime Error 98: assertion failed *** in file: XXXred/gtk/red-github/runtime/datatypes/object.reds *** at line: 384 *** *** stack: red/object/fire-on-set 00000062h 080951FEh 00000000h FFE69840h *** stack: red/object/fire-on-set F54FBFB0h 091DCF94h 091E43E4h 091E43D4h *** stack: red/object/fire-on-set* 091DDF24h 091DCF94h *** stack: ctx||458~showw F7EE3C8Ch *** stack: red/_function/call 091E43A4h F7EE3C8Ch *** stack: red/interpreter/eval-code 091E43A4h F531C788h F531C788h false F531C758h F531C7B0h F54FA000h *** stack: red/interpreter/eval-path F531C7B0h F531C768h F531C788h false false false false *** stack: red/interpreter/eval-expression F531C768h F531C788h false false false *** stack: red/interpreter/eval F531C6F0h true *** stack: red/interpreter/eval-function 091E4374h F531C6F0h *** stack: red/_function/call 091E4374h F7EE4428h *** stack: red/interpreter/eval-code 091E4374h F5284A38h F5284A38h false 00000000h 00000000h 091E42D4h *** stack: red/interpreter/eval-expression F5284A18h F5284A38h false false false *** stack: red/interpreter/eval 091E4364h true *** stack: red/natives/do* false -1 -1 -1 *** stack: red/interpreter/eval-arguments F54F94C0h F52849F0h F52849F0h 00000000h 00000000h *** stack: red/interpreter/eval-code F54F94C0h F52849E0h F52849F0h false 00000000h 00000000h F54F94C0h *** stack: red/interpreter/eval-expression F52849E0h F52849F0h false false false *** stack: red/interpreter/eval 091E4344h true *** stack: red/natives/try* true 0 *** stack: do-safe *** stack: do-actor *** stack: ctx||403~awake F7EEFC68h *** stack: gui/make-event 093A7100h 0 9 *** stack: gui/button-clicked 093A7100h 093A7100h