embedded wingets on cloned window's input behaving strangely

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

ID:2767023

Feb 7 2022, 3:14 am

Ter13

Resolved

Using an embedded winget in the form [[parent.control.parameter]] didn't work correctly and would especially fail in cloned windows.

BYOND Version:	514
Operating System:	Windows 10 Pro 64-bit
Web Browser:	Chrome 97.0.4692.99
Applies to:	Dream Seeker

Status:

Resolved (514.1579)

This issue has been resolved.

This is confirmed a bug on 514.1578.

I have a main window set up with an output, input, and a button that is rigged to call the command of the input with the current text of the input, then clear the input's text field. This is all done with embedded wingets inside of a client winset command.

It all works fine in the main window. But once I clone that window, no matter what's typed into the input element, the embedded winget doesn't grab any text, even though the embedded winget for the command works just fine.

You can scope out my test case here

Type something into the main window's input, then press the send button. Then type something into the cloned window's input and press the send button. Why the difference?

Feb 7 2022, 1:21 pm
Lummox JR	Lummox JR resolved issue with message: Using an embedded winget in the form [[parent.control.parameter]] didn't work correctly and would especially fail in cloned windows.