• Features Wishlist 5 1
Currently:  

Author Topic: Features Wishlist  (Read 253495 times)

0 Members and 2 Guests are viewing this topic.

SirCmpwn

  • Guest
Re: Features Wishlist
« Reply #285 on: March 21, 2010, 07:15:48 pm »
The ability to draw the back-buffer directly to the LCD
The ability to store the LCD content straight to the back-buffer

A) conj(L3, L6, 768) \ DispGraph      ; Backbuffer to LCD
B) conj(L6, L3, 768)                      ; LCD to backbuffer

Offline Builderboy

  • Physics Guru
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5673
  • Rating: +613/-9
  • Would you kindly?
    • View Profile
Re: Features Wishlist
« Reply #286 on: March 21, 2010, 07:24:27 pm »
You would probably have to change them to this to preserve the actual LCD buffer.

A) expr(L3,L6,768):DispGraph:expr(L3,L6,768)

And do this, since he was asking to store from the LCD, not the buffer.

B) expr(L3,L6,768):StoreGDB:expr(L3,L6,768)

However, it could be nice to have some built in commands for this.  Perhaps StoreGDB # with different numbers meaning different  buffers?

Offline ACagliano

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 903
  • Rating: +31/-2
    • View Profile
    • ClrHome Productions
Re: Features Wishlist
« Reply #287 on: March 21, 2010, 07:33:58 pm »
I tend to prefer the TI Basic way of calling lists, though I believe it was said that that is not possible. And, my request is for various linking commands. One set of send/receive that waits for a response or times out, and a single send command that just fires away, but doesn't wait for a response (if this is possible).
« Last Edit: March 21, 2010, 07:34:21 pm by ACagliano »

Offline DJ Omnimaga

  • Now active at https://codewalr.us
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55816
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • CodeWalrus
Re: Features Wishlist
« Reply #288 on: March 21, 2010, 09:30:20 pm »
You would probably have to change them to this to preserve the actual LCD buffer.

A) expr(L3,L6,768):DispGraph:expr(L3,L6,768)

And do this, since he was asking to store from the LCD, not the buffer.

B) expr(L3,L6,768):StoreGDB:expr(L3,L6,768)

However, it could be nice to have some built in commands for this.  Perhaps StoreGDB # with different numbers meaning different  buffers?
Is it still safe, though? I guess it might be since:

Quote
L3 = 768 bytes (appBackUpScreen) Volatility: MED (Saving to back-buffer will corrupt)
L6 = 768 bytes (plotSScreen) Volatility: HIGH (Any buffer drawing will corrupt)

