Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text Input Bars for Geyser Elements #3809

Closed
Symple85 opened this issue May 19, 2020 · 5 comments
Closed

Text Input Bars for Geyser Elements #3809

Symple85 opened this issue May 19, 2020 · 5 comments

Comments

@Symple85
Copy link

Symple85 commented May 19, 2020

Description of requested feature:

The addition of an input bar feature for Geyser elements would be great!

Reasons for adding feature:

  1. Create an input bar that would be tethered to a function upon creation.

  2. Input from the text bar would be sent to the function.

3.Basicly the functionality of clickcallback but with flexibility.

@vadi2
Copy link
Member

vadi2 commented May 19, 2020

Hm you listed how you'd like it to work, but where are the reasons :)

@demonnic
Copy link
Member

easy chat window inputs, to allow for text input in a miniconsole's input line to be sent to a function which then sends it to the appropriate channel automatically. EMCO inside a userwindow becomes usable as a chat window without needing to go to the Mudlet main window to respond to a message, for instance.

Or an input line for a configuration window, with all the information input into the line attached to that userwindow being parsed by the function to set values in a configuration table.

Just as a couple examples which have come up in discussions I've had with people recently.

@SlySven
Copy link
Member

SlySven commented May 21, 2020

What happens to execution whilst the whole application is waiting for the user to enter something into that entry widget?

I guess it might be do able if the text input was tied to/provided by a sysEvent ... 💭

@demonnic
Copy link
Member

I envision it working like a label clickcallback, except instead of when clicked it's when you hit enter to send the input and it sends the text being input as the argument to the function. Perhaps if no function is assigned it runs through the alias engine as normal?

@vadi2
Copy link
Member

vadi2 commented Sep 1, 2020

Duplicate of #1897, and we have a solution for testing available at #4055 (comment).

@vadi2 vadi2 closed this as completed Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants