Code center > Suggestions
I am back...
PurpleYouko:
There is no difference whatsoever between a circle and an elipse as far as these calculations go.
Like giz said, a circle is simply an elipse with zero ecentricity. Just like a square is a rectangle with 4 equal sides
Griz:
--- Quote ---I menat only that I agree with it for the case of a circle. An ellipse is less self-obvious to me. Now that I think about it a little more, I think certain ellipses would work this way and some wouldn't...
--- End quote ---
???
in what way?
an ellipse is a pretty simple/basic representation of a specific 2D spatial relationship.
what 'transformation' could you apply to one that you could not apply to another?
if you come up with it ...
please share, as it will be news to me ...
and I'm always interested in amending/adding to ...
what I think I already know.
Numsgil:
Again, geometry isn't my strong suit.
PurpleYouko:
Just think of a circle as plotting
X(centre) + X radius * sin(angle) against Y(centre) + Y radius * cos(angle)
All you have to do is apply a different radius in the X and Y directions to get an elipse
You could even use a circular (eliptical) coordinate system if you like. Might be a bit complex though.
Griz:
is there really a need to go elliptical?
I understand we want to utilize as much of the screen as possible but ...
how about ...
using as large a circular field as will fit the vertical dimensions of the screen ...
and using the remainder, be it on the left, right or both ...
for the various buttons/sliders for the controls one might want to access.
also ... one could call up something like a graph or robot info ...
and not have them be on top of the field blocking the 'action'.
just a thought ....
as it's seems coding bot placement/movement/repopulating ...
will be less complicated using a simple circle than trying to compensate
for an elliptical field ... ie ... calculating out of bounds/repop, etc.
if you can visulize it ...
using an elliptical field vs a circular one ...
really doesn't utilize that much more of the retangular screen ...
so it becomes a matter of priorities again ...
is the small sacrifice in area worth the less complicated coding ...
or not?
just tossing our ideas for consideration before Nums/PY/whoever
wades into the code. ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version