#PXPs calling PXPs
4 messages in this thread
Is it possible for one IPAS routine (especially a .PXP) to call another as a
subroutine, or even just branch to it? If so, it seems to me that this would
be a very easy way around the 14 PXP limitation — simply write a real small
.PXP that simply displays a list of all other .PXP files in the PROCESSES
directory, allows you to choose one, and then executes it. Voila!
<<Is it possible for one IPAS routine (especially a .PXP) to call another as a
subroutine, or even just branch to it?>>
Interesting concept. I hadn't thought of this. My initial reaction is No, but
let me look around a bit and see what I can come up with.
As I mentioned in the IPAS docs, we've found a much more elegant way to get rid
of the 14 PXP per 3DS.SET limitation in r3. I know that that doesn't help you
much with r2, but rest assured that it's already dealt with.
– G
PS: There's no way to do this in r2 with a pxp that loads pxps.
>>we've found a much more elegant way to get rid of the 14 PXP per 3DS.SET
limitation in r3. I know that that doesn't help you much with r2, but rest
assured that it's already dealt with.<<
Oooh, Gary! I'm pointing my finger. Does this mean you're marked for death?
<G,D &R…FAST>
Sorry, I couldn't resist. Promise I won't do it again, REALLY! (On pain of
death <GGG>)
DT