Help request: onchange of MultiLineEntry is never called

[danielRi]

Hi,

I´m fairly new to Nim and Uing. I started creating a text field, but I cant figure out why the onchanged function is never called, when I type something:

❯ nimble list -i      
nim  [(version: 2.0.8, checksum: 46333e8f4bda41dd6d3852a3f5fa4975b96b66a2)]
uing  [(version: 0.8.1, checksum: 92408d73d6e2e49e10c8d8d58aaaca63d0e85489)]

import uing

var 
  mainwin: Window
  mlEntry*: MultilineEntry
  mainhbox: Box

proc onChange(sender: MultilineEntry)

proc main =
  mainwin = newWindow("Parser", 640, 480)
  mlEntry = newMultilineEntry(onChange)
  mainhbox = newHorizontalBox()

  mainhbox.add(mlEntry)
  mainwin.child=mainhbox
  
  echo "starting..." # I see this output
  
  show mainwin
  mainLoop()

proc onChange(sender: MultilineEntry) =
  echo sender.text # I would expect this output when I type, but nothing happens

init()
main()

When I run this with

nimble run

I get a window with a multi line edit, everything looks good, however if I type in the text field, I cant see the echo output in the onChanged procedure (I do see the "starting..." output however). Im on a m1 macbook with macOs 14.5

Thanks a lot for any help!

[danielRi]

Edit: If I add this line after I create the MultilineEntry:

mlEntry.onchanged = onChange

Then my callback gets called, however there is an error showing:

vehicle_parser_nim(96198,0x201018240) malloc: *** error for object 0x109757068: pointer being freed was not allocated
vehicle_parser_nim(96198,0x201018240) malloc: *** set a breakpoint in malloc_error_break to debug

[danielRi]

another update:

I changed the code in the text proc in the uing.nim file. If I remove the free result line, it works. But its probably not what I want.  😄

proc text*(e: MultilineEntry): string = 
  ## Returns the multi line entry's text.
  ## 
  ## :e: MultilineEntry instance
  
  result = $multilineEntryText(e.impl)
  free result

[neroist]

Does HEAD not work either? I believe I fixed the issue "pointer being freed was not allocated" already. Though I do need to look into the first one you mentioned.

[neroist]

Please try using the most recent release 0.8.2! Both of these issues should be fixed.

[danielRi]

Hey,
Thanks a lot for your time!
I upgraded uing to 0.8.2 and everything works as expected, like a charm.
Thanks again!

[neroist]

🩷