CompuServe Messages

<Me too – I'd like to learn about how to POE> See my (disappointing) reply to Dave. <Im unfamilar with publication – how where to subscribe – how much etc?> It's "the official guide to Autodesk Multimedia" toll-free number for ordering: 800/441-4403 (ext. 362). $59.95 for one year (6 issues) < any special tricks or neat code fragments can often be useful!> OK <I have a few bit (or bytes) that I'm trying to upload – if I can ever get them up- very frustrating -> I found that to be the case with my first uploads. WinCim works pretty well for uploading. I prepare the keywords, description, etc. beforehand and then use "paste." Even though Edit/Paste is not available when uploading, you can use "shift-insert" for pasting. Really not clear why poco didn't take off> I initially found POCO frustrating. It took me a while to learn where it could be useful. For a long time I avoided POCO. It seemed that every time I started on a program, I couldn't finish it. There was always an action that had not been made available (or had to be done in an entirely different way). For example: 1. I wanted to create a menu for selecting tools. Couldn't find the equivalent of "SetInk()" for tools. 2. I wanted to write a POCO program to paste a cel so that its upper-left corner was in a certain spot. Maybe, there's a way, but I gave up. 3. I needed to "clip" the entire flic within a POCO program. I couldn't find an easy way to do it in POCO. ("CelClip()" requires user intervention, "CelGet()" requires that I specify the bounding coordinates.) 4. I thought I might get around these problems by using recorded macros to replace the missing functions. Guess what. There is no POCO function for reading macro files. And then there are a few bugs. I've come accross these: 1. Use of "if (something) continue" inside a loop resulting in an infinite loop. 2. Use of "float" in arguments causing problems (I have to check but I think a value of 0 was always passed). Now, I only use "double." Ed K