Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Rename UIActor to something less confusing
See original GitHub issueContext
The name UIActor causes confusion about the purpose and functionality of the class.
Proposal
Some suggestions have been
- ScreenElement
- ScreenComponent
- etc
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Actor Core Message Handling - NI Community
Perhaps I am missing something, but I thought an actor was a queued message handler? I am debugging a program I wrote using...
Read more >180 Synonyms & Antonyms of CONFUSE - Merriam-Webster
verb ; 2. as in to complicate. to make (something) unclear to the understanding stop confusing the issue with irrelevant facts ; 4....
Read more >SE-0300: Continuations for interfacing async tasks with ...
To clarify: this proposal is entirely agnostic to queues and performs no queue hopping. Absent anything else like actors being involved, ...
Read more >C++ Tutorial for IBM Rational Rhapsody
functions (meaning how to do something), explanations, and details than this ... diagrams opened in the drawing area, you might find it less...
Read more >Rename definition and meaning | Collins English Dictionary
Rename definition: If you rename something, you change its name to a new name. | Meaning, pronunciation, translations and examples.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, I’ll agree with that. The “Actor” portion does confuse the purpose of the “UIActor” and that is to be a fixed thing on the screen for UI purposes.
ScreenElement is less ambiguous and does make more sense, and it would fit into a possibly UI Elements design metaphor. We could also add DomElement wrappers in that as well…
Ill take it up. Thanks