Request for next firmware [10637]
|
03-14-2017, 12:59 PM
(This post was last modified: 03-14-2017 01:01 PM by Carlos295pz.)
Post: #1
|
|||
|
|||
Request for next firmware [10637]
Variables:
Functions:
Viga C | TD | FB |
|||
03-14-2017, 01:29 PM
Post: #2
|
|||
|
|||
RE: Request for next firmware [10637]
(03-14-2017 12:59 PM)Carlos295pz Wrote: Functions: I think it would be better to have a function that tells the program/app what the current view is (Home vs CAS) but I am not sure how any program would make use of being able to set the view. Any running program would not be able to interact directly with either Home or CAS view (in particular with respect to obtaining user input). Could you share what your ideas are for with respect to STARTVIEW(-10) and STARTVIEW(-11)? How enabling these two instances be used? Quote: Since you have presumably redefined those keys, you can simply call the functions themselves. That's all that STARTVIEW would effectively do anyway. So instead of STARTVIEW(8), simply call the Symb() function that you have redefined. Graph 3D | QPI | SolveSys |
|||
03-14-2017, 02:58 PM
Post: #3
|
|||
|
|||
RE: Request for next firmware [10637]
(03-14-2017 01:29 PM)Han Wrote: I think it would be better to have a function that tells the program/app what the current view is (Home vs CAS) but I am not sure how any program would make use of being able to set the view. Any running program would not be able to interact directly with either Home or CAS view (in particular with respect to obtaining user input). Could you share what your ideas are for with respect to STARTVIEW(-10) and STARTVIEW(-11)? How enabling these two instances be used? The need arises when working with Applications, for example that being in Plot in Graph3D you can go to Home or CAS with the keys, this in order to program a correct flow of operation of an App. (03-14-2017 01:29 PM)Han Wrote: Since you have presumably redefined those keys, you can simply call the functions themselves. That's all that STARTVIEW would effectively do anyway. So instead of STARTVIEW(8), simply call the Symb() function that you have redefined. Exactly, this is nesting, but if it is not well controlled, it could generate enough rubbish variables, using a STARTVIEW would allow you to completely exit the main function Viga C | TD | FB |
|||
04-11-2017, 12:58 AM
Post: #4
|
|||
|
|||
RE: Request for next firmware [10637]
When sending files to Apps using the Connectivity Kit, I would like the program to save the last visited route.
Also, allow the individual extraction of files by drag, since the current forms are not very clean methods, when adding files also allows to select multiple files and that to the Accept, display a separate progress bar to monitor the failure to send some file. I'm currently devoting myself to creating applications that use lightweight files. Viga C | TD | FB |
|||
04-11-2017, 09:27 PM
Post: #5
|
|||
|
|||
RE: Request for next firmware [10637]
When editing a program in the Connectivity Kit, saving should cause the calc to open the program and 'check' the syntax automatically.
Doing this manually each time gets a bit tedious. |
|||
04-13-2017, 12:59 PM
(This post was last modified: 04-13-2017 01:00 PM by toml_12953.)
Post: #6
|
|||
|
|||
RE: Request for next firmware [10637]
(03-14-2017 12:59 PM)Carlos295pz Wrote: Variables: I'd like to be able to read and set the font size from a program, too. HFont:=1; // For small font HFont:=2; // For medium font HFont:=3; // For large font would be great. Tom L Tom L Cui bono? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: