Author Topic: Features Wishlist (Read 694651 times)

Darl181 · « **Reply #975 on:** July 20, 2010, 02:36:23 pm »

Quote from: Magic Banana on July 19, 2010, 06:44:35 pm

Maybe have a number (not sure if all of them are taken already)

Aren't there some tokens left in the VARS menu?
The Window ones, for example.

I may be really behind on the poll thing ↑↑↑, but it would be nice if you could also write to OS vars. That way, a sprite editor could store the hex code in an OS string or a picture editor save to an OS picture.
Just a thought.

Oh, and I remembered this morning about the increase in sound quality, recompiled my old sound program, and inadvertently put the headphone in my ear. And got blasted by the volume.
Might a volume control be possible?

calcdude84se · « **Reply #976 on:** July 20, 2010, 03:08:32 pm »

The poll option is OS Var support, not just reading. If you're talking about "reading from archive", then no. There are very few programs that write directly to archive.

DJ Omnimaga · « **Reply #977 on:** July 20, 2010, 04:03:34 pm »

Darl181 was the sound really that loud? Was it from a real calc? Because if I remember correctly, even with really good headphones, sound coming out of the calc link port was usually very low. You had to use loud speakers to get decent volume.

Quigibo · « **Reply #978 on:** July 20, 2010, 10:25:47 pm »

I've finished the popular option "OS var support". You are now able to Create, Read, Modify, or Delete pretty much any OS variable you can think of, even obscure ones like GDBs. The only complication right now is that it is very difficult to read or write to any structure that uses floating points like Reals, Lists, and Matrices. I will probably have to add floating point conversion commands to simplify this, hopefully it will be in the next version, I'm not sure yet. But for now, strings, pictures, programs, and appvars are extremely useful as external variables. The best part is, there is no new syntax, you use the same commands you're already used to and plus the addition of DelVar which is intuitive to use.

I am also half way done with linking and I'm just about to start working on reading from archive, just have to think of the simplest possible way to approach it so its easy to use and not very confusing. It will probably consist of a CopyToRam command and a ReadByte command for the actual reading.

DJ Omnimaga · « **Reply #979 on:** July 20, 2010, 10:30:56 pm »

Oooh nice to hear

. Good luck with real/list/matrices. I think for now just string and Ans support would be very good, though, for making some libraries. I hope you can figure out something easy for the other features.

calcdude84se · « **Reply #980 on:** July 20, 2010, 10:49:37 pm »

I'll bump this, as it relates to reading directly from archive.
Can we have a command to create a temporary RAM copy of a variable in RAM?
Maybe something like token("string"), where the command takes a string that is the name of the variable and returns a pointer to the data of the temp var, or 0 if failed (not enough RAM, variable doesn't exist, etc.)

calcdude84se · « **Reply #981 on:** July 21, 2010, 06:51:00 pm »

This is more like a feature retainment request than a feature request, but you could you keep the single-argument Output(?
Even if 2-argument with constants is automatically optimized, it could still be useful with certain expressions involving variables.
While I can't think of a good example off the top of my head, I'm sure one exists

calcdude84se · « **Reply #982 on:** July 22, 2010, 09:41:42 am »

And, bumping another feature request. Can there be versions of sin( and cos( that support 8.8 FP?

ztrumpet · « **Reply #983 on:** July 22, 2010, 11:18:12 am »

Quote from: calcdude84se on July 21, 2010, 06:51:00 pm

This is more like a feature retainment request than a feature request, but you could you keep the single-argument Output(?
Even if 2-argument with constants is automatically optimized, it could still be useful with certain expressions involving variables.
While I can't think of a good example off the top of my head, I'm sure one exists

I'd like to see the one argument Output( as well. I use it a lot, and it should be easy to keep. Thanks!

Quote from: Quigibo on July 13, 2010, 09:11:16 pm

3 level grayscale compact masking for 8x8 sprites. I used this in Pyoro, it basically allows you to use the unused bit combination as an extra transparency layer so you can have automatic grayscale masking without needing an extra mask layer. 00=transparent 01=white 10=gray 11=black
16x16 aligned sprite drawing. Its a super fast and small way to draw 16x16 sprites when they're aligned horizontally and also using a more convenient array for the sprite data than trying to make 4 8x8 sprites.
Unclipped unsafe 8x8 sprite drawing. Speeds up sprite drawing significantly for sprites that are always drawn completely on-screen for applications where speed really matters. But it would crash/corrupt data for sprites drawn partly or fully off-screen
Would anyone be interested in any of these? I would probably use the Plot1() - Plot3() tokens.

I would like all three of these. They all sound useful, and I really want the first one.

nemo · « **Reply #984 on:** July 22, 2010, 09:28:52 pm »

i second ztrumpet. the 3 sprite features he quoted would help so much. mainly the last one, but those would definitely be something to look forward to.

Quigibo · « **Reply #985 on:** July 22, 2010, 10:56:56 pm »

Well the first one for sure I will add since it can be used for monochrome masking as well, but I'm still not so sure about the other ones since the 2nd one can be written in Axe and the 3rd one seems like a bad idea. They won't be a priority right now or in a near release.

I guess I'll keep the single line coordinate method for Output() and Text() just in case. Also, there is no reason to have a separate 8.8 routine for sin because you can do basically the same thing with this: sin(A/256)*2 The only advantage of a separate routine is to use a little bit of the decimal part to get slightly higher accuracy, but its not going to be that much better.

In other news, I've got archive reading completed and I'm rewriting the tutorial about it because there is a lot of new information to learn about, but lucky no new commands.

calcdude84se · « **Reply #986 on:** July 22, 2010, 11:06:39 pm »

Can't wait till Saturday!

Operator overloading seems fun...
And okay for not having extended sin( and cos(, I see what you mean
Keep up the good work!

ztrumpet · « **Reply #987 on:** July 23, 2010, 10:38:58 am »

Quote from: Quigibo on July 22, 2010, 10:56:56 pm

Well the first one for sure I will add...
I guess I'll keep the single line coordinate method for Output() and Text()...
I've got archive reading completed...

Yay!

I wish I was here tomorrow, but it looks like I have to wait an extra week...

Quote from: Quigibo on July 22, 2010, 10:56:56 pm

3rd one seems like a bad idea.

I think the third one is an awesome idea, just make sure to offer plenty of warnings in the readme.

Raylin · « **Reply #988 on:** July 23, 2010, 11:45:17 pm »

Was sprite rotation coming in 0.4.0?

Builderboy · « **Reply #989 on:** July 24, 2010, 01:16:49 am »

Sprite rotation would be extra useful. Rotating by angles other than multiples of 90 might be extremely difficult and slow, but 90 degree rotations, and flipping as well i think would be very useful, and hopefully not to difficult to implement.

Author Topic: Features Wishlist (Read 694651 times)

Darl181

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Quigibo

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

nemo

Re: Features Wishlist

Quigibo

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

Raylin

Re: Features Wishlist

Builderboy

Re: Features Wishlist