BETA VERSION COMPLAINTS (9/22/93) --------------------------------- PROJECT MANAGER -- D.A. Spanfield [] the following is a list of complaints folks have with the BETA version of the Project Manager. Additionally, there might be some explanation for the existence of the problem and possible solutions -- but don't count on it. [disclaimer] the fact that a complaint is listed here is, by now means, a guarantee that the problem/feature will be fixed/changed in the final version of the product. o begin BOY, IS THIS PRODUCT SLOW OR WHAT? --> This product was designed in Paradox for Windows on a Dell 486P/33 with 12 megabytes of memory. At the point of this writing, we find the speed of the application to be acceptable, but make no claims that on slower machines with less memory that you will be entirely pleased with that performance. While it is likely that some of this slowdown could be due to sloppy coding on our part, a majority of the credit should go to ObjectPAL which is no speed demon. AFTER SWITCHING PROJECTS, THE OBJECT LIST IS OUT OF DATE --> This problem has been noticed and is being looked into. This condition does not seem to be occurring EVERY time, so it is a bit slippery. Any information would be appreciated. *** Editor's Note: Selecting a different object type and then selecting the previous type causing the list of objects to synchronize. UNABLE TO CREATE DBASE FILES --> The dlgCreate() method in ObjectPAL takes one parameter and even if you specify a .DBF extension -- it does not create a dBase file. Feh. Possible solutions include using SendKeys, but we believe this to be a relatively sloppy choice. BITMAPS ON MAIN DIALOG SAY "MACRO" AND "MODULE" --> Whaddya want? These bitmaps were stolen in the first place. Possible bitmap editing before final goods may occur. USER FORCED TO SAVE QUERY TWICE --> Since ObjectPAL does not allow the nifty loading, running, and editing of QBE windows, we're using SendKeys to access QBE windows. This, unfortunately, forces the user to remember what he/she called the QBE and use the proper name when saving the in order for the associated project object to work correctly. THE BROWSER TO SELECT A DIRECTORY IS WAY CONFUSING --> The Paradox for Windows browser is the Achilles' tendon of the product. I would prefer to design my own browser rather than ever using the provided dialog. Unfortunately, I lack the time to undertake such a task and am firm in my belief that Borland will eventually fix this problem. ALL FUNCTIONS ARE NOT SUPPORTED BY THE KEYBOARD --> I'd like to take personal issue with this problem since I happen to be of the opinion that all Windows functionality should be accessible via keyboard since, once comfortable with a product, it boosts productivity immensely. Unfortunately, the ObjectPAL approach of making objects accessible via code is somewhat clumsy. It is our intention to make as much of Project Manager accessible via keyboard as possible. WHAT IS WITH THIS FLICKER THE FIRST TIME I LOAD THE PROJECT MANAGER? --> Only the keen of eye will have noticed this, but when the form is first loaded, you will be a flicker/redraw of the form. My first guess would this would be the setting of a tCursor filter, but, right now, we're just going to say -- AS DESIGNED. *** Editor's Note: Under PROPERTIES|DESIGNER from the Forms Menu, you can turn on a FlickerFree option which should suppress much of the flicker. ACTUAL KEYSTROKES ARE BEING DISPLAYED WHEN I USE CERTAIN FUNCTIONS --> Many ObjectPAL functions which are present for one type of object (say, FORMS) are not present for another (say, QUERIES). Before the 4.5 version of Paradox, there was no work around in ObjectPAL for the lack of these functions. Now we have the methods called "SendKeys" which basically allows use to pipe keystrokes into Paradox for Windows. These, rather messily, allows us the functionality to do most everything we need to do. Unfortunately, on slower machines, you'll actually be able to see the keystrokes being executed. WHERE ARE DELIVERED FORMS/LIBRARIES -- HOW CAN I DELIVER A FORM? --> A distinct lack of other buttons to represent delivered object is apparent. Before the final version of Project Manager, we will incorporate to not only display delivered objects as well as interactively deliver them via Project Manager. HITTING "RETURN" BUTTON FROM THE BUILD PROJECT DIALOG DOES NOT ALWAYS RETURN --> This problem is being looked into. Try hitting RETURN again, it'll probably work. WHY CAN'T I ADD OBJECTS FROM DIFFERENT DIRECTORIES TO THE SAME PROJECT --> That would be nice, wouldn't it? After a clean first run of this product, we will be devoting our efforts to a much more robust implementation of the idea of a "project" (That is, unless Borland beats us to it). Such an implementation would allow objects in a project to be located anywhere on the hard disk or network through the clever use of ALIASes or PATHS. WHAT ELSE THE PROGRAMMER WOULD LIKE TO ADD --> Robust object management --> Change the requirement for the path entry (c:\dirname) --> Prevent the user from loading more than one copy of the main form --> Add functionality to allow people to copy ENTIRE/PARTIAL PROJECTS to someone else --> Add object should allow user to not just create, but add from different directory (add field to OBJTBL, add code to deal with this) --> Some more "original" bitmaps POST BETA ADDITIONS ------------------- by D.A. Spanfield 1.55 ---- - Phil now remembers WHERE he is on the screen when he is closed down -- this needs to be verified on other resolutions even though we're saving the position in twips * Want to add option to switch whether or not Phil will record position * Want to add much SMARTER directory entry - Phil will now behave when he asks whether or not to switch projects after a new project is created - Misc UI changes o end