hello,
why i see in my compilation appear ttt after ex:
new ??? ttt ttt (self: Widget; event: gdk.Event): bool
I knew CC: stdlib_assertions.nim
thank you
thank you
Hint: used config file '/home/soleil/.choosenim/toolchains/nim-1.2.6/config/nim.cfg' [Conf] Hint: system [Processing] Hint: repr_v2 [Processing] Hint: widestrs [Processing] Hint: io [Processing] Hint: macro01 [Processing]
BUILD TEST macro01.nim-> not compile
[soleil@HPZ800 NimScreen]$ ./compile.sh TEST macro01.nim Hint: used config file '/home/soleil/.choosenim/toolchains/nim-1.2.6/config/nim.cfg' [Conf] Hint: system [Processing] Hint: repr_v2 [Processing] Hint: widestrs [Processing] Hint: io [Processing] Hint: macro01 [Processing] Hint: macros [Processing] CC: stdlib_io.nim CC: stdlib_system.nim CC: macro01.nim Hint: [Link] Hint: 13624 LOC; 0.516 sec; 18.027MiB peakmem; Debug build; proj: /home/soleil/NimScreen/macro01.nim; out: /home/soleil/NimScreen/macro01 [SuccessX] Hint: /home/soleil/NimScreen/macro01 [Exec] ok a c Foo x wow hey
BUILD TEST macro01.nim-> macro01 size : 53K
[soleil@HPZ800 NimScreen]$ cd /home/soleil/NimScreen/ [soleil@HPZ800 NimScreen]$ ./compile.sh PROD testVte.nim ttt (self: Widget; event: gdk.Event): bool ttt (self: Terminal; status: int) ttt (self: Terminal; width: int; height: int)
BUILD PROD testVte.nim-> testVte size : 56K
[soleil@HPZ800 NimScreen]$ cd /home/soleil/NimScreen/ [soleil@HPZ800 NimScreen]$ ./compile.sh DEBUG testVte.nim Hint: used config file '/home/soleil/.choosenim/toolchains/nim-1.2.6/config/nim.cfg' [Conf] Hint: system [Processing] Hint: repr_v2 [Processing] Hint: widestrs [Processing] Hint: io [Processing] Hint: testVte [Processing] Hint: gdk [Processing] Hint: gobject [Processing] Hint: glib [Processing] Hint: times [Processing] Hint: strutils [Processing] Hint: parseutils [Processing] Hint: math [Processing] Hint: bitops [Processing] Hint: macros [Processing] Hint: algorithm [Processing] Hint: unicode [Processing] Hint: options [Processing] Hint: typetraits [Processing] Hint: posix [Processing] Hint: gdkpixbuf [Processing] Hint: gio [Processing] Hint: gmodule [Processing] Hint: pango [Processing] Hint: cairo [Processing] Hint: gtk [Processing] Hint: xlib [Processing] Hint: atk [Processing] Hint: sequtils [Processing] Hint: vte [Processing] Hint: strformat [Processing] ttt (self: Widget; event: gdk.Event): bool ttt (self: Terminal; status: int) ttt (self: Terminal; width: int; height: int) CC: stdlib_assertions.nim CC: stdlib_formatfloat.nim CC: stdlib_io.nim CC: stdlib_system.nim CC: ../.nimble/pkgs/gintro-#head/gintro/glib.nim CC: stdlib_parseutils.nim CC: stdlib_unicode.nim CC: stdlib_strutils.nim CC: stdlib_times.nim CC: ../.nimble/pkgs/gintro-#head/gintro/gobject.nim CC: ../.nimble/pkgs/gintro-#head/gintro/cairo.nim CC: ../.nimble/pkgs/gintro-#head/gintro/pango.nim CC: ../.nimble/pkgs/gintro-#head/gintro/gdk.nim CC: ../.nimble/pkgs/gintro-#head/gintro/gtk.nim CC: ../.nimble/pkgs/gintro-#head/gintro/vte.nim CC: stdlib_strformat.nim CC: testVte.nim Hint: [Link] Hint: 180955 LOC; 4.957 sec; 267.805MiB peakmem; Debug build; proj: /home/soleil/NimScreen/testVte.nim; out: /home/soleil/NimScreen/testVte [SuccessX]
ttt (self: Widget; event: gdk.Event): bool
ttt (self: Terminal; status: int)
ttt (self: Terminal; width: int; height: int)
Perhaps a macro in your code or some library it uses is printing these?
echo "ttt ", ahl
Talk to StefanSalewski :-)
I think I found, until version 0.7.7 of GINTRO I had no problem, and putting version 0.8.0 I have problems as i can't mount gtk4 and gtk3 remains 3.24.21 !!!!!
now i have reverted to version 0.7.7
message for #Stefan_Salewski
Yes, the echo "ttt" output is unfortunately a small bug that made it into release 0.8.0.
It is only debugging output for some invoked macros, so please ignore it. Unfortunately we have only 20 releases left up to 1.0, so I can not make a new release for each tiny bug. I may push fixes to github without making releases, but then people would to do a "nimble install gintro@#head" what they generally not do.
I can not really understand your comment
mount gtk4 and gtk3 remains 3.24.21
we had release 0.7.8 and 0.7.9 before, and before current 0.8.0 there was a long testing period using nimble install gintro@#head. Next release 0.8.1 will add GList proc parameter support as noted in the readme, I am working on it, but it will take some time. Of course if there should be serious bugs in 0.8.0 then I will release a 0.8.1 soon and wast one more release number.
Next time please do not pollute this forum with such unimportant noise, we have the github gintro issue tracker for that.
Admins, I would suggest deleting this whole thread, it is really only noise.
Next time please do not pollute this forum with such unimportant noise, we have the github gintro issue tracker for that.
It appears that the OP didn't know that it was a gintro issue until well into the thread.
error: and gintro 8: just recompil
other ttt !!!
this extract:
(coln_2 , renderer_2) = mTreeViewColEdit("NOM" , col_nom, 30 , color_data)
connect(renderer_2, "edited", p_UpdRowData , coln_2)
discard gSFLine.appendColumn(coln_2)/home/soleil/NIMTEST/MYGTK/biggtk.nim(312, 10) template/generic instantiation of `connect` from here
/home/soleil/.choosenim/toolchains/nim-1.2.6/lib/core/macros.nim(567, 27) Error: type mismatch: got <CellRendererText, proc (pRenderer: CellRendererText, pPath: cstring, pNewText: cstring, pColumn: TreeViewColumn), TreeViewColumn>
but expected one of:
proc connect_for_signal_edited1(self: gtk.CellRendererText; p: proc (
self: gtk.CellRendererText; path: string; newText: string; arg: TreeViewColumn);
a: TreeViewColumn): culong
first type mismatch at position: 2
required type for p: proc (self: CellRendererText, path: string, newText: string, arg: TreeViewColumn){.closure.}
but expression 'p_UpdRowData' is of type: proc (pRenderer: CellRendererText, pPath: cstring, pNewText: cstring, pColumn: TreeViewColumn)
expression: connect_for_signal_edited1(renderer_2, p_UpdRowData, coln_2)else : gintro 7.7 this not error
@Stefan_Salewski some explanations: I do not put work in question, nor your publications which besides are excellent, I just wanted to know at the beginning why the information "ttt (self: CellRendererText; path: cstring; newText: cstring)", for example but there is in other identical and which does not beug.
In the example that I provided you, I am writing to you only on the subject of the beug. The connect option on a column does not work, whereas with version 7.7 there is no problem
I worked a lot with gtk C / C ++ I liked this library and this OOP approach is an approach I used on large systems. If I came to Nim-Lang it is because I found more rationality in this language.
Thanks for reporting.
So there is a real issue with version 0.8.0 and not only some unwanted debug message. And with gintro 0.7.7 it still works.
Unfortunately you are not able to provide a full small but complete example code, so it it not easy to find the cause of this error. Seems to be related with GtkTreeView widget, unfortunately one of the more difficult widgets.
All our tests compile fine with v0.8.0 of course. From version 0.7.7 upto 0.8.0 much has happened, totally that was about 100 hours of work. If I remember correctly we did modify the connect macro a bit, can not remember details currently.
Will try to investigate.
OK, I copied your compiler error message into an editor window and read it carefully:
One problem seems to be a mismatch cstring/string. I can remember that we tried to replace a cstring data type that was still necessary in out early listview related code with a plain Nim string, as Nim users generally like using real Nim strings better than cstrings.
So you may try to locate the position of the error in your code and see if you are still using a cstring where you with gintro >= 0.8.0 should use a Nim string.
I think we have updated indeed one of our shipped examples in such a way for 0.8.0, but I can not remember which one it was.
So hopefully this is not a bug put some progression.
OK, I think I found the change in our examples:
$ grep updateRow ~/gintro/examples/gtk3/*
/home/salewski/gintro/examples/gtk3/css_colored_listview.nim:proc updateRow(renderer: CellRendererText; path: string; newText: string; tree: TreeView) =
/home/salewski/gintro/examples/gtk3/css_colored_listview.nim: connect(renderer2, "edited", updateRow, tree)
Above string parameter type is used. But in our luckily still not updated readme we still use cstring:
http://ssalewski.de/gintroreadme.html#_a_simple_listview_example
proc updateRow(renderer: CellRendererText; path: cstring; newText: cstring; tree: TreeView) =
Interesting. I’m still in 0.7.9. It seems I will have to check if my programs still compile 🙂.
Never mind. I appreciate all changes which make the API more “Nimish” and more user friendly. And using string rather than cstring is indeed a good change.
Yes, in principle we should have a carefully update changelog.
The problem is, that all our test cover only a tiny part of all GTK related stuff -- more than 10000 procs and maybe 2000 data types.
HELLO
gintro 0.8.0
gintro # head
c) following the "ttt" problem: b) i was too fast and recompiled all my models and this is where i found the error a)
frankly I blame myself for not having thought of the evolution towards thong grrrrr
Thank you for taking the time to answer me anyway.
Unfortunately we have only 20 releases left up to 1.0, so I can not make a new release for each tiny bug.
Ummm, what?
You do know that two-digit minor-version numbers like 0.10.x, 0.11.x, ..., 0.99.x are possible, right?