But I want to make sure that before using your suggestion (or SirCmpwn's), I won't run in any further problems, later, doing some stuff with these pointers
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF


Bandcamp|Reverbnation|Facebook|Youtube|Twitter

_player1537

  • Guest
Re: Features Wishlist
« Reply #289 on: March 21, 2010, 09:58:28 pm »
on the next version, I think it would be helpful if the compiler told you what line was wrong, it wouldn't have to let you fix it right there just to tell what the line is.  Just my 2 cents  (great job so far :P)

Offline Builderboy

  • Physics Guru
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5673
  • Rating: +613/-9
  • Would you kindly?
    • View Profile
Re: Features Wishlist
« Reply #290 on: March 21, 2010, 11:23:57 pm »
But I want to make sure that before using your suggestion (or SirCmpwn's), I won't run in any further problems, later, doing some stuff with these pointers

Well since L3 and L6 are the backbuffer and the main buffer, i should think so, but you'd have to check with Quigibo o.O Using built in routines would indeed be safer :)

Offline DJ Omnimaga

  • Now active at https://codewalr.us
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55816
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • CodeWalrus
Re: Features Wishlist
« Reply #291 on: March 21, 2010, 11:43:13 pm »
Yeah I guessed it might be safe, since they're buffer-related. I was just a lil bit unsure. I try to not take too many chances sometimes you know XD (you know what happened to Illusiat 2002)
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF


Bandcamp|Reverbnation|Facebook|Youtube|Twitter

Offline Eeems

  • Mr. Dictator
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6158
  • Rating: +318/-36
  • C'est la vie
    • View Profile
    • Eeems
Re: Features Wishlist
« Reply #292 on: March 22, 2010, 12:38:10 am »
I would really like some sort of fps counter or something, so you can see how your code handles differing amounts of objects and such.
/e

Offline DJ Omnimaga

  • Now active at https://codewalr.us
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55816
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • CodeWalrus
Re: Features Wishlist
« Reply #293 on: March 22, 2010, 12:42:36 am »
wouldn't that be 84+-only, tho? (clock)
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF


Bandcamp|Reverbnation|Facebook|Youtube|Twitter

Offline Eeems

  • Mr. Dictator
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6158
  • Rating: +318/-36
  • C'est la vie
    • View Profile
    • Eeems
Re: Features Wishlist
« Reply #294 on: March 22, 2010, 01:22:49 am »
True, though if there was some way to do that on 83+'s that would be nice, even an approximation.
/e

Offline LordConiupiter

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 339
  • Rating: +3/-0
  • Just one of the thousands of Axe-fans...
    • View Profile
Re: Features Wishlist
« Reply #295 on: March 22, 2010, 12:22:12 pm »
Yeah, sure.
But is it true that there is no way to get vars from the calc like the Pic1-Pic0 vars and the real variables?
If (that's true), I would like to have the function GetCalc([var name]) manage that.
Else I would like to have an example for how to do it.

I also would like the ability to use ElseIf:

If EXP1
[code1]
ElseIf EXP2
[code2]
Else
[codeX]
End
everytime that I was down, you would always come around, and get my feedback on the ground. (modified part from 'Seasons in the sun')

No matter how many errors are bothering you, always try to stay rel-Axe!

The HoMM project will be resumed as soon Axe 1.0.0 will be released!
Projects:
Code: [Select]
HoMM:   [==--------]    Project 'resumed': I'm suffering overwhelming new ideas being popped up in my dreams :P
tiDE:   [----------]    Explored and understood the main part of the code: just started writing a Tokenizer.



password of the week: uvanapererubupa (Any pronunciation is the right one ;) )   :D click me, and you'll be raided :D

SirCmpwn

  • Guest
Re: Features Wishlist
« Reply #296 on: March 22, 2010, 12:26:42 pm »
I also would like the ability to use ElseIf:

++ ElseIf
Also, speaking of ++, I would like to see ++ and -- implemented, and possibly +=, -=, *=, /=.

I've been meaning to write another routine for accessing user variables.  I'll post it when I get around to it.

Offline Quigibo

  • The Executioner
  • CoT Emeritus
  • LV11 Super Veteran (Next: 3000)
  • *
  • Posts: 2031
  • Rating: +1075/-24
  • I wish real life had a "Save" and "Load" button...
    • View Profile
Re: Features Wishlist
« Reply #297 on: March 22, 2010, 01:52:01 pm »
The ++ and -- are already supported.  You just write them as +1 and -1.  The compiler automatically optimizes them to the increment.  ElseIf is a possibility, I forgot about that.  A FPS counter is something you could do with interrupts.
___Axe_Parser___
Today the calculator, tomorrow the world!

SirCmpwn

  • Guest
Re: Features Wishlist
« Reply #298 on: March 22, 2010, 01:55:31 pm »
The ++ and -- are already supported.  You just write them as +1 and -1.  The compiler automatically optimizes them to the increment.  ElseIf is a possibility, I forgot about that.  A FPS counter is something you could do with interrupts.

Okay on the +1 and -1, thanks.  Also, FPS requires you to know when a second (the S in FPS) has passed.

Offline LordConiupiter

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 339
  • Rating: +3/-0
  • Just one of the thousands of Axe-fans...
    • View Profile
Re: Features Wishlist
« Reply #299 on: March 22, 2010, 01:57:07 pm »
I also would like the ability to use ElseIf:

++ ElseIf
Also, speaking of ++, I would like to see ++ and -- implemented, and possibly +=, -=, *=, /=.

I've been meaning to write another routine for accessing user variables.  I'll post it when I get around to it.

OK, Nice!

*LC hopes to hear from you soon*
everytime that I was down, you would always come around, and get my feedback on the ground. (modified part from 'Seasons in the sun')

No matter how many errors are bothering you, always try to stay rel-Axe!

The HoMM project will be resumed as soon Axe 1.0.0 will be released!
Projects:
Code: [Select]
HoMM:   [==--------]    Project 'resumed': I'm suffering overwhelming new ideas being popped up in my dreams :P
tiDE:   [----------]    Explored and understood the main part of the code: just started writing a Tokenizer.



password of the week: uvanapererubupa (Any pronunciation is the right one ;) )   :D click me, and you'll be raided :D