#CELROT.POC
8 messages in this thread
OK David heres my opinion I promised you on your CELROT.POC,
I am very happy with it and think it's great for doing various maps for 3DS. I
do have a few nice features I think you could add if you like.
1. The ability to place the cels over a series of frames like CELSPRAY.POC and
have at the same time the cels rotating.
2. The ability to draw a RubLine first and then have the cels placed evenly
along the line with the cel rotation option.
Oh, I almost forgot do you have a POCO routine that can access all the POCOs
you have from one menu (like "int Qscroll"). This POCO would be like the PXP
and the KXP IPAS Loader for 3DS and would be placed in the resource directory
then when you ran this you would get a long list of all of the POCOs you had in
the \ani directory? If you have something like this I would love to see it. I
have way to many great POCOs that have to be loaded manually. If you don't
have something like this how would I use the "int Qscroll" command in a POCO?
The only knowledge I have of programming in POCO comes from looking at other
POCOs to see how each command works.
You are going to upload more POCOs right?
/* I am very happy with it and think it's great for doing various maps for 3DS.
I do have a few nice features I think you could add if you like. */
Thanks, Mark. And thanks for the suggestions!
/* 1. The ability to place the cels over a series of frames like CELSPRAY.POC
and have at the same time the cels rotating. */
This shouldn't be too hard. Great idea.
/* 2. The ability to draw a RubLine first and then have the cels placed evenly
along the line with the cel rotation option. */
Oooh. Cool. But this would only be for a uniformly divided line segment?
/* Oh, I almost forgot do you have a POCO routine that can access all the POCOs
you have from one menu (like "int Qscroll"). This POCO would be like the PXP
and the KXP IPAS Loader for 3DS and would be placed in the resource directory
then when you ran this you would get a long list of all of the POCOs you had in
the \ani directory? If you have something like this I would love to see it. */
I don't (since I usually just use the U parameter (Use in POCO pull down) to
load POCOs anyway. It could be done, but it would be redundant to the existing
USE option. What types of features would you want that go beyond the current
USE feature?
/* You are going to upload more POCOs right? */
Sure, as time allows. 🙂 -dave
<< RubLine feature – But this would only be for a uniformly divided segment? >>
Yes
<< What features would you want that go beyond the USE command? >>
1. Speed would be one when I try to load a POCO I don't want to scroll through
the list of subdirectorys.
2. It would be nice to use the "int Qscroll" command because you can have a
short description of each POCO you have instead of guessing from a character
name.
Mark Yankee
/* 1. Speed would be one when I try to load a POCO I don't want to scroll
through the list of subdirectorys. */
Okay.
/* 2. It would be nice to use the "int Qscroll" command because you can have a
short description of each POCO you have instead of guessing from a character
name. */
You realize that every time you added a POCO routine, you would have to add
code then to the POCO routine that scrolls it with a description…? If this is
no problem, I suppose it wouldn't be bad, but otherwise, by nature oif Qscroll,
the code would hjave to be updated to have descriptions, and you would still
have to "scroll" to get down to the ones at the end. 🙂 -dave
<< every time you added a POCO routine, you would have to add code to the POCO
routine that scrolls >>
Yes, I agree this would be a little bit of a pain but I think it would be worth
the description.
Mark Yankee
Just tried CELROT. Neat! And it's fun!
I didn't think I would have a use for it when I first read the description. But
after trying it, and seeing your examples, I got some ideas I'm going to try.
Your examples really show the potential!
Regarding a menu to select from all POCOs.
A big portion of the addendum to the POCO manual is dedicated to functions for
producing custom panel-menus (E.g., GetPhysicalScreen, MenuText, — page 12).
I've never tried them (maybe I can tonight), have you?
Mark:
While you wait for Dave's program to do the "rotating cel along a path," here
are hard ways <:)> to do it (over several frames):
1. Use Optics to create a flic of the CEL rotating.
2. Use Cel/Clip to place the result in an animated-cel.
3.
A. Evenly spaced on a straight line:
Use Cel/Paste FROM the Main Screen. Then drag the Cel
to the desired endpoint and click.
B. Not evenly spaced and/or along an arbitrary path:
Method 1: (allows you to enter/edit/save/load path):
Use Optics, enter path with a mouse or with POCO
(see 3-OPT.POC for example of how to do it with POCO).
Method 2: (manual placement, path cannot be reused)
Use Sprite (in the Animated Cel panel).
If you want more details let me know.
Ed K
/* Just tried CELROT. Neat! And it's fun! */
Yeah, I sat for a 1/2 hour playing with it when I first wrote it… found some
bizarre patterns were achievable based on rotation angle. It gets even crazier
at higher resolutions with strangle cels.
/* try. Your examples really show the potential! */
I'm glad to hear it. I wasn't sure if I was wasting people's download time by
including sample uses or not.
/* producing custom panel-menus (E.g., GetPhysicalScreen, MenuText, — page
12). I've never tried them (maybe I can tonight), have you? */
I haven't yet. I've read through it, but have probably only experimented with
about 1/3 of the addendum functions. The PDR library was especially useful.
Until this arrived, we had no way of working with specific file formats unless
we relied on internal menus. This is much cleaner. -dave
Cool!,
Thanks for the info Ed.
Mark Yankee