This is not a bug, I just do not understand how to replace the default sendButtonBuilder about dash_chat

[fayeed]

@SushiRoll53 Its really simple you create a function that returns a widget and the function you see a parameter is actually the onSend function you passed to the Dashchat.

Here's an example:

Function sendButtonBuilder(Function onSend) {
  return IconButton(
     icon: Icon(
       Icons.send,
       color: Colors.white  
     ),
     onPress: onSend
  );
}

// Your dashchat code
Dashchat(
  sendButtonBuilder: sendButtonBuilder(),
)

[PolymathWhiz]

One way i'll suggest is to change it from the core code to fit what you want

[PolymathWhiz]

@SushiRoll53 Its really simple you create a function that returns a widget and the function you see a parameter is actually the onSend function you passed to the Dashchat.

Here's an example:

Function sendButtonBuilder(Function onSend) {
  return IconButton(
     icon: Icon(
       Icons.send,
       color: Colors.white  
     ),
     onPress: onSend
  );
}

// Your dashchat code
Dashchat(
  sendButtonBuilder: sendButtonBuilder(),
)

Much better

[SushiRoll53]

Cool it seems easy, I tried as the following, I had to make some modifications so I was able to run a test

sendButtonBuilder(Function onSend) {
  return IconButton(
     icon: Icon(
       Icons.send,
       color: Colors.white  
     ),
     onPress: onSend
  );
}

Dashchat(
  sendButtonBuilder: sendButtonBuilder(onSend),
)

and the icon does not get replace it.
Do you have another way I can try to solve this?

[SushiRoll53]

It's me again, for the record I managed to solve with some help, here it is how I could fix it

sendButtonBuilder(Function onSend) {
  return IconButton(
     icon: Icon(
       Icons.send,
       color: Colors.white  
     ),
     onPressed: onSend
  );
}

Dashchat(
  sendButtonBuilder: (function) {
    sendButtonBuilder(function)
  },
)

I'm gonna close it, thank you for your responses.

[kornha]

Reopening. This does not work, the onSend method does not get triggered. As this is not expected behavior, this is a bug.