|
5/6
⬜🟨⬜⬜⬜
⬜🟩⬜⬜⬜
⬜⬜⬜⬜⬜
🟩🟩🟩⬜⬜
🟩🟩🟩🟩🟩
It wasn't difficult but I got sidetracked by my choice of starting words. Anyway, I solved it, period.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
This one was easy.
Wordle 291 3/6*
⬛⬛⬛🟨⬛
🟩🟩🟩⬛⬛
🟩🟩🟩🟩🟩
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
No it wasn’t. “easy” is only 4 letters!
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Wordle 291 5/6
⬜⬜⬜⬜⬜
⬜⬜⬜🟨⬜
⬜🟩🟨🟨⬜
⬜🟩🟨🟨⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 291 5/6
⬛⬛🟨⬛⬛
⬛⬛⬛⬛🟩
⬛⬛🟨⬛🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
User controls in UWP and WPF have a top, left, width and height; and an implied angle of zero degrees.
So I can move them around by altering the top, left coordinates with code at run time.
My user controls have "facings": front (top), back (bottom), left, right. I get to "face" them in different directions by rotating them around a center point.
Rotating the controls has NO effect on the original coordinates (though the "visual" rotates), so I have to calculate (matrix transform) the rotated coordinates myself for collision detection etc.; and reference the original coordinates when I want to move.
In effect, I almost wind up working with 2 controls at the same time; with only the center points in common.
My OCD question is: what would you call the "first" user control versus the second, rotated one?
I'm at "actual" and "visual" but not quite satisfied.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Sorry... "Got a programming question?"
|
|
|
|
|
It's a "terminology" question.
Quote: The body of terms used with a particular technical application in a subject of study, profession, etc.
"the terminology of semiotics"
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Hmmm,
Are you referring to 'world' versus 'local' coordinate systems? I think that's the terminology you are looking for.
|
|
|
|
|
They "both" have the same coordinate system. Until the control is rotated, everything corresponds. Once you rotate it, the "visual" no longer corresponds to the coordinates of the "actual"; only code can derive it.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
|
Is the nomenclature for the end user or for you as the implementer? If for you then maybe pure/virtual or absolute/relative works better? If for the end-user then maybe fixed and realitve?
Keep Calm and Carry On
|
|
|
|
|
It's for me; coding. One set of methods works on the actual coordinates; another set "shadows" and translates the visual to the actuals required to move it, etc.
2 names (2 ways) to look at the same object.
But it's also a "pattern" (IMO); so, it would also be useful in discussing UWP and WPF user control animation: what you see is not what gets coded.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Just to add to the confusion: is this 2-D or 3-D?
Software Zen: delete this;
|
|
|
|
|
Object local coordinate space transformations relative to the world/global space use the same terminology in both 2D[^] an 3D[^] API.
But I'm not exactly sure if that's what he's asking. It seems that he wants to name the objects. I think Tom and Jerry are good names.
|
|
|
|
|
Randor wrote: I think Tom and Jerry are good names. I'm a Fred, Barney, Wilma, Betty, Pebbles, BamBam, Dino, Hoppy, and Gazoo man myself.
Software Zen: delete this;
modified 5-Apr-22 21:03pm.
|
|
|
|
|
Sounds like the old joke of the person who had to set his password to 8 characters, so he set it to "BashfulDocDopeyGrumpyHappySleepySneezySnowWhite"
|
|
|
|
|
2D. 3D would involve different classes and methods and not (uwp/wpf) "user controls" per se.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
To be honest, I have no idea what you're talking about so I have no idea how to even suggest an answer.
|
|
|
|
|
If it was me, maybe 'orthogonal' and 'transformed' (or 'rotated')
|
|
|
|
|
I though of a "rotated", but it isn't until it is. It has only potential at the start, unless you start rotated.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Why are you not just working with an 'anchor' and a 'rotation'? That seems like it would be the simplest, unless I'm not understanding something. If the rotation is 0, the rotation is 0, and you don't care, but your nomenclature doesn't change. If the initial positioning can be rotated, and the change is an additional rotation, you I'd go with 'preTransformRotation' and 'postTransformRotation', or something like that.
|
|
|
|
|
Don't know what you mean by "anchor". The controls are moving and can be rotating at the same time.
Besides the "angle", the "visual" corner points also move when you rotate; but the actual corner points don't. You have to calculate the visuals yourself to "see" (in code) what's happening.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Gerry Schmitz wrote: the "visual" corner points also move when you rotate; but the actual corner points don't.
Are you trying to say that the 'bounding box' size doesn't change? If that is the case, the 'anchor' point would be the center of the bounding box, unless you wanted to use another arbitrary position, such as a corner of the box. If that isn't what you mean, you will need to clarify your intent.
|
|
|
|
|
'Straight' and 'Rotated'.
|
|
|
|