alexis@ccnysci.UUCP (Alexis Rosen) (01/08/89)
A few more problems with LSP 2.0: 1) I don't see how this could have gotten past QA, so maybe I'm doing something wrong. But still, it is *very* strange. According to IM I-353, InsertMenu() takes two arguments, a MenuHandle and an Integer (menuID). When I tried to use it in my code, LSP insisted that my MenuHandle was not the right type (it said something like "Actual and formal paramaters incompatible"). Just to make sure I wasn't somehow giving it the wrong kind of Handle, I coerced it to type MenuHandle. It still failed. Then I coerced it to type Pointer (which is compatible with all pointer-types) so it would compile. The code then worked fine, which leads me to believe that my code is correct and LSP is at fault. But how could it be? I imagine almost everyone uses InsertMenu... 2) LSP 2.0 apparently uses the old MenuInfo structure. While this data structure can't really be expressed in Pascal, there is a semi-pascal structure given for it in IM Volume 1. IM Volume 5 changes this definition, and it would be nice if the interface files matched the new definition. But since the LSP interfaces come from Apple, it doesn't seem likely that this will change. 3) Arrow keys in the editor are wonderful (it's about time) but they don't always work right. If you arrowkey to a different line, and the prettyprinter decides to do its devilish work, you're screwed. There's no telling where the insertion point will go. If you then start typing or deleting, you can really mess things up if you don't notice what you've done immediately (although undo makes this a little less dangerous). Shades of Fourth Dimension (ugh!). Flames to /dev/null. This isn't a _serious_ bug report, but it is legitimate. Alexis Rosen alexis@ccnysci.uucp