Keeping graphic objects in programs
|
11-21-2020, 04:43 PM
Post: #5
|
|||
|
|||
RE: Keeping graphic objects in programs
(11-21-2020 03:03 AM)cahlucas Wrote: Dear Mr. Gege, If you type ICON in the command line, and while the cursor is touching any letter of the word ICON, pressing the [Help] key will bring up any relevant information on its usage. The unfortunate drawback (pun optional) is that one must rely on computer program to create the data for the ICON command. The data itself can be quite large even for very small images, and it makes code management extremely cumbersome if you ever need to alter your images. In short, there are much better ways that will also make your code more manageable. If you are planning to create a relatively large project (perhaps large due to lots of graphics files), I would recommend creating them as PNG files. This can be done on your computer. Simply create them, and incorporate them into your application. Or if you generate them on your calculator, you can save the image on the screen using AFiles("filename.png"):=G0 (G0 through G9 are the system's graphic objects, with G0 being the current screen.) The AFiles() command really only makes sense within a custom application (i.e. an app you create based on one of the existing apps). One of the applications I wrote makes use of an extensive collection of images: https://www.hpmuseum.org/forum/thread-7725.html The source code is provided as well, so you are welcome to look at how they are used. A snippet of the drawing routine is below. Basically, the images are stored as img##.png files where ## are alphanumeric digits and "na" specifically means a picture is not available (scheme selected for ease of coding). The "picture" is either a static image, or a collection of frames within an animation. Code: // UI for viewing picture Graph 3D | QPI | SolveSys |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)