DP Tool Club 17

home *** CD-ROM | disk | FTP | other *** search

/ DP Tool Club 17 / CD_ASCQ_17_101194.iso / vrac / suglst.zip / SUGLST.TXT < prev

Wrap

Text File | 1994-09-01 | 1MB | 16,449 lines

Clarion Database Developer Suggestion List Ascii Report as of 9/01/94 COPYRIGHT 1985, 1986, 1988, 1990, 1992, 1993 by Clarion Software Corporation All Rights reserved. Status - Meaning -------------------------------------------------------- Suggestion - Suggestion for future release. ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2986 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ API Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:41630 │ │ I'd like to put that in as a suggestion. "Please add a way │ │ (even if it's in the API Toolkit) to retrieve the currently │ │ aliased keys (and what they are aliased to)." Thanks. │ │ ..Ralph │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4159 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 3/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ API Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ documentation for findfirst/findnext should include a │ │ statement that "all filenames" in directory will be │ │ returnedincluding any that match the attribute passed to │ │ findfirst. User is expecting only entries to be returned │ │ that match the attribute. │ │ ex. using the FA_DIREC attribute, user │ │ expected to only see directory entries, but was seeing │ │ all files including directory entries. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0338 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/12/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ BROWSE.CLA and CLARION3.TPX MODIFIED. │ │ Spent quite a while last night looking at the BROWSE │ │ functionality. I was trying to determine the changes │ │ necessary to place a functional SCOPED HOT LIST (ie. list │ │ of recs from a secondary file scoped to the current hilited │ │ record in the main queue) on the same screen. │ │ I looks to me like the only good way to implement such a │ │ capability right is to have BrowseAction() return a │ │ specified value (6?) indicating that the record under the │ │ hilite bar has just been read (due to FirstHot/LastHot │ │ being in use). Maybe something like "OF NewHilite" with │ │ template set for #EMBED('Hilite Bar Moved') under it to │ │ provide for the code insertion. │ │ This basic ability to recognize when hilite bar movement │ │ has occurred (w/o having caused any scrolling) was missing │ │ from 2.x also, and prompted many of us to develop our own │ │ arcane code/models to provide this functionality. From │ │ reading msgs left by others, I know that I am not the only │ │ one interested in this capability. Although I as well as │ │ other developers will probably be able to build │ │ "workarounds" with 3.0 just as we did with 2.x, the gurus │ │ there at Clarion could surely provide a much cleaner, and │ │ faster implementation. The desire for support of this one │ │ feature has been (under 2.x), and will continue to be │ │ (under 3.0) a very important issue. The "HOT" field │ │ implementation is a great step in the right direction, but │ │ my feeling is that a more complete implementation (similar │ │ to that described above) would be more a lot closer to what │ │ most users are looking for. │ │ Hope this doesn't ruffle any feathers, but I (and many │ │ others) think its VERY important. It might be interesting │ │ to take a poll on this and make Mr. Barrington aware of the │ │ outcome. What do ya think? │ │ Larry Teames AZ CUG Pres CREATIVE PC SOLUTIONS 602 963-3506 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0365 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Record selectors are just like 2.1 where it is case │ │ sensitive, is there a way we can aviod this if the choose │ │ there key to be non-case sensitive. │ │ ----------------------------------------------------------- │ │ Suggestion: Detect if Case insensitive key and UPPER each │ │ component for the compare if it is a string │ │ key. (This will be driver dependent) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1457 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 6/08/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Cannot use a radio button as a locator. ?maybe we │ │ shouldn't be able to? │ │ R&D: 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1588 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/18/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ >>Process selected will only get embedded when enable HOT │ │ Records is checked │ │ Ok, but when "Process Selected" is enabled, then the │ │ "HOT Records" should be automatically checked or beeped or │ │ generate a compile error, or something. Because as it │ │ stands now, it's very easy to stick code into "Process │ │ Selected" and it never gets embedded into the source. The │ │ developer will wonder what's going on or he may not realize │ │ the code isn't being executed. This type of assumption that │ │ "Hot Records" must be checked when using "Process Selected" │ │ will lead to programming bugs. │ │ Could we at least put something in the HELP or generate a │ │ warning if this EMBED is Used and HOT Records is NOT │ │ checked? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1983 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/26/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Patrick Donnelly 73730,1215 │ │ When adding records to a file that has a list box th at is │ │ not full (Browse template) ie. 15 row list box with 5 │ │ records. When you add a record that goes at the beginning │ │ or the end of the list, the entire list is displayed │ │ (Good), but if a record is added that would go in the │ │ middleof the list, that record is dispalyed at the top of │ │ the listbox and all records that preceed the new record │ │ scroll off (Bad). Let me run a (very) simple example: │ │ List Box: A B C D Z │ │ Add record 'F' New list box: F Z │ │ Personally, I feel that if the file being │ │ dislayed is smaller than the List box, the entire file │ │ should always be displayed. │ │ Q & A : Browse Change, Enhancement │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2213 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 8/25/93 │ │ Reported In : 3005 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about a checkbox for "no automatic update if no records │ │ or selector/filter fails"? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3056 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/15/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:42386 │ │ In case any of the template folks are interested, the │ │ present implementation of Browse (actually TPX and the CLA) │ │ is such that one has to go thru a lot of hoops in order to │ │ redisplay the Browse List items when the Range Value has │ │ been changed thru something other than a ?Field < ?List. │ │ For instance, if one has a Pulldown item which │ │ selects various Range Values, Browse.Cla will not see │ │ changes and thus redisplay the first page because of the │ │ following: OF ProcessField │ │ IF FIELD() <> Locator │ │ IF Increment │ │ DO ClearLocator │ │ END │ │ IF INRANGE(FIELD(),1,List-1) │ │ <<< Assumes a screen field < List FirstPage = 1 │ │ END │ │ END │ │ Of course, simply looking for │ │ pulldown values will redisplay the first page everytime. │ │ Anyway, a good solution might be one for someone to │ │ consider. Douglas │ │ R&D: Possibly will make ROUTINE that will re-initialize │ │ the BROWSE. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3328 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/15/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Multi-ordered Browse suggestions collected from CIS....... │ │ 1. Descending or Ascending order (driver independent). 2. │ │ View/Locate on several different listbox key fields. Switch │ │ to different views/locators on hotkey/mouse click. 3. │ │ Grey+/- reordering of listbox items. 4. Vertical │ │ scrollbarshowing relative record position/number of records. │ │ The ability to use a vertical scrollbar. 5. Faster │ │ accessing of records. 6. Ability to view entire file as a │ │ Browse option, instead of just a "viewer". 7. │ │ Standalone speed increases vs. shared access (using global │ │ #PROMPT). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3604 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 1/26/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests in order to make the BROWSE truly universal, │ │ it should include an option to change the DISPLAY order of │ │ the browse when it is used for either a lookup or validate, │ │ instead of only having an access key for the queue. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3699 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -- when no records match the range limit │ │ itgoes to the entry field on the screen vs to the update │ │ proc..... it appears that the embeded source code point │ │ for of no records is actually no records in file vs no │ │ records in queue. If this is the case is it posible to │ │ make the of no records really mean of no records in queue?? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3788 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 54418 S8/3.0 Support │ │ 09-Feb-94 03:57:28 │ │ Sb: #54322-Locator field alert keys │ │ Fm: Juergen Bartsch 100020,1044 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ if Tom is already working on the locatorthing it would be │ │ nice if he could look │ │ at the problem that I can't type german characters (o,u, a │ │ with dots) at the │ │ first position of the locator field. Workaround: type first │ │ a "legal" │ │ character, press backspace - then you can type any special │ │ character you want. │ │ rgds Juergen Bartsch │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3869 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/16/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a user wants to have browse as a validate allow blank but │ │ ifthey type something in to validate that │ │ This was a suggestion that was made previously since it is │ │ fairly common. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3916 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ reported by user -- ÅÄÖ these characters to not make │ │ anything happen in a locator since they are ascii │ │ characters greater than 127. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3922 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:56444 │ │ Following are 3 examples which the Universal Browse does │ │ nothandle but the Validate does. │ │ Example 1: │ │ You have a Property (parent) 1:many Appraisal (child), │ │ the task is to place the appraisal file on the screen and │ │ let the user select property at run time from an input │ │ field on the universal browse. The Property_ID is on both │ │ files and is the relationship field in appraisal as a "Must │ │ be In File". │ │ The browse is range limited by │ │ appraisal:property_id (property_ID is internally │ │ generated long(@n_5), the user cannot touch). Place the │ │ appraisal:property_id in the screenbefore the ?List, in the │ │ when completed code BR_property which is a universal │ │ browse to validate the propery_ID (to the user this is │ │ property number that I control). The │ │ Appraisal:property is defined as "must be in file" as a │ │ many:1. The BR_PROPERTY is a striped down universal browse │ │ with the Change, Insert & debutton removed and all other │ │ files removed from the normal browse that has many related │ │ hotfield displays. After all the purpose is to simply │ │ selecta property. │ │ Since I am not in a form, keycode() never gets set │ │ to SHFTENTER, the browse displays the list table with │ │ select disabled, pressing enter does select the button │ │ (real problem), but nothing is returned. If I hand │ │ code setkeycode(SHFTENTER) before the BR_PROPERTY, │ │ the browse displays the list table with select enabled & │ │ either enter or mouse/key press on select will select the │ │ record, remember I am not in a form, nothing is in │ │ the appraisal:property_id. I I hand code │ │ SETKEYCODE(SHFTENTER), BR_PROPERTY, APPRAISAL:PROPERTY_ID = │ │ PROPERTY_ID, display(?appraisal:property_id) it │ │ will work. If I simply put VA_property (to a validate │ │ template) in the when completed, all the actions will │ │ be completed. In either caseI need to add a select(?list) │ │ for the filter to work or mouse press on the list table. │ │ Example 2: │ │ Each user has a default │ │ printer assigned, but on the redirectreport I provide │ │ the abilty to allow to temporarily override using a local │ │ variable, the user can either type in a new printer name │ │ or just overtype one character so that validate doesn't │ │ match and provides a list of printers to choose from. (In │ │ reality I put a down-arrow button in front of the field │ │ so the user can click this clears the printer name │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4075 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From Greg_W: After explaining why the Browse doesn't │ │ support a vertical scroll bar I recieved the following │ │ "suggestion". │ │ Greg, I've seen this explanation offered at least twice │ │ before by you guys. The problem is, our clients are going to │ │ complain to us and we'll complain to you until this is │ │ madeto work differently, no matter WHAT the explanation is. │ │ Whenever there's a table of records displayed and the │ │ operator knows *(*&% well there are more records above │ │ and below the display, if he has a vertical scroll bar │ │ ANYWHERE in the application, he is going to expect one │ │ EVERYWHERE in that situation, and will expect to be able to │ │ drag it up or down to scroll the data. Period. Especially │ │ if he's a client who doesn't know beans nor care about │ │ queues, listboxes, or whatever. │ │ If it's a basic, core system characteristic │ │ that's is a super big deal to fix, it's still a problem. │ │ It seems to me something is going to have │ │ to be done about performance of queues and list boxes, │ │ anyway. The current convention of loading the queue │ │ with a list-box-worth of records is causing │ │ horrible performance problems when one more record is │ │ scrolled into the list box (up or down). I don't know what │ │ you guys are doing differently from the rest of the │ │ industry -- a scrolling data table with quick, │ │ responsive movement up and down the table seems to be sort │ │ of a basic capability one has come to expect. CDD can't do │ │ that yet. It's going to have to, somehow. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4087 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/09/94 │ │ Reported In : 30071 RevisedDate : 3/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:59162 │ │ 3007.1 Browse template with range limit. If the File has │ │ no records, the update form is presented, if the fille has │ │ records, but none that match the range limit, the browse │ │ retains focus with the Insert button highlighted (no │ │ records in list box). │ │ The browse template should always remain displayed, │ │ regardless of whether records exist in the file. │ │ Example, fileb is range limited to filea, the range │ │ value is not used and the range limit is an input field on │ │ the browse allowing user selection to filea. The input form │ │ is presented when no records exist, the range limit field │ │ has not been completed and is zero. The range limit │ │ field is NOT an input field on the form, it is supplied │ │ from the browse (which is zero at this time). │ │ Jerry L. Petri │ │ Practical Computing Group │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4091 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/10/94 │ │ Reported In : 30071 RevisedDate : 3/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Princen 100276,2655 MSG#:59198 │ │ My last message probebly scrolled. I responded to your │ │ answer on NEWPTR. This is what I find a bit unacceptable: │ │ I have a browse with a file with a non unique key. │ │ When I add a record with a key value that already │ │ let's say 20 times exists then my selector bar stands on │ │ the first one in the list and not on the one I just added. │ │ Did I add the record or .......... This is what I call │ │ confusing. │ │ Majodi Ploegmakers │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4292 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/05/94 │ │ Reported In : 30072 RevisedDate : 4/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Larry Teames 73150,104 MSG#:63536 │ │ 1. Regarding NoMemo: The BROWSE.CLA looks for a '2' to │ │ designate whether the memo should be read at particular │ │ times, even if NoMemo is selected in the template prompts. │ │ The template, however, never sets the BeginBrowse │ │ parameterto a '2', but _always_ sets it to a '1' (NoMemo │ │ except for HotFields). In my testing, I found that if a │ │ memo is NOT inuse at all, the '2' causes SIGNIFICANT speed │ │ increase. I suggest that, barring the addition of │ │ template code to conditionally set the '2' (ie. is a │ │ memo in the HotFields?),alwaysit to a '2' is NoMemo is │ │ checked. │ │ ****** This bug is a │ │ duplicate of 3997: 2 .Based on my │ │ testing, it appears that if a browse is being used as a │ │ lookup and the lookup code does a GET() which causes an │ │ access which is BEYOND THE HIGHEST RECORD IN THE KEY, the │ │ browse begins building the QUEUE FROM THAT POINT, which │ │ causes the LIST TO BE EMPTY. I'm not sure what the │ │ answer is, but I would think that in the lookup code, if │ │ the get() turns up an errorcode(), maybe then test for 33 │ │ and if it is 33, do a previous(). Hope some of the above │ │ makes sense. I've seen several messages recently │ │ regarding topics which I suspect have had to do with both │ │ of these issues. Later, Larry Teames -- Creative PC │ │ Solutions -- AZ CUG There is 1 Reply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4361 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TM DateReported : 4/12/94 │ │ Reported In : 3009 RevisedDate : 4/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Incremental locator should be dimmed if no locator was │ │ entered. Of course this means additional APPGEn & │ │ Tem[plate changes could be a 3.1 or above issue │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4849 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/17/94 │ │ Reported In : 3008 RevisedDate : 6/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like the ability to get hold of the locator │ │ field before anything is done with the locate action. │ │ currently some things happen before the code within the │ │ editproc gets issued. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4936 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 7/12/94 │ │ Reported In : 3009 RevisedDate : 7/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ end user suggestion dealing with numeric incremental │ │ locators. see 4936.zip │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4946 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/15/94 │ │ Reported In : 3009 RevisedDate : 7/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Browse Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Attached file has a suggested change for browse incremental │ │ locator. │ │ 4946.zip │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2203 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 8/24/93 │ │ Reported In : RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Btrieve Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about some sort of menu driven utility to view a │ │ Btrieve file's statistics <ala BTFILER/BTVIEWER> to help │ │ with file/key definition in the dictionary? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2939 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/05/93 │ │ Reported In : 3006 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Btrieve Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ With NLM 5.x you non-case sensitive sorting is controlled │ │ via the alternate collating sequence. The Clarion system │ │ allows you to use the CLACOLSEQ variable to specify an │ │ alternate collating sequence. However, this does not give │ │ true case insensitive sorting like Btrieve. Instead you │ │ have a<A<b<B... │ │ How about a method of specifying that a Btrieve ACS file is │ │ used when creating the file. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3318 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 12/15/93 │ │ Reported In : 3006 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Btrieve Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Btrieve currently does not support a 'manual' key. This is │ │ a key that if any component of the key is null an entry is │ │ not put in the key. Hopefully we can add this in a future │ │ release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3993 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/01/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Btrieve Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Leschak (CompuSyste 71461,471 MSG#:56502 │ │ i would like to know if there is some way that i can │ │ process all fields in a record and get a record layout at │ │ runtime. │ │ i was thinking this might be done via some SEND │ │ commands, possible something like this: │ │ !*** get the number of fields in a file │ │ lFields# = SEND('FILE=MYFILE.DAT,FIELDCOUNT) │ │ for i#=1 to lFields# │ │ !*** get the name of the i#'th field │ │ sFldName" = │ │ SEND('FILE=MYFILE,GETFIELDNAME,i#) │ │ !*** search │ │ for a record lErr# = │ │ SEND('FILE=MYFILE,KEY=MYKEY,'&sFldName&"'='jones') │ │ !*** │ │ get the field value │ │ sFldValue = SEND('FILE=MYFILE,GETFIELD='&sFldName") next i# │ │ then i │ │ could do some limited (or unlimited) user defined functions │ │ and queries with this capability. boy, the things we could │ │ do with this kind of functionality would be incredible! │ │ jsl │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4107 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/14/94 │ │ Reported In : RevisedDate : 3/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Btrieve Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Allow Truncated files to be created by the Btrieve driver. │ │ R&D Note: Can do via /TRUNCATE=[ON|OFF] switch │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1647 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/25/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Child Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a line needs to be added to the template help as to │ │ whether any of the pushbuttons may be deleted. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1985 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/26/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Child Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dave Carlton 75620,617 │ │ With the child template, is it possible to prevent duplicate │ │ records while the user is adding the child records to the │ │ que? Ccurrently it just warns them after they have entered │ │ several child records. │ │ R & D: Enhancement issue. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2904 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Child Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Need to be able to use sum, avg and count formulas in the │ │ child template. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3701 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Child Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ You might want to relog as suggestion rather that problem, │ │ but the child template does not support autonumbering. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3903 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 2/18/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Child Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Release 3007.104 │ │ Is it valid to get rid of the delete button? Template help │ │ needs to be updated to tell which fields/buttons are │ │ required and which ones can be deleted. │ │ Suggestion: User would like to be able to get rid of the │ │ delete button? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0187 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/01/93 │ │ Reported In : 3001 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ ClaCnv │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Take away the "immediate" attribute from the case │ │ conversion field prior to conversion. Maybe add a "PRESS │ │ ENTER TO BEGIN CONVERSION" message. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0848 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 8/10/93 │ │ Reported In : 3000 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ ClaCnv │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ This was legal in 2.1... │ │ file file,pre(fil) │ │ record record │ │ field1 long │ │ field2 long,over(fil:field1) │ │ . . │ │ The 3.0 compiler does not like the prefix in the over() │ │ statement. Could that be fixed by clacnv??? │ │ This will need to be fixed by the developer. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0740 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/02/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Clarion file driver seems to support string greater than │ │ 255. You can't declare this in the dictionary but you can │ │ in the code. You are then able to read and write a │ │ string(1200) to the data file and read it back. In │ │ discussion with Chuck, he said this would be changed to │ │ return "Invalid Record Declaration" if a file Clarion file │ │ is declared this way. │ │ Q & A : This will be a 3.1 issue. │ │ This is a feature in hand code. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2326 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/15/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 │ │ Hi Guys │ │ We have a developer who designed an access-control system │ │ using version 2.1. The system adds & deletes approx 20000 │ │ records per day. │ │ Until 2109 the key files had to be re-built every two │ │ weeks (at one site) because the key entries were not │ │ reclaimed - the key files would grow to fill the hard disk │ │ and if the BUILD was not executed, the system would crash. │ │ The developer claims that the situation is │ │ better in 2110 but that the key files do still grow - at │ │ the same user site they have to re-BUILD every 3 months now │ │ instead of every 2 weeks. │ │ This has implications for the version 3 │ │ CLARION driver if it is true... │ │ I would strongly recommend including a │ │ test for this situation in the driver test suite. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2940 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 11/05/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The tech bulletins current have our data file and key file │ │ layouts. It is my understanding that these layouts have │ │ changed after the release of 2109 any may be different │ │ still in 3.0. A couple of users have requested this new │ │ information. │ │ Also the tech bulletins indicate that you may read Clarion │ │ files but that to update them you must be licensed. Is this │ │ still the case. Maybe the new tech bulliten could state the │ │ current policy │ │ Suggestion: Please update this information in the tech │ │ bulletin. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3005 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/10/93 │ │ Reported In : 3006 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Sink 71161,2354 MSG#:41741 │ │ Transaction files from logout are created in the directory │ │ where the EXE is located. Instead of defaulting to the │ │ application's original directory, can you guys change it to │ │ read the CLATMP variable? │ │ Thanks, Paul │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4046 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 3/07/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There should be a method to encrypt key files; when DATA │ │ files are encrypted, important data may be left visible in │ │ the KEY files since keys are not encrypted. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4909 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 7/05/94 │ │ Reported In : 3009 RevisedDate : 7/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clarion Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Driver.doc needs to include the fact that we recommend 2110 │ │ versions of 2.1 data files for compatiblity reasons. │ │ And if we don't then what are the pitfalls of using │ │ 2108, 218a or 2109. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3866 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 2/16/94 │ │ Reported In : 30071 RevisedDate : 6/03/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Clipper Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion for extra functions to be added for clipper key │ │ expressions: TRIM, ALLTRIM, LTRIM, RTRIM, UPPER │ │ R&D: UPPER has been implemented for 009. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0229 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/08/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The 3.0 compiler gives a "variable expected" error when │ │ trying to do a CLEAR on a report label. i.e. │ │ CLEAR(RPT:DETAIL). 2.1 allowed this and it is very handy │ │ when needed. Obviously, you can clear each individual field │ │ in the section, but is it possible that this could be │ │ allowed in 3.0? │ │ I originaly reported this anomaly in the first testings of │ │ the Compiler! You allow a CLEAR() of a Group, Record and │ │ everything else, why not a Detail structure? │ │ Q & A : This report is a compiler bug. This problem will │ │ be addressed in a later release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2133 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/16/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Thomas D. Stevens 71726,367 │ │ >> Seperating a large report into 2 smaller reports may be │ │ necessary even in 3005. │ │ I find it entirely unacceptable that a screen or report │ │ structure that worked in 2.x would be too complicated for │ │ CDD. │ │ I can accept a certain amount of re-coding to make 2.x │ │ code more palatable to the CDD compiler. But to suggest │ │ that a report be split into two reports, or that a complex │ │ screen be split into two screens, is an arbitrary │ │ limitation and agi ant step backwards. Please log this as a │ │ bug/suggestion -CDD should compile any file, screen, or │ │ report structure that is within the documented limits of │ │ CDD. Tom │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2196 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/23/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard Speiss 76036,17 │ │ I would like to make a suggestion for the 3.x compiler. │ │ I can't convert simple Clarion 2.x programs (menus, reports) │ │ without getting 'dynamic pool limit exceed isl.args' during │ │ the compile. I have replaced all ROUTINES with PROCEDURES │ │ and moved screens to where they are local instead of │ │ global but If I am having to do this much manual conversion │ │ of the code for simple programs I am really worried about │ │ some of my more complicated programs. │ │ I can see a couple of potential options that could be │ │ done: │ │ 1. Increase the size of the pools. I realize that │ │ you are restricting them to 64K due to the chip's │ │ architecture but I think you need to take a look at │ │ working around the 64K limit. This could be an option │ │ in the project file so if people not are having this │ │ problem they won't have to pay any speed penalty during │ │ compilation. │ │ 2. Add a new option to CLACNV to │ │ convert all ROUTINES to PROCEDURES and insert the │ │ prototypes into the MAP. I wrote my own program to do │ │ this since it looks like I will have to do this to all of my │ │ programs (300+) but it would be nice to be part of the │ │ regular conversion. │ │ Thanks Richard Speiss │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3556 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user - ability to hide a field - HIDE() │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3650 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : J DateReported : 1/31/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User wants ability to access EMS with third party OBJ's │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5297 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/22/94 │ │ Reported In : 3009 RevisedDate : 8/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Windows compatible dlls │ │ Section │ │ Compiler │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice to be able to compile straight Clarion │ │ code (no interface stuff) into DLL's that could be used │ │ bothin CDD and CW (like library routines/procedures). Kind │ │ of like Borland's new DOS pack can. I guess it would mean │ │ making the TS DOS DLL's Windows/CW compatible. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1802 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 7/13/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ CPD21 Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Uses sent in 2.1 code for how he thinks a scrolling data │ │ entry should be implemented. │ │ R&D: 3.1. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3208 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/03/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ CPD21 Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have a 2.1 Table Template using hot fields. The load time │ │ for this table is excessively slow, appears to be video │ │ writes to write the repeat area and the fixed area for │ │ EACH and EVERY record in the repeat. Could a │ │ suggestion be put in to modify the REPEAT code, so that │ │ when a full screen page (First_Page and New_Page) is │ │ being displayed, the fixed fields are NOT updated? │ │ Thanks for your help! │ │ Dianne Anstien 73524,107 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0184 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/01/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Include .BTM extensions in the "Programs Only" option of │ │ CSHELL. NDOS and 4DOS use these "Batch to Memory" files. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0716 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 4/08/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Rename (Ctrl - R) of a 2nd or 3rd level directory does not │ │ work. │ │ Q & A: Maybe 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1225 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestion from user: │ │ Can the tree in Cshell be automatically rebuilt │ │ as needed? Like the Windows file manager. │ │ GF: I don't know how windows can detect if the directories │ │ have been changed outside of windows, but this user │ │ says it can detect and 'dynamically rebuild as needed' │ │ it may be a Micky$oft trick. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1229 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: │ │ Add a 'TOUCH' type of facility to allow the user to tag │ │ a block of files and change the Time and Date stamp. │ │ GF: Would be really handy for those who do not have │ │ Borland's TOUCH.COM or do not have SDK. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1487 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/14/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 │ │ CSHELL doesn't ask if you want to overwrite an existing │ │ file when copying a file to a file that already exists. │ │ 1) Press Ctrl-C on a highlighted File. │ │ 2) Enter the name of a File that already Exists │ │ 3) Press Enter │ │ 4) It overwrites the existing file without asking if it │ │ is OK. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2041 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 8/04/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In CSHELL, if you tried to access a disk drive that is not │ │ ready or try to print to a printer that isn't ready, │ │ insteadof having ABORT come up as the default, since this │ │ will kickyou out to DOS, FAIL seems to be the better │ │ choice for the default, it doesn't seem to kick you out │ │ to DOS. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2582 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/06/93 │ │ Reported In : 3005D RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Could we create a way of controling what tier of the tree │ │ we are on? If I have a directory where the name repeats │ │ itself then I can only get to the first occuranc when the │ │ second occurance might be three pages away. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2823 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/29/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 MSG#:39562 │ │ CSHELL will not accept a DOS command line longer than the │ │ displayed entry field length. I think it should accept │ │ input to the DOS limit, rather than the 50 or 60 │ │ characters that it does now. │ │ Joe Bouterse Creative Solutions, Inc. Indianapolis, IN │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3448 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JD DateReported : 1/03/94 │ │ Reported In : 3007 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There is no printer redirection available for Print File or │ │ List Directory in CSHELL. │ │ For users without an LPT1, this can be a show-stopper -- │ │ returning a hardware error window. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3534 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Can we have a message line that shows the status of file │ │ mask displayed, especially "Programs Only". This will avoid │ │ confusion and eliminate the user having to access the │ │ Options Menu to view what files should be displayed. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3668 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tim Murray 73174,3645 MSG#:52416 │ │ How about adding a feature to Cshell which lets you point │ │ toa file like STUFF.CLA then do a CTRL-C to copy the file │ │ and give it the name *.OLD. Same goes for RENAME. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3886 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 MSG#:55605 │ │ In CDIR if you press the Grey + it would put the filename │ │ of the currently highlighted file on the command line │ │ unless you had files marked, then it would put %N.%E on │ │ the command line. This behavior has not carried over to │ │ CSHELL. At least on my computer <g>. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3887 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is not indicated anywhere in the help that CTRL-T │ │ activates tag in the CSHELL. │ │ **Note: 2.1 users are used to CTRL-M. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4190 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick D. Williams 72262,2720 MSG#:61815 │ │ When on a network the Build Tree option causes problems │ │ whenyou use the CShell. It locks the user in building the │ │ tree and takes forever, if you are not totally locked up │ │ first. Why not disable the tree function if the user is on │ │ a network drive or only build the tree for the current │ │ branch,not for the total network. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4349 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/11/94 │ │ Reported In : 3008 RevisedDate : 4/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Martin Wehlou (Cactus) 72047,2444 MSG#:63950 │ │ The "old" rename in 2.1 was *very* nifty; i.e. marking a │ │ number of files, then ctrl-R, then simply a new directory │ │ name or extension using wildcards. One can't do that in │ │ 3.x,or can one? -- Martin [Cactus Computing bvba - Belgium] │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5135 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/20/94 │ │ Reported In : RevisedDate : 7/20/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Cshell won't except standard dos syntax in ctrlC copy │ │ Section │ │ Cshell │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 83809 S8/3.0 Support │ │ 18-Jul-94 18:33:48 │ │ Sb: CSHELL: brain damaged │ │ Fm: Marjolein Katsma 100276,2414 │ │ To: Sysop (X) │ │ I was changing an application, when I discovered - too late │ │ - that I had wanted │ │ to save the previously generated source for comparison but │ │ forgotten to do so. │ │ I had made only some minor changes (screen lay-out and a │ │ few embed lines) in │ │ three procedures (two modules out of five). │ │ So I went to CSHELL (which I don't like anyway) to copy the │ │ original source │ │ files. After poking around in the menus to try to remember │ │ how to mark the │ │ files I wanted to copy (spacebar didn't work), and │ │ 'remembering' to use Ctrl-T │ │ (it's nowhere on the menus but it does mention 'tagging'), │ │ I found the program │ │ to be even more brain-damaged than I already thought: After │ │ marking the files, │ │ I typed Ctrl-C to copy them and entered '*.SA2' (without │ │ the quotation marks). │ │ The program gave me an error (and left the files marked). I │ │ cleared the tags │ │ (that _is_ on the menu) and tried with a single file: │ │ highlighted it, then │ │ Ctrl-C, then typed '*.SA2'. Again an error message! │ │ Come on, this is normal, legal DOS syntax! When I finally │ │ typed out the │ │ command in the space for the DOS command line, it went │ │ without a hitch: 'COPY │ │ OZADDR*.CLA *.SA2' │ │ BTW, Director from CPD can do this - why not CSHELL??? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0333 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/12/93 │ │ Reported In : 3001 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In DataBase Manager there is a drop down menu for │ │ "Locate..." when this option is selected the locate record │ │ window come up.... there is no place to type the name of │ │ the record that I wanted, as soon as I press a letter on │ │ the key board an entry field appears at the bottom left of │ │ the screen. This entry field should be in the locate record │ │ box and be there when the window comes up. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1247 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ using database manager with an ascii or basic file does not │ │ seem to work correctly. if i am creatng a new file and add │ │ data to a field, the data repeats all the way down the │ │ screen, similar to editing an existing file. │ │ user also reported an xtrace when trying to view a large │ │ ascii file │ │ Q & A : Cannot Browse Ascii or Basic │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1255 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Identification of file to browse. │ │ Can there be a way to allow the user to select the .DCT │ │ file first then, default the file name to what is in the │ │ .DCT file when you choose the file label? │ │ GDF - Now the user selects the Data file first. If this is │ │ the first time viewing the .DAT file (ie no .DBM file │ │ found) the user will be asked for the .DCT file, and then │ │ will be asked to select the file label and order. Any way │ │ to cut out a step by asking for the .DCT first and using │ │ the file name found in the .DCT file? If this will cut out │ │ some flexibility then it might need to stay as is unless │ │ you have any other ideas. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1315 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 5/20/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ WE NEED A WAY TO VIEW THE STATUS OF A RECORD....IS IT │ │ ACTIVE, DELETED, OR HELD???? I HAVE TO USE 2.1 SCANNER AS A │ │ TEMPORARY WORKAROUND │ │ Version 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1358 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/26/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 │ │ By the way, you guys should consider doing this to your │ │ version, since it only involves one line of code--just │ │ prior to the set(key,key) you just iniitialize the │ │ *KeyField to the passed value). │ │ What I think Danny is asking for is the ability to give a │ │ value to the Key Field(s) and then issue the Set(key,key) │ │ so that you can jump to the record w/ the closest match. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1386 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/31/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about a way to look at your file with the columns not │ │ having any justification. (left right center) This │ │ prevents me from seeing what my fields really look like!!! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1660 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 │ │ In working with the Database Manager, I noticed that │ │ there is no display of the number of records in the │ │ database, the record number or the amount of space a record │ │ and the file occupy. I would like to suggest that these be │ │ added (like 2.1), as they are very useful when confirming a │ │ conversion or addition to the database has been done │ │ correctly. │ │ Thanks, Joe │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1662 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 │ │ How about adding an 'Empty' item to the Edit Menu in the │ │ Database Manager? I can find no way to create a new or │ │ empty database file other than shelling to DOS and deleting │ │ the .DAT file and then going back to the DB Mgr and │ │ creating a new one. Another option would be to add a │ │ confirm prompt to the Create item if the file already │ │ existed (as opposed to the current error window that does │ │ not allow the overwrite). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1730 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RT DateReported : 7/07/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When changing data in a field in Database Manager, when the │ │ user presses Enter, the data is put into the field and the │ │ cursor goes to the next field in the file. The cursor │ │ should stay in the same field when data is changed, │ │ otherwise it is confusing as to whether the data was │ │ changed ot the highlight just changed fields │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2053 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/06/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 │ │ Create an ASCII file layout in a dictionary. Make just one │ │ field, a string of any length. Save, make a new file using │ │ the file layout just created via the database manager. │ │ Insert a new record - type aaaa & click on Ok. The whole │ │ screen will fill with repeats of the record. │ │ Bug in the driver? │ │ R&D: Use the Editor or Cshell or something other that │ │ Database Mgr to look at Ascii, Basic or DOS files. This │ │ may get addressed in a future release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2117 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/12/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ record number is not displayed in the database. This is │ │ very helpful and 2.1 users have relied on it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2345 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 9/17/93 │ │ Reported In : 3005 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Database Manager : In the "File", "Print" pulldown option, │ │ "Print" should be "Print..." since another dialog pops up │ │ after you choose it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3850 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Database Browser │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Is there a posibility of getting word wrap to happen when │ │ you are editting a memo here in the editor. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2477 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 9/27/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dbase IV Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reports -- dbase4 driver -- he says that dbase │ │ actually stores a CR and he cannot store the CR in the same │ │ manner in clarion -=- This gets stored by pressing the │ │ enter key in dbase ... │ │ he claims that if he adds a memo to the dbase4 file in │ │ clarion ...then goes to dbase and edits then saves that │ │ memo, clarion can no longer read that memo. │ │ R&D: This will require a change to the screen structure, │ │ addition of new driver functions and a rewrite of │ │ parts of the screen library. So this will not be │ │ done until 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0154 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 1/28/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the field worksheet for a file that has groups defined │ │ you cannot move the groups. in 2.1 you could use the +/- │ │ keys to move the groups. in 3.0 you have to move each │ │ field into the group instead of the the group field once. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0425 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/19/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ all of the up arrows and down arrows on the verticle scroll │ │ bar only work one at a time. The same thing happens in │ │ Cshell. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0504 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 3/04/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On the relationship properties screen - the line being │ │ expanded for 43/50 line mode also expands the botton of │ │ the ref. integ box. either need to move box up or choose │ │ next line to expand │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0506 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 3/04/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Go into 43/50 Mode, Select Relations, Change or add a new │ │ one. Look at that stack of Ref. Integs. │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0509 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/05/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Some time ago in this forum there was talk of a Field │ │ Dictionary for CDD3. This would let a developer keep a │ │ catalog of common fields, (Name, Address, Social Security │ │ Number, Phones, Zips, etc.) so that their basic definitions │ │ did not need to be entered every time a new file using them │ │ was built. │ │ If it is, you might also consider allowing edit logic to be │ │ attached to stored fields. That way a date field might │ │ also carry with it the logic to pop up a calendar for │ │ reference or a name field carry with it logic for editing │ │ and/or capitalization. │ │ What we're evolving here is a pragmatic approach to object │ │ orientation (Bruce's analysis of the other kind is right on │ │ the mark). The only problem is that the buzzword generators │ │ are likely to refer to our pragmatic object orientation as │ │ "POO". Oh well! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0510 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/05/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The idea of including standard edit logic to fields │ │ in the database should be included to include setup logic │ │ as well. Since all forms allow both setup and edit code for │ │ entry fields, it makes sense to allow these items to be │ │ defined in the data dictionary. │ │ There should also be a DESCRIPTION field (string 80?) for │ │ each field. This would be used for the DESC attribute, │ │ which now must be defined at the form level. It makes a lot │ │ of sense to allow this to be defined in the dictionary as │ │ well. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0523 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/07/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Put these on the list for the SECOND commercial release! │ │ <g> │ │ 1) The file display area for the Data Dictionary should │ │ display in a tree based on the defined relationships, sort │ │ of like the procedure map, as an option. If there are │ │ multiple roots in the tree, arrange them alphabetically. As │ │ it is now, I can only look at relationships a maximum of │ │ three files at a time. (GrandParent, Parent, Child from the │ │ Parent viewpoint) I end up sketching this out on paper! │ │ 2) This is more of a question: Why doesn't the Clarion │ │ compiler look in the data dictionary instead of the .CLA │ │ files for file definitions when a data dictionary is being │ │ used? That way, I could make a minor change in the data │ │ dictionary and simply recompile, instead of regenning. │ │ Adding fields that are not used in existing applications │ │ would not require a regen of those existing apps, just a │ │ recompile. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0548 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/09/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Dictionary Editor: │ │ a) Add multiple views, │ │ ex: files: file_label,prefix,driver,file-spec,.... │ │ description b) Reduce the number of sub-screens (via │ │ pushbuttons), there is plenty of screen room USE IT. I know │ │ this removes your ability to write a single generic screen │ │ for sections of fields (ex: attributes), but so what. │ │ c) when selecting a key (in relationships [and generator]) │ │ show all information. At least show the field │ │ components.d) Add DEFAULT control for new fields. Ex: I │ │ prefer IMM on for all fields it is a pain to have to change │ │ every fielde) Add macro support, kind of like editor. │ │ (ex:so I can change all fields to IMM) │ │ Either that, or since the data dictionary is held in a │ │ data file, then maybe we could run a LOOP over the data. │ │ Global changes support --hmmm. f) Support the LIKE field │ │ typeg) I like the idea of a field list, especially for │ │ where relationships are involved. Most of the time the │ │ related fields are Identical in each file they appear in. │ │ h) You should be able to ^Tag-^Copy fields from on file to │ │ another. i) Allow two/multiple dictionary windows to be up │ │ at once. -- sort of editor like -- │ │ should be able to copy (block-copy?) between windows. │ │ j) Add default mode support as in open(label,mode) │ │ for reference files that are usually read-only. │ │ k) ADD SUPPORT FOR FILTERED KEYS │ │ this is really a lanaguage or driver level issue. │ │ l) add support for files that ONLY exist as keys │ │ -- whaaaat ? -- │ │ how many times have you created a file where most (if │ │ not all) of the fields are duplicated in a key. │ │ m) at the key level, when a GROUP is listed as a key │ │ component. then show it as a group, with its sub-fields. │ │ In C21 I have wound up defining two keys, on with as the │ │ group and one with the sub-fields so that both │ │ situations could be used in designer (I know there is no │ │ need for the second key at the language level) n) Allow │ │ field definitions to be editted from the key component │ │ listings. o) Allow EXPRESSIONS to be given for initial │ │ values ex: today() │ │ p) Add support for a CENTER attribute to fields │ │ q) Add computed fields (non-stored) that appear as if they │ │ exist in the record. -- ?Avail as key fiels? -- │ │ 1) Add support for foriegn fields (internalized as │ │ computed) in keys !!! This would allow sort orders that we │ │ can't get right now (without reading through the whole │ │ file, putting info into a queue and then sorting the queue, │ │ to create our own dynamic index) --argh r) Add support for │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0700 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/31/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Goldberg Mark 75250,2551 │ │ Hello Everyone, │ │ I would like to make some C3.1 suggstions for the │ │ dictionary. │ │ 1) Support the LIKE command. │ │ should be for fields and for entire files │ │ (except for the file driver and file spec. [see ASCII │ │ thread]) │ │ 2) Allow QUEUEs to be defined in the dictionary │ │ 3) Add a global memory section to the dictionary, not just │ │ in APPs │ │ 4) Add support for computed fields, │ │ by this I mean non-stored fields, that appear as if they │ │ are stored. It would be resonable to limit the │ │ expression for the computation if that is required to give │ │ us the feature. Start with four function math if you must. │ │ 5) Add support for filtered keys. │ │ It is embarassing to not be able to match the power of │ │ Alpha-4. I understand that this will likely be file driver │ │ dependent. │ │ 6) Show key components when given a key selection list box │ │ !!!!! │ │ 7) Show file relationships that point _to_ the current file │ │ 8) Support expressions for the initial value. │ │ ex: today() │ │ ?? add default pre & post edit sources ?? │ │ ?? add default screen pre & post edit sources ?? │ │ 9) Allow a null prompt (as in no prompt) │ │ -- Mark Goldberg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0723 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 4/01/93 │ │ Reported In : 3002 RevisedDate : 1/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have defined a Clarion file in my dictionary with fields, │ │ keys, memos, etc. I then decide that I want this to be an │ │ ASCII file. The keys, memos, and relations are dimmed out, │ │ and a message appears at the bottom of the listboxes that │ │ say "Not Supported"... HOWEVER, if I use the "Generate │ │ Source" option, the keys and memos are generated in that │ │ source! The same goes for generating source in the app │ │ generator. │ │ R & D : This will be addressed in a future release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0779 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/06/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ bruce: │ │ wants to be able to copy a field between files or use like │ │ in dictionary or have a default pool of fields to pull │ │ from. If a field changes, he would want to change it in │ │ one place, not in all his files. │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1122 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/30/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When creating a fields and specifing the entry options; the │ │ fields defaults to the last entry option selected. So once │ │ I select immediate then all my fields from then on are │ │ immediate. Is this by design or mistake? │ │ If by design, lets take a vote ???? │ │ Q & A : This creating field entry option is by design. │ │ Bring this up in the tech support meeting for a vote and │ │ see it get shot down. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1215 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/13/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tony Kirk (AKA) 71222,2520 │ │ Paul, │ │ - In Dictionary, how about having the data-type picklist │ │ point to the data-type already selected for an already │ │ defined field? If the field is defined as a SHORT, for │ │ example, tabbing to that pick-list will still have STRING │ │ highlighted. (It would also be hellacious if pick-lists │ │ would at least bounce to the desired entry by pressing the │ │ first letter.) │ │ - Off the wall suggestion (or food for thought, if you │ │ will): Consider, in a future version or release, the │ │ ability of creating virtual screens which have fixable │ │ portions and don't have to fill the physical screen. For │ │ instance, if I wanted to have 40 lines worth of screen │ │ (window?) which started on row 2 and ended (physically) on │ │ line 24, but I also wanted the top 3 lines of this "window" │ │ to stay put while the rest of it moved around as needed. │ │ This would allow information specific to the record being │ │ edited, for example, to remain visible throughout the │ │ virtual screen scrolling. │ │ Just in case I didn't explain well enough (distinct │ │ possibility), consider a spreadsheet. This spreadsheet will │ │ only display on lines 3 thru 24, with menu and status │ │ lines taking the others at top and bottom. Along with these │ │ lines not used by the actual spreadsheet, you can mark │ │ fixed "titles" which stay put even during scrolling. │ │ Now, I know this is far-fetched and programmatically │ │ far-reaching... but I could have asked for fixed portions │ │ for horizontal scrolling, too <g>! │ │ See ya... │ │ Tony │ │ Q & A : Maybe in 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1216 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/13/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: DOUG ANDREWS 73740,2622 │ │ Found a couple of minor bugs in the 3002 dictionary editor. │ │ 1. I was importing a Clarion file created using 3001 so │ │ that I could clone it to Btrieve. When the dictionary │ │ imports the file, field labels over 12 characters are │ │ truncated. │ │ 2. The clarion file I imported contained some decimal │ │ fields (11,2). When I went to the field editor to change │ │ the field type and scrolled down to PDECIMAL, the editor │ │ keeps changing the field size to (2,2). No biggie, but │ │ annoying. │ │ Thanks │ │ Doug Andrews │ │ 1. That is because the file was created with 3.0 and that │ │ is when the field label gets truncated. │ │ 2. We will look at in the future. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1241 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: │ │ Allow a field's MSG attribute to be entered in the │ │ dictionary editor. Then carry this over as the default │ │ for the screen formatter. │ │ GDF: If implemented, a new template token may be needed │ │ called %FieldMsg. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1254 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Import ability for 2.1 APP files. │ │ Would like to be able to import all files with picture and │ │ field attributes from a 2.1 APP file. │ │ GDF - Good Idea...but, may be in the upcomming APP file │ │ converter and might not want to duplicate the work. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1257 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Change a Picture token in the Dictionary │ │ editor and have a window pop-up to ask if the user wants │ │ this to change the picture throughout the .APP also. │ │ GDF: This is part of the whole propagation issue. Seems │ │ like this would be a REAL tough one to implement because: │ │ 1 - Multiple .APPs may use the same .DCT so the user │ │ may or may not want to change ALL .APP files which │ │ use this .DCT file. │ │ 2 - What if the picture is lengthened!? Then on a │ │ SCREEN or REPORT structure you may either stomp on │ │ another field, go out of the screen boundry, mess │ │ up the report width, etc... │ │ However, some sort of selective propagation from .DCT to │ │ .APP should be implemented and maybe this can be considered │ │ during the design. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1276 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/18/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ 1) The Gray +/- keys should move the fields in the │ │ Dictionary Editor. Othwerwise I'd have to delete and insert │ │ the field all over again at the correct location. │ │ 2) Dictionary Editor/Field Properties/Type: Should be able │ │ to press the first letter of the type, "L" for "Long", and │ │ the cursor should jump to that field type. Moving the down │ │ arrow to select field type slows things down considerably. │ │ But by pressing the first letter, the user doesn't even │ │ have to look at the list. │ │ 3) Dictionary Editor/Field Properties: Why not allow │ │ PgDn/PgUp to page through the various fields? The user can │ │ check each field property much quicker. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1295 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/19/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Plaut 74170,2263 │ │ Must be in list option. │ │ Suggestion: In the dictionary there should be a │ │ flag to initialize the first choice into the field. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1341 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/25/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Timothy Wade 71163,1461 │ │ 1) When I add a field to a screen, I would like to be able │ │ to choose the field type with just the first letter. A │ │ button could be B, not alt-B. │ │ 2) In field properties windows, it would be easier to be │ │ able to select the data type with the first letter, rather │ │ than hitting down arrow down arrow down arrow down arrow │ │ down arrow.... │ │ 3) I hit F5 to save my app and bring up the data dictionary │ │ just to remind myself what I named some variable. I'd love │ │ to have a hot key to peek into Data Dictionary information │ │ from the application screens. Then, of course, it │ │ would be wonderful to be able to point-and-select those │ │ field names onto screens and reports. │ │ 4) I would really like to have ctrl-enter or some other key │ │ combination _consistently_ finish what I'm doing. One of │ │ the places it doesn't work is on the local-procedure field │ │ worksheet. │ │ 5) Activate the insert key on the Procedure Calls list box. │ │ 6) Alerting the escape key on the ShowWarning procedure │ │ would increase its usefulness to those of us who use it in │ │ our app's. (As in, "Warning, you are about to do something! │ │ Press Escape to prevent this catastrophe") │ │ 7) I really like the browse--it's efficient and its easy to │ │ code. there are times when I really miss 2.1 tables. I │ │ realize mult-line tables would require major work, but │ │ there are times when they'd really be great to have. │ │ 8) I (and others I've spoken to) often would like to have │ │ locators that work they way they did in 2.1, as an │ │ alternative to the current 3.0 locators. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1349 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/26/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 │ │ In the Data Dictionary, it would be nice to be able to also │ │ specify a relationship as 1:1 rather than just 1:Many or │ │ Many:1. │ │ As presently implemented, specifying a 1:Many when in fact │ │ a 1:1 exists, means that GET(File,Key) is not generated for │ │ looking up related data when building a Queue for a list │ │ box. The alternative is to turn this around and specify a │ │ Many:1. This generates the GET(File,Key) but renders the │ │ Update/Delete Constraints inappropriate. │ │ Being able to check for a 1:1 value in %RelationType would │ │ allow the appropriate Template changes to be made for │ │ generating the proper code. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1389 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/31/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Why not allow me to change the order the files appear in?? │ │ Move is dimmed. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1420 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/02/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ When defining the Referential Integrity fields in the │ │ dictionary, it can't link to the child field using a │ │ constant or a variable. For example. If I have 2 files, │ │ Student & Notes. │ │ (One To Many Relationship) │ │ ===STUDENT FILE==== ======NOTES FILE===== │ │ (No Link???) NOT:Note_Type X(3) │ │ (Key not set correctly) │ │ Student_Id X(10) ----> NOT:Note_Id X(10) │ │ I would like to define the Parent to Child link as: │ │ 'ST' ----> NOT:Note_Type │ │ ('ST' denotes Student Notes) │ │ STU:Student_Id ----> NOT:Note_Id │ │ (Finds note for this student) │ │ or │ │ GBL:varname ----> NOT:Note_Type │ │ (Local/global variable) │ │ STU:Student_Id ----> NOT:Note_Id │ │ This would give the referential integrity much more │ │ flexibility. True, the developer would have to assign the │ │ variable the correct value during the form setup, but it's │ │ much easier this way than forcing the developer to write │ │ his or her own referential integrity code. And if the │ │ variable does not exist in the dictionary, a compiler error │ │ will flag it as a bad link, which is the correct thing to │ │ do. │ │ You may also want to add a filter to help select the child │ │ records. It's not always possible or practical to have a │ │ key in the child file that will uniquely find the records │ │ to delete/change. (The child key may select too many │ │ records for its key or the proper key field may not exist.) │ │ Example: If a lookup field value changes in the States file │ │ from "AX" (originally mistyped) to "AK" (for Alaska), does │ │ it mean I have to add a State key to my Address file? In │ │ 3002, if I want ref. integ. to work, I do! Even though I'll │ │ never use this ADR:State_Key for anything else. A filter │ │ would solve this problem and will eliminate the key. Sure │ │ this filter may not be fast, but since this "link" isn't │ │ used that often, speed isn't that important. A ref. integ. │ │ filter will ELIMINATE a lot of unecessary key and disk │ │ space. │ │ P.S. If this can't be implemented, I will have to dust off │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1424 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/02/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 │ │ A nice enhancement to the Dictionary for future versions │ │ would be something that is essentially a "code point" which │ │ gets implemented as an "Edit Embed" such that one's │ │ Business Rules of Integrity for any given field could be │ │ entered ONCE rather than on each form in every App using │ │ that field. │ │ In addition, such an implementation might eventually be │ │ able to be hooked into the "triggers" of the newer file │ │ formats - v6 Btrieve, SQL Server etc. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1432 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/03/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 │ │ I know that I can work around the mutiple lookups to one │ │ file from many fields in one record with hand written code │ │ and this is fine but since the 3.0 Report Writer will use │ │ the .DCT file to establish relationships between the │ │ files how will I get the lookups to work beyond the first │ │ one. This is kind of crucial since end users will want to │ │ use the Report Writer to make reports utilizing the fields │ │ in the Lookup file. If you report writer will not handle │ │ the multiple fields from one record accesing mutliple │ │ records in a the same Lookup file then the purchasing of │ │ report writers for end users is kind of useless. │ │ Again I would hope the capability that was present in 2.1 │ │ Report Writer would not be lost in 3.0 Report Writer. │ │ Please pass this on to R&D. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1575 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/17/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ It would be nice to have the LIKE field type in the data │ │ dictionary. This field type would then prompt the user for │ │ another field in the dictionary to be LIKE. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1655 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tony Kirk (AKA) 71222,2520 │ │ Just a question/suggestion for 3.0's Dictionary... │ │ What's the chance of getting the FILES' prefixes to be │ │ displayed with the files, either prior to or immediately │ │ following the file label? I know the dictionary will tell │ │ you when you have duplicated a prefix, but... │ │ Just a thought... │ │ Thanks, Tony │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1719 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/05/93 │ │ Reported In : RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 │ │ When R&D is working out a method of listing datafile │ │ definitions I suggest they modify the Cla2.1 approach as │ │ follows: │ │ When Ctrl-L is pressed, have a dialog box that │ │ asks for * All Files/Current File Only │ │ * Brief/Complete Listing │ │ The Brief listing would contain only the │ │ FieldName, DataType, DisplayFormat, and Description; The │ │ Complete listing would contain _all_ info ala Cla2.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1767 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/09/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ When I delete relationships in the Dictionary, the file │ │ schematic is not updated correctly. It will leave a blank │ │ line in the schematic where the secondary file was located, │ │ so when it's compiled, I'll get a compiler error. │ │ (The syntax for the GET(file,) is missing a parameter). To │ │ fix it, I have to go into each procedure that has this │ │ blankline in the schematic and delete it manually. This │ │ should befixed. │ │ R&D: This will be addressed at a later release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1809 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 7/14/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ For importing files the relationships do not come with the │ │ files that you import for good reason. But If by chance │ │ somebody is doing a group project they will each have to do │ │ there own dictionary then pull them together for one app if │ │ they wished to have just one exe. THE SUGGestion was made │ │ that maybe the tagging of files to copy over or importing │ │ an entire dictionary. Both of these options would be so │ │ that importing the relationships would also happen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1939 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 │ │ This type of Relationship was no problem in 2.1 and won't │ │ bein 3.0 if I don't care about having the relationships def │ │ ined in the dictionary, but if the EVENTUAL end user │ │ Report Writer is going to used the Data Dictionary I may run │ │ in to some problems. In the 2.1 RW I could establish │ │ these relationships with little problem, (i.e. no second │ │ Lookup file or joining file was needed) so I would hope that │ │ 3.0 would eventually support this type of relationship. │ │ This is very Important to me and to you │ │ (Clarion) because I currently ship report writers with every │ │ program(100 - 200 / year). And some of the bigger │ │ businesses (GM, FORD, NASA, Martin Marietta, etc..) that use │ │ the current report writer get some exposure to │ │ Clarion that they wouldn't otherwise. If 3.0 can't support │ │ these types of relationships in the report writer (and │ │ therefore the Data Dictionary) then I will have to stop │ │ buying Report Writers and consider moving to another │ │ developement platform, which I don't want to do. Please │ │ see if R&D can look into allowing these types of │ │ relationships because I not only use them in the example I │ │ listed but I also use them in 2.1 to allow │ │ consolidated Lookup Files(i.e. I turned what was 38 │ │ differnet lookup files into what is now 3 Lookup Files). I │ │ would hate to think of going back to the amount of overhead │ │ and maintainence involved in all those files. I'm pretty │ │ sure John Herron used a similar technique, he gave me the │ │ method for defining the relationships in the 2.1 RW, so my │ │ methodology can't be that far out in Right/Left field, and │ │ even if it is I don't think you should force me (and │ │ possibly Barry, he uses consolidated lookups) to create │ │ all those extra files. │ │ Thanks for listening, and I hope │ │ R&D &/or Bruce may be accomodating on this one. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1949 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tim Mirande 76011,3112 │ │ I think that the idea of the centralized data dictionary │ │ iswonderful. It will allow us to define data once and once │ │ only. We simulate this now (2.1) with liberal uses of │ │ INCLUDE statements. However, here's the rub. The data │ │ dictionary only permits one line of description. │ │ This is sufficient space to descriptively name the field, │ │ but doesn't give sufficient space to 'self document' the │ │ field. │ │ Example: Field Description = 'Status Code'. │ │ Currently, we indent two spaces and describe the status │ │ codes on as many subsequent lines as appropriate. Just as │ │ an aside, we currently average about 3.5 lines of additional │ │ lines of explanation for each field entry. │ │ What I am suggesting is that we be given │ │ a MEMO for each field -- in addition to the description │ │ field. Without this, we will still have to document this │ │ information somewhere supplementary, which always has the │ │ potential (and in my opinion, tendency) to become out │ │ of date. This kind of information should really be in the │ │ data dictionary. If you think about it, how effective would │ │ Webster's dictionary be with only one line of explanation │ │ per word? As always, thanks muchly <g> │ │ for your efforts. │ │ Tim Mirande │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2096 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/10/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests that Column heading and Default Prompts, │ │ use the same case as the field name. │ │ Invoice_Number should be Invoice Number no Invoice number │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2246 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/27/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 │ │ In an app I'm working, on I choose to store the NAME() file │ │ attribute in a control file. This file is called │ │ 'Control1'. When I generate and compile my app, I get two │ │ undefined variables, one called Ct1:BasesPath (this is the │ │ NAME() attribute for the 'Bases' file) and I get │ │ an undefined var. called Ct1:ConfigPath (this is the NAME() │ │ attr. for the 'Config' file). The problem is that when │ │ generate places the file structures in the source code, the │ │ file structure definitions are put in the source │ │ in Data Dictionary alphabetical order. The two undefined │ │ variables are from the NAME() attribute variables defined in │ │ the two file structures that preceed the file structure for │ │ the control file. This is where the │ │ alphabetical order comes into play. │ │ I can work around the error by │ │ going into the generated code and use the text editor to │ │ move my Control1 file structure to the very first file │ │ structure. When I do this the variable is then properly │ │ defined BEFORE the compiler encounters the │ │ variable name. This seems to be a bug since there are a │ │ total of eleven files that have variables for NAME() │ │ attributes and only these two cause me any problem. │ │ The │ │ question is, since the dictionary only permits alphabetical │ │ order. Should I change the name of my control file to make │ │ sure it is alphabetacally before all the others OR is this a │ │ bug in the compiler? Is there another method I │ │ could use to avoid this problem without having to modify the │ │ generated code before each compile? │ │ -Paul │ │ From Greg_w: I'm logging this as a suggestion. The │ │ suggestion is to be able to rearrange the order in which │ │ the data files are located. Thereby moving there order in │ │ the generated code. The above problem is just one reason │ │ to have this feature. Also, 2.1 let you do it<g>. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2247 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/29/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests that we check for the occurence of a number │ │ as the first character of a file name and alert the user. │ │ Currently you can create file names with numbers as the │ │ first character and you don't find out that its invalid │ │ until after you've defined your appication and try to │ │ compile it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2257 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/30/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user to be able to enter a filespec like │ │ the following: │ │ File Spec: glo:filepath & 'contacts.dbf' │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2274 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/31/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ I am having many problems with the field lengths in the │ │ application generator. My problem is if the maximum key name │ │ is 255 characters then every entry field that takes a key │ │ name should be 255 characters in length. Most are 10 or 20 │ │ characters in length and this can be really limiting. │ │ Fred Schmitthammer │ │ Professional Practice Systems, INC. │ │ (310)804-7674 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2475 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/27/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: George Williams 70436,1643 │ │ I agree...CFIL is definately needed in cdd. │ │ If you have several versions of a program scattered │ │ throughout many users, it is easy to loose track of which │ │ version they are running. Doing an upgrade using CDD's │ │ method requires that a copy of the description of each old │ │ file be kept and used when doing the convert. with CFIL, │ │ the only file defination that is needed is the most │ │ current.A MUCH better method. Also a 2.1 style CSRT would │ │ be nice.... │ │ From Greg_W: Many users have made this suggestion │ │ in the past and I don't see any "official" suggestion so │ │ I'm adding this one. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2993 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jon B. Bushey 71521,2267 MSG#:41534 │ │ We REALLY need a way to share the .dic file. In the old │ │ Clarion users with reporter could share the 'dictionary'. │ │ Now we have taken a step back. If a programmer has the │ │ generator up - nobody else can access the dictionary. This │ │ problem is a killer AND there is no reason. The │ │ dictionary does not need to be modified from generator - │ │ why is it locked? Thanks, Jon B. Bushey │ │ QA: The DCT is not "Locked" it is OPENed therefore it is │ │ not shareable! This is not a multi-user development │ │ environment! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3014 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 11/10/93 │ │ Reported In : 3007 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Currently when editing a DCT, if I have multiple copies of │ │ a datafile, that MUST stay in sync, there is no methdo to │ │ copy over (ie. REPLACE) that file's definition with another │ │ via a Copy. IOW, I have no method for replacing a datafile │ │ definition w/ deleting the current and importing or copying │ │ it. │ │ Case: Main DCT resides on Network, programmers use a local │ │ DCT while programming. Project Mgr Updates DCT. The │ │ programmer must either: │ │ a) Overwite his DCT. If he does this thru DOS Prompt │ │ he is HOSED when he return to the APP and has to access the │ │ DCT │ │ b) Open the DCT and delete the Files he needs to │ │ re-import and then Import them │ │ c) not get the changes until a later time. │ │ This could be a big winner wh all of our users. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3022 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from end user - wants to be able to use the LIKE │ │ definition on a field from the dictionary editor │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3268 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/09/93 │ │ Reported In : 3007 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Import from 3.0 DCT file only allows you to select ONE FILE │ │ this means you can't get related files with their │ │ Relationships intact ???! Come on. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3599 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 1/25/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice to be able to reorder the files in the │ │ dictionary so that they are not in alphabetical order. If │ │ I were to have a datafile with the paths of my files, (file │ │ specification) it needs to go first in the list of files. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4100 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/11/94 │ │ Reported In : 30071 RevisedDate : 3/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gregory C. Bailey 76615,1350 MSG#:59700 │ │ Since the BUILD feature is useless for btrieve files. Why │ │ not change the Convert file option to look for the output │ │ file being a btrieve file and not including the BUILD │ │ command in the generated program. │ │ From Greg_W: Maybe we could have the code generate a prompt │ │ for whether to BUILD the file after the conversion is │ │ performed (just an idea). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4145 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Robert E. Hoag 73201,2607 MSG#:60552 │ │ I have a field declared as byte that has a 'must be in │ │ list'validity check. Radio buttions are created on a │ │ screen field, along with other variables that are │ │ declared as strings (with 'must be in list'). I have │ │ added a button that sets these fields to a default │ │ value, by making assignments the variable, then │ │ using DISPLAY. All of the radio buttons show the default │ │ selection except for the one that is declared as a byte (2 │ │ integer byte). Is this a bug? What's going on? │ │ Suggestion from Greg_W: Disable "Must be in List" for any │ │ field type other than STRING, since the option structure │ │ created for it's implementation only works with STRINGs. │ │ Either that or add something to the on-line help │ │ explaining the fact that "Must be in List" creates an │ │ Option structure that only works for STRINGs. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4189 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick D. Williams 72262,2720 MSG#:61815 │ │ 1)When Importing from another Dictionary the user can only │ │ import one file at a time. Why are you not able to mark │ │ several files to be copied, the same as you can when │ │ importing files from a 2.1 APP file? │ │ 2) When working in the Dictionary Editor on the Main Menu, │ │ it would be nice to have a locator field for each topic. If │ │ the user has a lot of files in the dictionary, it can be │ │ anunwanted hassle to move up and down the list to try │ │ and find the file/field/key wanted. │ │ 3)A locator field on the import from another Dictionary or │ │ aClarion 2.1 APP file. This would also save valuable time │ │ andsave on headaches looking for the file(s) that the user │ │ wants to import. Especially if the list is extremely │ │ long. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4278 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Will Fastie 76655,1566 MSG#:63346 │ │ I'd like to be able to import the entire contents of a │ │ dictionary in one fell swoop, not a file at a time. In │ │ otherwords, a merge of two dictionaries into one. Perhaps │ │ this capability already exists and I just haven't found │ │ it. I've been doing it one at a time. Will │ │ From Greg_W: How about something like importing 2.1 │ │ procedures where you can import all or tag the ones you │ │ want. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4554 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/26/94 │ │ Reported In : 3008 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Date: 22-Apr-94 10:50 EDT │ │ From: Will Fastie [76655,1566] │ │ Subj: #67852-Multi-user Comments? │ │ I always thought that method of opening file should be in │ │ the dictionary as a > choice... │ │ This is a very good idea! The dictionary should have the │ │ default open mode to be used if one is not specified in an │ │ open statement. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4636 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/10/94 │ │ Reported In : 3008 RevisedDate : 5/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Show the file prefix at the top of the screen whenever │ │ displaying the filename and description. │ │ 2. Provide a summary screen which shows prefixes, │ │ filenames, descriptions, driver name, and record lengths of │ │ all files defined in the dictionary. This │ │ function could also show total fixed file overhead and the │ │ total amount of storage required for each record (including │ │ all keys, etc.). It might be interesting to have a what-if │ │ worksheet here where the developer could key in │ │ estimated records counts (which you would save) and have │ │ the dictionary editor estimate total capacity required to │ │ store that many records. │ │ 3. Show the total record length whenever the cursor is in │ │ the Fields list box. │ │ 4. I suggest that the dictionary editor be equipped with a │ │ broad range of defaults, primarily for file definitions. The │ │ most important default is the driver type. If no driver │ │ type was declared for a specific file, the file │ │ declaration would use the default type. │ │ This enhancement would allow bulk changes to a dictionary │ │ if a developer decided to use a different driver or just │ │ wanted to experiment. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4802 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 6/10/94 │ │ Reported In : 3009B RevisedDate : 6/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Eliminate double-error on dictionary line. Make the popup │ │ button required, and only error check when button is │ │ completed. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4887 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 6/29/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggestion: When copyuing a field in the dictionary, │ │ the column heading reverts back to reflect the label. The │ │ user would like it to reflect what it was when it was │ │ copied. For instance, if you change the column title from │ │ phone to phone number, this should be reflected when you │ │ copy. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4893 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/30/94 │ │ Reported In : 3009 RevisedDate : 7/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Dictionary │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The field and file descriptions do not get put into the │ │ generated code. This is │ │ a big problem even though it seems like no big deal. The │ │ dictionary editor │ │ becomes a kind of black hole - you can type all the │ │ description you want and it │ │ goes no where. A number of Clarion programmers have │ │ mentioned it at DevCons │ │ and at user groups. I need it for CLADOC3. Jon B. Bushey │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0852 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 4/08/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Would like to see some help in the environment which lists │ │ the available hot-keys. Without having to go to the │ │ pulldown menu to find out what they are. Also would like │ │ the hot-keys listed in the utilities. │ │ For example: in the screen formatter would like to have │ │ help which lists Ctrl-F, Ctrl-L, etc... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1115 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 4/29/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice if MEMORY.DOC contain information on │ │ example settings under DRDOS6.0. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1154 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 5/07/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When the tutorial manual get updated it would be nice if │ │ there was an example of converting a dbase file (AnyFile) │ │ toa Clarion file format. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1228 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It was suggested by a user that the tutorial manual be │ │ expanded to include example and use of all the templates as │ │ well as giving example of more advance topics, such as, │ │ column report, an idle procedure to display time, etc. It │ │ was also requested by this user for more detail expanation │ │ on why thing are done in this manner not just how. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1443 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 6/04/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice if the tutorial manual had an index. I │ │ would of like the tutorial manual to walk cover all the │ │ template and what thay are use for in CDD. I would like to │ │ have seen an exsample on how to dislay a logo screen. I │ │ would of like have an example on placing and using a │ │ locatorfield on a browse procedure. I would of like the │ │ tutorial to cover how to use thin borader. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1698 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 6/30/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In clarion version 2.1 the various command keystroke ( for │ │ such things as toggling the case of character, centering, │ │ and many other feature) were well documented in the printed │ │ material ( page 5-75+ in the utulity manual) and in the │ │ on-line help. This information is not documented in 3003. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1708 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 7/01/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Add the following example to the Clarion Gui Kit │ │ Documentation: This example handles all the differant type │ │ of graphic mode: │ │ Global - Data Section │ │ EGA Equate(121) ! EGA Equate Value │ │ VGA Equate(89) ! VGA Equate Value │ │ SVGA Equate(87) ! SVAG Equate Value │ │ Global - Setup Program │ │ Case Graphic(0) ! Find graphic mode for GUI Kit of EGA │ │ of EGA │ │ SetGraphic(121) ! Force EGA mode of VGA │ │ of VGA │ │ SetGraphic(89) ! Force VGA mode of SVGA │ │ of SVGA │ │ SetGraphic(89) ! Force VGA mode for fast executio │ │ else │ │ SetGraphic(90) ! Force Text mode END LoadGUI │ │ END │ │ Load GUI ! Set Graphic mode, using GUI │ │ ! library │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1904 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 7/19/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I think we should put a recommendation in MEMORY.DOC about │ │ using consistent versions of HIMEM, SMARTDRV, and EMM386. │ │ It is a know fact that using various versions will cause │ │ sporatic reboots/ xtraces. ie, │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1941 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Euan Hill 100143,1660 │ │ I started by working right through the tutorial. I loved │ │ theproduct but found one or two ove rsights that should be │ │ corrected when you have a chance, for the benefit of │ │ other new users: 1. p.24 fig 1-21 The buttons have changed │ │ on the Global Sett ings Window Not important. You are │ │ probably already aware of this. Next printing. 2. │ │ p.53/54 The ShowPhones procedure . This is │ │ important. Following the present instructions in t he │ │ text, the procedure will not display any values from │ │ the IntlPhone field and there is no way for a new user to │ │ solve this problem. A List box worksheet won't let │ │ yo u superimpose one field on top of another the way you │ │ c an with the FORM worksheet used with the │ │ UpdatePhones p rocedure (p.55/56). This is liable to │ │ irritate an impatient new user and leave her/him │ │ feeling uneasy about template programming. I haven't worked │ │ out the answer yet and if you have a moment I'd be │ │ interested in seeing your solution. Incidentally it would │ │ probably be a good idea to add a reminder on p.56 to │ │ re-order the fields after completing the │ │ UpdatePhones window worksheet. If you dont you can find │ │ that IntlPhone numb ers cant be input. This is because │ │ the idea of physically superimposing prompts and │ │ numbers can be a bit confusing the first time round. │ │ 3. p.67 Same problem with the PrintAllCards procedure. The │ │ Body band field entries make no provision for IntlPhone. │ │ 4. p.70 It would be a good idea to add an explanation to │ │ the discussion of the SelectContact procedure as to how │ │ you change the size of a List box as you are likely to be │ │ presented with a too small box at this point and it │ │ can take some time to figure it out. │ │ 5. p.74 Unimportant. For next printing. You now press │ │ the Ok button and not the Exit button. │ │ 6. p.79 Again for next printing. Code example. Empty │ │ parentheses dont seem to form part of the procedure calling │ │ syntax as suggested by the example. │ │ I had made all the changes to the 0393 printing of │ │ the Tutorial book which were advised in CHANGES.DOC, │ │ CORRECTS.DOC and README.DOC prior to working through the │ │ tutorial. The tutorial is a good one and enjoyable to use. │ │ The only addition I would like to see would be a │ │ REPEAT field example to work through. I feel this memo is │ │ really a bit of a gilding the lily exercise - trying to help │ │ you make a great product better! │ │ To finish, as Secretary of the British │ │ Computer Society's Modular Languages Special Interest │ │ Group, I would like to extend my compliments to Bruce │ │ Barington for his marvellous essay on the Origins of the │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2016 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/30/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 │ │ I'ld like to add a suggestion to the documentation. In 2.1 │ │ there were I believe five annotated source code examples. I │ │ found them to be some of the best things for learning the │ │ Clarion language. I would like to see some of these for │ │ each of the templates. It sure would help understanding all │ │ thedetails of the new structures and how the source entry │ │ points can be used.. │ │ The new tutorial was a big help. It might be nice to │ │ add to it with other variations. I can appreciate the time │ │ it takes to write the tutorials and the work required to │ │ publish them. Perhaps a less formal approach could result │ │ in some additional tutorials at less cost. After you │ │ go through the first tutorial you might not need such a │ │ keystroke by keystroke approach. │ │ Paul │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2783 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/26/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Brooks 71234,1534 MSG#:38608 │ │ I get the following error in the Halt Window ..Filename:33 │ │ Please recommend that Clarion print some documentation on │ │ the operation and interpretation of the Program Halt window. │ │ There was enought information in the window to allow │ │ me to solve the problem, but no documentation to tell me │ │ how to read it. thanks again. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3020 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the template documentation it would be nice to have some │ │ indication as to which built-in symbols are multi-lined │ │ symbols. │ │ users are trying to use template code to assign a user │ │ defined template symbol to a multi-lined template symbol │ │ which is not allowed - but there is no notation as to which │ │ are multi-lined │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3184 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/01/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Asa Dean 75600,3421 MSG#:44603 │ │ Per the "User's Guide" page 4-30 is a Go ReStart command, │ │ but the program doesn't support it. I've seen nothing in │ │ the README and DOC files. Am I doing something wrong? │ │ Asa... │ │ Go Restart in no longer an option in VID - should be │ │ included in corrects or somewhere. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3367 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 12/21/93 │ │ Reported In : 3007b RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ statements that must have the file open should be indicated │ │ in the manual under each statement as 2.1 manuals indicated │ │ that they would be opoened automatically │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3674 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: George Hale 72567,2653 MSG#:52247 │ │ Is there ANY possibility of making a file available for │ │ download while we wait for new manuals? The tutorial is │ │ especially a problem. I started trying to make all the │ │ updates in the manuals and realized what a mess I was │ │ making; then I tried cutting and pasting -- even │ │ bigger mess, then I tried just noting which paragraphs │ │ changed, in order to be able to reference back and forth -- │ │ THAT's a pain in the rear, too. I'd surely appreciate a │ │ chance to print out a clean set of documentation and put in │ │ a loose-leaf folder, for now... There is so little bound │ │ documentation that came with the product that re-printing │ │ it ourselves, in this case, wonot be a lot of trouble. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3725 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 2/08/94 │ │ Reported In : 30071 RevisedDate : 2/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Change POOLLMT.DOC in reqards to ROUTINEs and how they are │ │ NOW (as of 3007) treated by the compiler. Since ROUTINE's │ │ which were the main cause of POOL limit problems are now a │ │ thing of the past. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4014 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/02/94 │ │ Reported In : 30071 RevisedDate : 3/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 MSG#:57656 │ │ I have a suggestion/request for 3008 or sooner. How │ │ about a chart (grid) with the available file drivers on │ │ one axis and the features on the other. This would show │ │ at a glance which drivers support which features. For │ │ example, │ │ Clarion BTrieve dBase III+ │ │ dBase IV Paradox │ │ ADD x x x │ │ x x POINTER x │ │ ? POSITION x x x │ │ x x │ │ You could also use a number instead of an x if │ │ there is a need for a special note for that │ │ feature/driver combination. This would sure make conversion │ │ between file formats a lot easier than it is now. │ │ Thanks, │ │ Joe Bouterse Creative Solutions, │ │ Inc. Indianapolis, IN │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4347 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/11/94 │ │ Reported In : 3008 RevisedDate : 4/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Martin Wehlou (Cactus) 72047,2444 MSG#:63948 │ │ While on the subject of docs & help <g>: can't seem to find │ │ a language quick reference in the cdd 3 online help; │ │ something akin to the language quick ref in 2.1 online │ │ help, I mean. I found that one *extremely* useful, since │ │ I'm totally incapable of remembering the order of the │ │ parameters in stuff like "SUB()", "FORMAT()", "INSTRING()" │ │ and similar nifty extravaganzas. │ │ Would it be too much to ask...? It's not │ │ high-priority in any way, but it sure would be nice to │ │ have. │ │ Hmmm... actually I can add that to │ │ the help text myself, can't I? (Haven't tried.) Except it │ │ gets clobbered with the next update, of course. │ │ -- Martin [Cactus Computing │ │ bvba - Belgium] │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4657 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 5/12/94 │ │ Reported In : 3009 RevisedDate : 5/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ You can only zoom in on a Topic in Column 1 only. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5094 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : J DateReported : 6/08/94 │ │ Reported In : RevisedDate : 6/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Tutorial Two example demonstrating two body bands with │ │ print filters has insufficient data, may be confusing to │ │ customers since only one of the body bands prints. i.e. │ │ data file needs some Customer records which are NOT from │ │ Florida. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5182 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion for documentation on Display Statement │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ As I recall from reading other messages, I wasn't the only │ │ one having missed the documentation on 'Smart displays'... │ │ >>I'm not sure, possibly in one of the DOC files that │ │ shipped with 3007.2. I'm pretty sure that 3007.2 was the │ │ release that this "smart" displaying of fields │ │ was introduced.<< │ │ I just looked, and searched for 'smart' and for 'display' │ │ in all the likely .DOC files (README, CHANGES, CORRECTS, │ │ even DRIVER...) - case INsensitive, of course. Can't find │ │ it (the strings do show up here and there, not the │ │ combination). If it's there, it's bedtime <g>. │ │ Can we have that documentation for the next (interim) │ │ release, please? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5272 │ │ Product : GUI Duplicate No.: 0 │ │ Reported By : BN DateReported : 8/17/94 │ │ Reported In : 3009 RevisedDate : 8/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Suggestion for the documentation │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It appears that GUI disables certain screen attributes, for │ │ example, the FALL, WIPE, ect attributes for the screen │ │ do not seem to have any effect at runtime. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5294 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/22/94 │ │ Reported In : 3009 RevisedDate : 8/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Missing files/extensions in Documentation │ │ Section │ │ Documentation │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Following is a list of File names/extensions that could be │ │ added to the User's Guide for 3.1. │ │ 1)Code.$$$ -file generated when xtrace during code │ │ generation │ │ 2).$$$ -created by overlay loader/protected mode │ │ 3)Errorinf.$$$ - │ │ 4).ERR - Compiler errors │ │ 5).INC - Include file used in Templates │ │ 6).INI - Configuration file mentioned on B-1 │ │ 7).MEM - Clarion memo file │ │ 8).TPX - Template file │ │ 9).SWP - │ │ 10).LOG - Logout file │ │ 11).TR$ - Logout file │ │ 12).RUN - Created by RUN statement │ │ 13).OVL - │ │ 14).DBT - dbaseIII memo │ │ 15).SES - Editor.ses │ │ 16).DBF │ │ 17).D$$ - temporary dictionary file │ │ 18).R$$ - temporary report writer file │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4280 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : J DateReported : 4/01/94 │ │ Reported In : 3007 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ DOS Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests an error be generated when unsupported │ │ functions are used, i.e. HOLD │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0210 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestion By End User: │ │ When exporting to a file the file name should default │ │ to the last one used. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0211 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestion By End User: │ │ Under options there should be the option for ruler bars │ │ as in 2.1 │ │ Answer: This suggestion will not be placed in the 3.0 │ │ editor. This may be addressed in a later release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0974 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 4/10/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Shouldn't "Undo" be called "Undelete" since all that it │ │ could do is undelete a previous CTRL-D? I assumed that an │ │ "Undo" would delete backspaced text and CTRL-END'ed text. │ │ Q & A : No change yet at this time. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1131 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/03/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Thomas D. Stevens 71726,367 │ │ Am I missing something here? To run a macro, I have to │ │ summon the Macro Play function, and then select the macro? │ │ Whatever happened to the CEDT macro facility, which worked │ │ well, or even the TS macros? Wazzup? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1218 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/13/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: DOUG ANDREWS 73740,2622 │ │ Two minor editor bugs. │ │ 1. If you mark a portion of several lines of text in block │ │ mode, and press the END key, the block does not move to the │ │ right of the longest line in the marked block. It used to │ │ 2.1. │ │ 2. If you put the cursor on a line that only contains a │ │ period, say period is in col 5 and cursor in col 50, then │ │ try to use the plus or minus keys to shift the period, most │ │ of the time it won't move. Sometimes it will move, but only │ │ one way. │ │ 3. I have seen other notes, so add me to the list of │ │ people that would like something done about that macro play │ │ function. It's cumbersome to the point of being useless. │ │ Thanks │ │ Doug Andrews │ │ 1 & 2 are Fixed │ │ 3. Version 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1576 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Advantage Software 100116,3350 │ │ L.S. │ │ one of our clients would like to be able to load any │ │ sourcefile that was recently compiled with errors, and │ │ being able to jump with Ctrl-E to the errors in this │ │ sourcefile first, as opposed to another sourcefile which │ │ happened to be compiled earlier. This means: being able to │ │ 'jump into' the errorlist for a specific sourcefile, │ │ continue the errorlist from there (into following │ │ sourcefiles with errors), and at the end of the errorlist │ │ jump to the first sourcefile. │ │ This was the way Ctrl-E behaved in the CPD 2.1 editor, │ │ and he liked it. We tend to agree with him. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1756 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/09/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Thomas D. Stevens 71726,367 │ │ >>> Also, I like to pop in and out of "Zone Insert" mode. H │ │ ow about adding a hot key so I don't need to wade │ │ through menus to achieve this? │ │ >>> I use CtrlL for this and it is very effective. │ │ I think you missed my point on this one ... Ctrl-L │ │ togglesbetween block and line modes. │ │ What I want is a toggle for Zone Insert (used to be │ │ Ctrl-Z in 2.x). This option is currently toggled from some │ │ obscureeditor menu, and has no hot key. │ │ Q&A: Currently I don't think there is a hot key │ │ available for Zone Toggle. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2049 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/05/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User says.... │ │ Every other text editor and wordprocessor on the planet │ │ uses Ctrl_home to go to the first line in the file. Clarion │ │ uses it to erase the current line. He would like this │ │ changed. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2333 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 9/16/93 │ │ Reported In : 3005B RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when creating a macro -=- ctrl k is pressed │ │ it then asks for the keystroke that you want for this macro │ │ after you type that key it brings up a screen for │ │ description..... If you are going to bring up a screen │ │ for the description anyways why not bring it up for the │ │ entry of the letter that will play the macro????? │ │ The Suggestion here is to bring up that screen for both │ │ fields. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2559 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 10/05/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User wants the gray * to be an asterick instead of a space │ │ in the editor. This is a left over from 2.1. I'm not sure │ │ of its usefulness. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2678 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/18/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Wayne Eggleston 73777,607 MSG#:36528 │ │ Is there any way to set the Insert/Overwrite mode default │ │ in the editor? It always defaults to Overwrite which is │ │ getting VERY frustrating! │ │ From Greg_W:I duplicated this problem and it is a duplicate │ │ of bug#327. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2893 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/03/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 MSG#:40100 │ │ Loading editor costs a lot of time. │ │ I am impatient and start typing Ctrl-S (for search) and │ │ some text. It is annoying to find out that, once editor is │ │ loaded, part of my text is typed into my document. │ │ I know, I know, it is my fault and I am to impatient. But │ │ ifpossible and not to much trouble, please don't clear the │ │ keyboardbuffer when Editor is ready. It would enable me │ │ and many others to start typing during the loading time of │ │ Editor. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3343 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 12/17/93 │ │ Reported In : 3007 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Chromacoding (the use of color to highlight syntax) is │ │ becoming more common in commercial editors. I think that │ │ for v3.1, we should consider on-the-fly syntax │ │ highlighting,showing comments and OMITs (perhaps in red), │ │ language statements (perhaps in green), text or │ │ constants (perhaps in red, also), sectional separators │ │ (e.g. CODE, in blue), etc. This would be very helpful in │ │ locating code as well as highlighting (no pun intended) │ │ the simplicity of the Clarion language. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3743 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mike Hanson, BoxSoft 73234,1447 MSG#:53565 │ │ Hi! Just a wish that I've mentioned a couple of times, and │ │ it shouldn't be too tough to implement. With the advent of │ │ 3.0, the interface designers at Clarion decided that some │ │ people working with the Editor would like to mark blocks │ │ for operations before actually deciding which operation to │ │ perform (ie: the "Mark Block First" option). This is not a │ │ problem, as it is an option. The problem is that the Ctrl-B │ │ key was stolen for this pursuit, and Ctrl-B's functionality │ │ was moved to Ctrl-L. │ │ I am requesting that you treat Ctrl-B as Ctrl-L if the │ │ "Mark Block First" option is disabled. The main reason I │ │ want this is that I normally let my fingers hover over │ │ Ctrl-C and Ctrl-B, while maneuvering with the cursor keys. │ │ By forcing me to use Ctrl-L, I must repeatedly │ │ return my hand to the home row because I continue to forgot │ │ to hit Ctrl-L before heading off to the cursor keypad. │ │ This would make me very happy. I thought I │ │ had gotten over it, but after using CDD3 for over a year │ │ I've decided that there is a better way. Please put some │ │ consideration into this. It shouldn't be too tough to do. │ │ Thanks in advance! Catch you later! │ │ -=> Mike Hanson, BoxSoft <=- │ │ There is 1 Reply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3772 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/10/94 │ │ Reported In : 30071 RevisedDate : 2/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Regarding editor hot keys....why not provide, in a setup │ │ type environment, the capability to assign user (us the │ │ programmers) defined control keys for all the │ │ functions. Then if you liked Ctrl-B better than Ctrl-L │ │ then you could assign │ │ it in your environment setup. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3897 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/17/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GLENN HARDIN 72611,1410 MSG#:55640 │ │ Give us the capability to assign our chosen keystroke │ │ combinations for the various actions throughout EDITOR and │ │ the rest of the Clarion environment. ..............Happpy │ │ Programming...Glenn │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3920 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 2/21/94 │ │ Reported In : 3007 RevisedDate : 7/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Editor will not take you to an error if it is in an │ │ Embed that was generated by the app generator. It WILL │ │ work if you are in the app generator. │ │ Dave: │ │ This is due to the fact that from the editor I am still │ │ getting embedded source names instead of CLA file names. If │ │ I were given a switch for the compiler to tell it to │ │ renumber the errors for editor vs generator this could be │ │ handled. │ │ Thanks - Lisa ( R&D at Clarion ) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3963 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/25/94 │ │ Reported In : 30071 RevisedDate : 2/25/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Arthur Svensson 71554,3162 MSG#:57137 │ │ The movement of text seems inconsistent. In 'good ole' 2.1 │ │ pressing ^M hi-lited the text to be moved. After pressing │ │ ENTER the hi-lited text moved and 'displaced' the │ │ unselected text. In true WYSIWYG fashion you could see │ │ where the text would be placed before you pressed the final │ │ ENTER key. │ │ In 3.0 the 'displacement' doesn't occur ... the │ │ elegant WSIWIG if 2.1 is gone. If moving text 'down', │ │ the selected block is moved one line _below_ the visual │ │ 'release' point (As I recall the same happens when moving │ │ text 'up'). This causes my feeble mind to churn & churn. │ │ It's not a big deal _but_ it would make life easier │ │ for those of us who use both 2.1 & 3.0 to have a │ │ consistent Editor interface. │ │ Please mention it to the IDE │ │ designers. TIA. │ │ ----------------------------------------------------------- │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4074 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/08/94 │ │ Reported In : 30071 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How can I get insert mode to become the default for the │ │ text editor,app │ │ generator and to remain in effect? I'm screaming sick and │ │ tired of the various │ │ IDE tools flipping insert mode off when I have it enabled │ │ (by pressing the INS │ │ key). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4380 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 4/14/94 │ │ Reported In : 3008 RevisedDate : 4/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like to see how many replaces were done after a │ │ search and replace operation. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4381 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 4/14/94 │ │ Reported In : 3008 RevisedDate : 4/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggested by user - when editing a read-only file at save │ │ time you are told you cannot save a read only file. User │ │ would like to be able to change the file attribute at the │ │ time he is told he cannot save the file, instead of going │ │ back to the dos shell and changing the attribute and then │ │ going back to edit the file. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4402 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : UK DateReported : 4/15/94 │ │ Reported In : 3009 RevisedDate : 4/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There seems to be a need of improvement with the Macro │ │ playback in the editor. It is no where near as effective │ │ as the 2.1 macro playback. │ │ For example in 2.1 one could have the Tracking selection │ │ come up and select a track character and draw it, or I can │ │ import from a file, and there are other items. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4958 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 7/19/94 │ │ Reported In : 3009 RevisedDate : 7/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Make CTRL-F work anywhere within a Structure │ │ Section │ │ Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Are there any intentions of correcting the Ctrl-F function │ │ in the CDD editor to allow access to the screen formatter │ │ WITH OUT having to be on the "SCREEN" line in source code. │ │ This is really bothersome!!!! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4417 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/18/94 │ │ Reported In : 3008 RevisedDate : 4/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Example Applications │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: SCOTT CHARLES 74144,151 MSG#:66194 │ │ i notice that there is no support for hp III in the laster │ │ ctl file. has the ctl not been updated? does anybody know │ │ when, or if, it will be? any info on printer support will │ │ be appreciated. scott charles. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3820 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ File Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:54880 │ │ I'm sure that you will correct this in time, but I thought │ │ I'd point it out... │ │ SUGGESTION │ │ ---------- │ │ Starting on line 198 of FILE.TPX, the following code may │ │ be found │ │ SETPATH(SaveDir) ! │ │ Return to starting path #IF(%DirQueueExists) │ │ FREE(DirQueue) ! │ │ Free the DirQueue memory #ENDIF │ │ FREE(FileQueue) ! │ │ Free the FileQueue memory #IF(%ClearOnCancel) │ │ CLEAR(%SaveFilenameVar) │ │ #<! Clear the filename variable │ │ #ENDIF │ │ DO ProcedureReturn │ │ #<! And leave the Procedure │ │ But ProcedureReturn repeats all this code - kill │ │ all the above lines except DO ProcedureReturn. │ │ ProcedureReturn ROUTINE │ │ #<! return from the PROC SETPATH(SaveDir) │ │ !Return to starting path │ │ #IF(%DirQueueExists) FREE(DirQueue) │ │ !Free the DirQueue memory #ENDIF │ │ FREE(FileQueue) │ │ !Free the FileQueue memory DO │ │ EndOfProcedureEmbed #<! Process the │ │ final EMBED RETURN │ │ #<! END exit the PROC │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4617 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/05/94 │ │ Reported In : 3008 RevisedDate : 7/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ File Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The directory can not be changed unless you double-click on │ │ the directory list box. There needs to be a way to change │ │ directory without that. Like in cshell, pressing the enter │ │ ke while in the list box would change directories. │ │ QA&E: Please supply a testfile and reset Status to │ │ Incident. │ │ TB: Use demo.app in the example directory to demonstrate │ │ this. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1199 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/13/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jan van Dalen 71773,3321 │ │ ask R&D to add a Source to the FORM template? │ │ Setup Before Opening Screen │ │ This will allow for code after knowing which action is in │ │ effect and before the screen will be open. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1271 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when pressing the ok button,, there are two embeds for │ │ this. the extra one, not the edit procedure, could we │ │ place this one after OF NOMOREFIELDS this is a place where │ │ we could put code for something that is to happen only one │ │ time when pressing the ok button. If a field is required │ │ and it is blank when youi press the ok button the after ok │ │ is pressed embed will happen twice. │ │ Maybe we should just add a new one so as to not make code │ │ act differently than how it appears now for any embeds they │ │ are currently using. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1428 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/03/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ When defining the Referential Integrity fields in the │ │ dictionary, it can't link to the child field using a │ │ constant or a variable. For example. If I have 2 files, │ │ Student & Notes. │ │ (One To Many Relationship) │ │ ===STUDENT FILE==== ======NOTES FILE===== │ │ (No Link???) NOT:Note_Type X(3) │ │ (Key not set correctly) │ │ Student_Id X(10) ----> NOT:Note_Id X(10) │ │ I │ │ would like to define the Parent to Child link as: │ │ 'ST' ----> NOT:Note_Type │ │ ('ST' denotes Student Notes) │ │ STU:Student_Id ----> NOT:Note_Id │ │ (Finds note for this student) │ │ or │ │ GBL:varname ----> NOT:Note_Type │ │ (Local/global variable) │ │ STU:Student_Id ----> NOT:Note_Id │ │ This │ │ would give the referential integrity much more │ │ flexibility. True, the developer would have to assign the │ │ variable the correct value during the form setup, but it's │ │ much easier this way than forcing the developer to write │ │ his or her own referential integrity code. And if the │ │ variable does not exist in the dictionary, a compiler error │ │ will flag it as a bad link, which is the correct thing to │ │ do. │ │ You may also want to add a filter to help select the child │ │ records. It's not always possible or practical to have a │ │ key in the child file that will uniquely find the records │ │ to delete/change. (The child key may select too many │ │ records for its key or the proper key field may not exist.) │ │ Example: If a lookup field value changes in the States file │ │ from "AX" (originally mistyped) to "AK" (for Alaska), does │ │ it mean I have to add a State key to my Address file? In │ │ 3002, if I want ref. integ. to work, I do! Even though I'll │ │ never use this ADR:State_Key for anything else. A filter │ │ would solve this problem and will eliminate the key. Sure │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1766 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/09/93 │ │ Reported In : RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ I'd like to be able to embed code just after/before the │ │ formulas in a FORM. Also, I know BROWSE can embed text │ │ AFTER the formulas, how so how about adding an embed just │ │ Before the formulas? │ │ These extra embeds are really important for a │ │ form. If I have a calculation based on 4 fields that were │ │ entered, as it stands I have to embed the same formula │ │ after each of the 4 fields so that when either of the 4 │ │ fields are changed, the computed field changes │ │ too. I also have to add the formula after the screen opens │ │ so it's initialized correctly. Adding a single embed after │ │ the formulas solves all of these problems. All of the │ │ formulas will be stored in one file where we can │ │ easily see the relationships between them. Makes editing │ │ formulas a real breeze! │ │ Of course I could │ │ attempt to use the Crazy Formula Builder (CFB), but I don't │ │ have enough patience for it. Besides, I can't include │ │ references to my own functions using CFB. The Crazy Formula │ │ Builder is a throwback to the Infostar days when │ │ everything had to be menu driven, regardless of whether it │ │ made any sense to or not. BTW, Infostar is no longer being │ │ sold. <hint> <hint> At │ │ least these extra embeds will give us an alternative to the │ │ CFB. It should be easy enough to implement that I'm hoping │ │ you can make it available in 3004. The productivity wrt │ │ formulas should skyrocket once it's been implemented. The │ │ sooner the better!! │ │ There is 1 Reply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1919 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 7/20/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ one individual would like to have the default field │ │ selection when deleting to be the cancel button vs the ok │ │ button │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2251 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/30/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Same as bug# 1067 │ │ Fm: Gary Finlay 100270,3006 LOC:Message is defined in local │ │ data in a form procedure as @S30. Why then are you only │ │ allowed to enter 20 characters for the Insert, Change and │ │ Delete messages on the Procedure Properties screen? │ │ Gary Finlay (Dublin, Ireland) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3071 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 11/16/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Eric BabCock - Template Suggestion / Relational - Affects │ │ RelationalUpdate, RelationalDelete │ │ Long 'LINK' field names with multiple segment indexes (5 │ │ segments or more) generate lines that are too long in the │ │ 'IF' (any field names are different than the value saved by │ │ Relation AccessSave) ! Is the record releated? statement. │ │ Suggestion: Place a 'End of line' before or after each AND │ │ in these statements. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3231 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 12/07/93 │ │ Reported In : 3007 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When adding to an Auto-Increment file, Action starts out as │ │ AddRecord then gets changed to ChangeRecord after Auto# is │ │ assigned. This makes it impossible to check for Action = │ │ AddRecord when you are indeed adding a record. Probably │ │ need something like 2.1's Action = 5 (AutoNumber). │ │ R&D: We can do something like that in the future. For now │ │ though, If Action = Change then check AutoIncAdd, a byte │ │ flag (obviously, true if AutoInc Add in progress). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3310 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/14/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David L. Shapiro 72122,330 MSG#:46799 │ │ In the case where I have a form that is performing repeated │ │ adds, clearing the record each time, I am not happy with │ │ the way the template is set up. In my case, I need to set │ │ values for various fields. Usually, I set the values in the │ │ "Setup Screen" embedded code. This method does not │ │ work for multiple adds since this codes is only called │ │ once, before the loop, and the record gets cleared after │ │ each add. The only other alternative I found was setting │ │ the values in the database dictionary through the "Initial │ │ Vales." The "InitialValues" is effective, however, any time │ │ I need to make a change or set up additional fields, I need │ │ to compile the entire application since the database │ │ dictionary changed. Augh! │ │ I would like to see you add to │ │ the Form Template embedded code for 'Set Initial Values' │ │ which gets called at the same place as Do InitializeFields. │ │ case keycode │ │ of InsKey │ │ Action = │ │ AddRecord Do │ │ AutoNumber │ │ ... │ │ Do InitializeFields │ │ Do SetInitial Values ... │ │ Thanks for │ │ your consideration......Debbie │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3744 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/09/94 │ │ Reported In : 30071 RevisedDate : 2/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:53581 │ │ In the 3007.101 FORM.TPX there is a line that needs to be │ │ changed. This will allow the user to hit ESC on the │ │ pulldown (if any) that is on the form. This ESC will │ │ return the user to the form instead of exiting the form. │ │ The line that needs to be changed is line 355. It needs │ │ to be changed from: │ │ IF FIELD() <> ?Cancel │ │ To: │ │ IF FIELD() <> ?Cancel and FIELD() > 0 │ │ Regards, │ │ Fred Schmitthammer │ │ Professional Practice Systems, INC. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4180 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 MSG#:61244 │ │ I'm wondering if there's not something wrong with the way │ │ the Form's CANCEL button is handling referential │ │ integrity. │ │ Let's say you're adding an Invoice record, who's │ │ primary key is INV:InvoiceNum. When the invoice form is │ │ on the screen, the user starts entering the customer's │ │ name Inv:Address etc., then hits a hot key or a button │ │ to enter detail records. He saves the detail records │ │ then returns to the invoice form. If he now hits the Cancel │ │ button the abort the Invoice form, the Cancel doesn't │ │ delete the Child records that he's just added! │ │ Oh boy! │ │ So the Detail records are orphaned │ │ with an Dtl:InvoiceNum that doesn't exist in the Invoice │ │ file. Worse yet, when a new Invoice is created, the │ │ detail records gets appended to the next customer's │ │ invoice (since he'll reuse the deleted number). He won't be │ │ too happy about that.<g> │ │ Since the form is │ │ deleting the Child records properly when the Invoice is │ │ DELETED, the Child records MUST be also be deleted when │ │ a record is being added then cancelled. Otherwise you run │ │ the risk of circumventing referential integrity. │ │ What do you │ │ think? │ │ Barry... │ │ There are 2 │ │ Replies. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4626 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 5/06/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Brian Stevens -- would like to have the form to │ │ automatically be able to update related files. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4925 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 7/08/94 │ │ Reported In : 3009 RevisedDate : 7/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Form Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ end user suggestion to have an embed added to the form │ │ template right before the autonumber routine is called. "On │ │ ADD after record buffer is cleared" │ │ #IF (%Autoinc) │ │ #EMBED('on add after...) │ │ Do AutoNumber │ │ #ELSE │ │ #INSERT(%ClearValues) │ │ #EMBED('on add after...) │ │ #ENDIF │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4222 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 3/25/94 │ │ Reported In : 30072 RevisedDate : 5/31/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ FoxPro Driver │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ foxpro driver does not support the EMPTY function for an │ │ index. database manager gives error 22 - Express: No │ │ Function │ │ ts proj3051 │ │ R&D: Will be considered as an enhancement for later │ │ releases │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0118 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 1/25/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CLARION'S EXIT is Ctrl_x, Top Speed's Exit is Alt_X, │ │ Windows Exit is Alt_F4 and OS2 exit is Alt_F4. Please do │ │ Alt_4 for CDD.BAT. Have a switch to go from Ctrl_x to │ │ Alt_F4, then the product will be compatible with OS2 and │ │ windows. │ │ Q & A : Suggestions from compuserve user. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0282 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/07/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Watch out, I'm getting into the swing of writing these │ │ messages now. │ │ Apparently, no one (at Clarion Software) has yet tried to │ │ construct an application WITHOUT USING A MOUSE. I would │ │ urge that this be done. │ │ It is very aggravating to press Alt-O seven times before │ │ finally getting to 'OK.' IMHO, the only use for Alt-O │ │ should be to accept a screen. Also, how about switching │ │ from Ctl-X to Alt-O. 'OK' is as good as 'Exit.' │ │ In a like vein, Alt-C (or Escape) should only be used for │ │ 'Cancel.' Don't use it for 'Change' (in some places, Alt-H │ │ means Change, this is OK). │ │ Another quibble. I have been unhappy in not having the │ │ Wordstar(tm) cursor and deletion keys available in CPD │ │ (version 2). Most of the programs I have that use │ │ keystrokes to move the cursor around the screen have │ │ implemented at least the cursor 'diamond' and │ │ character/word/line deletion keys (this is about the only │ │ thing Borland & Microsoft agree on - check your OZCIS, it │ │ has it too). I hope it will be in version 3.0x. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0363 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/15/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Clarion DD Initial Menu Bar Query... │ │ 1) Is NOT {File} and [Clarion] duplicate file initiation │ │ menus? But, {File} being an SAA/CUA requirement! │ │ 2) Would it not be peferable to order [Project] [Clarion] │ │ [Tools] or [Clarion] [Project] [Tools] │ │ Opening Menu Bar │ │ ---------------- │ │ per PreRelease: │ │ {File} [Project] [Tools] [Clarion] │ │ {Help} New F2 M&r aA Shell F10 Ld │ │ App F4 Using Open F3 M&d aK Prompt │ │ Ld Dict F5 Index Dir Make aM │ │ Calc Ld Db F6 ----- ---- Run │ │ aR ------ Ld Rpt F7 About Prnt │ │ Debug aD ASCII Ld Txt F8 ---- │ │ ----- Color Ld Hlp F9 eXit cX │ │ Ch PR aN KyCde ------ Ld PR │ │ aL 43/50 │ │ Setup... │ │ Opt... │ │ Db Drvs │ │ Paths │ │ Coll │ │ Styles │ │ suggested revision, 3.001kjh │ │ {File} [Project] [Clarion] [Tools] │ │ {Help} New F2 M&r aA Ld App F4 │ │ Shell F10 Using Open F3 M&d aK Ld Dict F5 │ │ Prompt Index Dir Make aM │ │ Ld Db F6 Calc ----- ---- Run │ │ aR Ld Rpt F7 ------ About Prnt │ │ Debug aD Ld Txt F8 ASCII ---- │ │ ----- Ld Hlp F9 Color eXit cX Ch PR aN │ │ ------ Keycode Ld PR aL │ │ 43/50 Setup... │ │ Opt... │ │ Db Drvs │ │ Paths │ │ Coll │ │ Styles │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0526 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/08/93 │ │ Reported In : 3002 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is immaterial that eXit is *NOT* consistent within the │ │ Clarion Software Corporation. (And will need to be changed │ │ for Windows, and, again for OS/2). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0667 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 3/25/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Clarion3 resides on server with Btrieve NLM (ie │ │ Q:\CLARION3). .RED file set to Q: paths. Brequest is │ │ loaded at workstation. Try to load an APP (that resides │ │ on the server). 020 BTRIEVE NOT LOADED error message is │ │ returned.... │ │ PS-> Administrator works ok... │ │ BUCHLDAV │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1057 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 4/19/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you accidentally try and open an .app created with │ │ Professional 2.x it would be nice if we detected a 2.x │ │ application file and displayed a message indicating this │ │ fact. Right now you get an error window with │ │ 002 I/O ERROR │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1403 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/31/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ throughout the enviornment provide locators for our │ │ listboxes, ie field lists │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1502 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 2/11/93 │ │ Reported In : 3001 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I would like to suggest that the COLOR CODE list from │ │ the TOOLS option, │ │ Tools/Color Chart │ │ show the actual colors at the bottom, like it does when you │ │ change the .sty file. │ │ Clarion/System Setup/Edit Styles file │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1689 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/29/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GARY WEGNER 100236,1224 │ │ 1) Extend 'DUPLICATE' fn to support non-unique keys. │ │ Sometimes I want to be able to warn users that they are │ │ will create a duplicate key but still allow them to do so. │ │ 2) Change the mnemonics listed in the 'Keycode Chart...' │ │ tool to be exactly the same as 'KEYCODES.EQU' │ │ 3) Add a facility to the 'open' dialog to 'chnage │ │ directory' │ │ 4) Remove the border around the 'edit errors' │ │ screen so that the scroll bars are still available for use │ │ with a mouse │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2058 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/09/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ under ship list for the distribution files a user has │ │ suggested a COPY button, to copy all the distribution files │ │ to a specific directory │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2065 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/09/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tony Kirk (AKA) 71222,2520 │ │ Greg, │ │ I made a suggestion/request to Paul a while back, but │ │ figured I'd clarify it now for you. One thing that I'd like │ │ to see in the AppGen portion of CDD is the ability to │ │ access Template Help from many more segments of the system. │ │ Being able, for example, to view Template Help from │ │ the list box containing all the EMBED points would be nice. │ │ Actually, anywhere and everywhere you guys can put it in │ │ the AppGen would be a big help, especially with Template │ │ procedures which are involved and intricate. │ │ If you want or need specific suggestions │ │ about specific screens and/or processes in AppGen in which I │ │ would like access to Template Help, just let me know. │ │ Otherwise, consider my request for "everywhere" <g>... │ │ See ya... Tony │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2498 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/29/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Steve Gonczi 71331,1531 │ │ make ctrl-enter save and exit whatever you are in.! Best │ │ thing would be changeable hot-key assignments ( I would │ │ program F7 to generate code, build and run a project) │ │ Automate the selection of appropriate libraries, depending │ │ on the model selected in developer ( why do I have to take │ │ out dxvxgui.obj and substitute desxgui when I switch from │ │ static model to prot. mode ? the computer is much better at │ │ keeping track of tedium than me) Next best thing is │ │ conditional linking. I would settle for something like #if │ │ defined protected_mode link thisguy #else link that_guy.... │ │ Stay tuned for more ... │ │ /Steve │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2499 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/29/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: PARKER DOOLEY 73710,102 │ │ Make Enter complete a field without completing the screen │ │ (CTRL-Enter completes screen). It may be CUA to use TAB for │ │ this, but it's sure more intuitive to hit ENTER for most │ │ folksAnother pet peeve: use of period as a block terminator │ │ in Clarion language. It is the hardest character to see and │ │ is not a unique character so cannot be used by the editor to │ │ findend of blocks consistently. What is wrong with │ │ BEGIN...END??? (I know, I've read the Programmers │ │ Guide!) Parker │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2516 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/01/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jim Mumford 72760,3274 MSG#:34030 │ │ An example of excess keystrokes consistant is from the │ │ source screen. To test your app you use the following │ │ Keystrokes. │ │ Using all Hot keys: Using pulldowns Clarion-2.1 │ │ CTRL-X Alt-F Sht-F7 │ │ Ctl-Enter ALT-X │ │ Ctl-Enter ALT-O │ │ Alt-X Enter │ │ ALT-A Alt-O │ │ Sht-F8 Alt-P │ │ Alt-A │ │ Give this a try. As you can see 2.1 is much quicker. Also │ │ Steve Gonzi has some good ideas. │ │ From Greg_W: The actual keystrokes got mixed up in the │ │ transmission but you get the idea. This suggestion is │ │ based on a thread which I asked for examples of keystokes │ │ that are "not as easy as 2.1" │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2641 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/14/93 │ │ Reported In : 3005 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User is looking for a switch such as an enviornment │ │ variable to switch the buttons on a mouse. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2898 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 11/03/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Why cant the Wrap button mean the same thing in report │ │ layout as in screener?????!!!!??? │ │ R & D - Because there is no way for this information to be │ │ passed to the runtime report engine or for that matter, the │ │ report formatter. │ │ RB - I was under the impression that the screen formatter │ │ and the report formatter had access to the same information │ │ about files and fields. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2998 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user is requesting that the calculator, ascii chart, color │ │ chart and keycode chart be made movable │ │ This ability is already there using the mouse. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3536 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 1/17/94 │ │ Reported In : 3007 RevisedDate : 1/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about an option in the enviroment to Enable and/or │ │ Disable sticky pulldowns??? │ │ R&D: This means many of the ACCEPT loops in the system must │ │ be changed, and a global environment variable added. │ │ Major change. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3557 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the system setup/options, Three checkboxes; smooth │ │ mouse, graphical fonts, graphical intro. It appears that I │ │ should be able to arrow down to graphical intro but I │ │ cannot. Just a bit odd. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3559 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The default colors for every thing except the pulldown is │ │ the same as the colors that were used in the templates. │ │ And, the default color for hot Selected is ugly,... │ │ personal opinion. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4230 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/28/94 │ │ Reported In : 30072 RevisedDate : 3/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Tom Hebenstreit 72154,731 MSG#:62634 │ │ Please file as a suggestion that some method be implemented │ │ for alerting us as to which fields need us to enter the │ │ quotes and which don't. It's a pain to either have to │ │ remember each prompt's requirements or constantly get these │ │ kind of compile errors. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4239 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 3/29/94 │ │ Reported In : 3007 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The mouse sensitivity in the Environment is not very good. │ │ I would like a way to increase the sensitivity so I don't │ │ have to move the mouse a mile to get it to move half way │ │ across the screen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4406 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/15/94 │ │ Reported In : 3008 RevisedDate : 4/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:65982 │ │ Subject: Project Window (displays during/after compiles) │ │ Please ask R&D to consider the following: │ │ 1. Increase size of OK button (it's a little too small to │ │ select easily with mouse). │ │ 2. Use ENTERKEY as hotkey for OK and ESCKEY for CANCEL. │ │ Right now, we're forced to select one of the buttons since │ │ the keyboard isn't tied in (with the exception of │ │ ALT+button hot letter, of course). │ │ 3. Remove EDIT ERRORS button, it's too │ │ tempting not to use and stings to badly when you do <g>. │ │ (Sorry, I couldn't resist that one). │ │ Thanks, │ │ Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4420 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/18/94 │ │ Reported In : 3008 RevisedDate : 4/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:66232 │ │ Subject: Controlling multiple instances of CDD │ │ Several times now I've used the TOOLS, DOS PROMPT option │ │ from within Generator, then stupidly reloaded the CDD │ │ environment (that makes two copies in memory). Each time │ │ CDD has been kind enough to ask me if I wanted to │ │ rename/delete my APP.$$$ file. I usually say delete to │ │ this, since Netware's salvage can bring it back anyway. │ │ Unfortunately, CDD will then HANG the computer after │ │ loading the APP (for the second time). │ │ In 2.1, CLARION.COM │ │ prevented such mischief. Any chance R&D could add this │ │ capability to CLARION3.EXE as well? │ │ Danny │ │ R&D: This is being added to Clarion, probably in batch │ │ 3010. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4795 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/10/94 │ │ Reported In : 3008 RevisedDate : 6/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:75557 │ │ It is not impossible for clarion .MEM files to become │ │ corrupted or deleted. With CPD21 you could run filer on the │ │ file and it would fix a corrupted memo file or create one │ │ if it was deleted. │ │ How can you accomplish the same trick with CDD? The user │ │ has100 sites, some of them in the real outback here & he is │ │ trying to pre-empt possible support calls. │ │ Rob from Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4798 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/10/94 │ │ Reported In : 3008 RevisedDate : 7/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the conditional and computed formula screens, Field Name │ │ has a hot key as AltN, but since this is not an entry field │ │ nothing happens when AltN is hit. AltN should select the │ │ button to the right of the field or there should not be a │ │ hot letter. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4801 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 6/10/94 │ │ Reported In : 3009B RevisedDate : 6/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Clarion3.INI should allow an unlimited task │ │ list...current limit is 255 characters. Tasks can be │ │ allocated on separate lines... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4804 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 6/10/94 │ │ Reported In : 3009B RevisedDate : 6/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Standardization of all buttons... │ │ Some have ellipses (...), others (like the Colors button in │ │ the Screen Formatter) do not. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4988 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/05/94 │ │ Reported In : b2 RevisedDate : 5/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about sticky Pulldown options, it'll make things a lot │ │ easier to learn │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5003 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/05/94 │ │ Reported In : b2 RevisedDate : 5/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ We should ship completed copied of the tutorials │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5009 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/05/94 │ │ Reported In : b2 RevisedDate : 5/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The ability to print the report description on your report, │ │ via a system variable. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5043 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/10/94 │ │ Reported In : B4 RevisedDate : 5/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be more intuitive if we had Hot keys for the │ │ following: │ │ Run Report ---- Alt G (for Generate Report) │ │ Report Order -- Alt S (for ALTernate Sort) │ │ Record Filter Ctrl F │ │ Something should also be done w/ File Paths and Schematic │ │ so you don't have to KEEP Pressing so many keys!!!! │ │ How about make the PdMenu STICKY!!!!!!????????? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5067 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/23/94 │ │ Reported In : 3.0B RevisedDate : 5/23/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ We have a save on the menu, now where is the Save As │ │ selection. The user relizes that he can first make a copy │ │ of his report. However, what if he doesn't remember. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5075 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : DB DateReported : 5/25/94 │ │ Reported In : RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Does not operate as documented │ │ Synopsis │ │ Button suggestion │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you choose a range limit field that is a runtime, │ │ you pull up a list of all the runtime fields. at the │ │ botton of the screen, there are Insert and, Change buttons. │ │ On the right side, there are Select, and Exit buttons. │ │ Where I highlight the Runtime field that I want, I │ │ hit Enter, thinking that I will choose that runtime field, │ │ and return to the previous screen. Instead, pressing │ │ "Enter" will select the "Change" button which brings up the │ │ properties screen for that runtime field. This is very │ │ confusing! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5076 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : DB DateReported : 5/25/94 │ │ Reported In : RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Does not operate as documented │ │ Synopsis │ │ Report run "Formatting report" │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When I run a report to the screen, I do not get any │ │ indication as to whether or not the report is running, or │ │ it has finished running. In 2.1, there was a flashing │ │ message at the bottom of the screen that said "Formatting │ │ Report". When the report was done generating, That message │ │ went away. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5086 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/26/94 │ │ Reported In : 3.0 RevisedDate : 5/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Include all printer controls in one file instead of │ │ separate ones MATRIX & LASER CTLs. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5091 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : J DateReported : 6/06/94 │ │ Reported In : RevisedDate : 6/06/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When running a report to CONSOLE, there should be a way to │ │ exit the report via mouse - currently, you are required to │ │ ESCape out. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5095 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : NA DateReported : 6/08/94 │ │ Reported In : RevisedDate : 6/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When running a report from within Report Writer, if you are │ │ not in the current directory of your data files, you get a │ │ cannot locate file error. This coincides with 2.1 but in │ │ 3.0 this did not matter. It would be a nice option to run │ │ CRW from any drive and path and your data files were found │ │ automatically. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5172 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Suggestion for locator on Color selection │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the CDD3 applicatio generator, when I'm selecting a │ │ colorfrom the list of colors stored in the style file, a │ │ locator field would be *SO VERY HELPFUL*. I can't remember │ │ all thosecodes, but the names are meaningful. So sorting by │ │ alpha helps, but that alone doesn't come close to how │ │ easy it would be to pick those lil' suckers with a │ │ locator. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5174 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion for alternate Editor for Embed areas. │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Please also give us the option to use our 'own' editor also │ │ for #EMBEDs; it should be easy enough to implement: just │ │ start the (installed) editor with a temporary file (with │ │ thecontents of the embed if one already exists), and pick │ │ it upagain on return from the editor. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5179 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion - Procedure Tree organization App Gen. │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The procedure worksheet gets too complicated for large │ │ applications. What I'd like to see is the same child "hide" │ │ feature that's available in OS/2 directory listings. You'll │ │ have a "+" in front of the parent procedure, when you click │ │ on it the child procedures will then appear appear │ │ underneath it, and the "+" turns into a "-". This will │ │ allowus to compress all the sub-trees that we don't want to, │ │ or need to look at. │ │ Example: │ │ + ProcA │ │ - ProcB │ │ + |--ProcB-1 │ │ - |--ProcB-2 │ │ - |--ProcB-21 │ │ The "+" beside ProcA means there are child procedures │ │ underneath it but they're hidden. Click on it and the │ │ child procedures will appear. │ │ Clicking on the "-" beside the ProcB will hide the │ │ child procedures ProcB-1, ProcB-2, etc.. │ │ The hidden subtrees remain from one session to │ │ another. So if the user is working on just one branch of │ │ the tree, that's all they need to see at that level. │ │ Using a collapsing tree like this will remove │ │ a heck of a lot of clutter and will make applications │ │ more manageable for the developer. │ │ Something else I'd like to have is the │ │ ability to search on the description of the procedure. When │ │ dealing with 100+ procedures in one app, it's easier to │ │ remember part of the description rather than the actual │ │ procedure name. After a while, all the procedure names │ │ begin to look and sound alike. To accomplish this, just │ │ have a radio box when you enter the search string that │ │ says: │ │ Find String: │ │ Accounts Payable Form [x] Search │ │ from top of view ( ) Name │ │ (*) Description <-Searches desc instead of Name │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5180 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion for SAVE hotkey from APPGEN, DCT, DBM │ │ Section │ │ General Environment │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestion for a "SAVE" hotkey from the various Clarion │ │ Editors. ie, AppGen, Editor, Dictionary Editor. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0310 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/10/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Could we maybe get a control - g to get a pulldown menu │ │ when generating a pulldown menu in let's say a browse? │ │ Instead of creating one from scratch that I might want from │ │ many different areas? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0315 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/11/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Just to make it official.... It would be really great to │ │ have memory variables defined in the data dictionary. This │ │ way any module that uses a particular data dictionary will │ │ all have the same global memory variables. │ │ The reason for using this is because we have several │ │ programmers working on the same project. So we break it up │ │ into seperate app files and call all of the procedures │ │ together in the main app by referring to all of the │ │ procedures as other. If one of the sub apps has a variable │ │ that is not defined in the main app this can cause │ │ problems. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0364 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ there is no way to delcare a group over a record structure │ │ or over anything except other data declared in the global │ │ properties area. │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0520 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/07/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestions: │ │ 1) Allow PHYSICAL order to be treated like a key in │ │ generator │ │ 2) Allow copy of a procedure to another procedure (AND) │ │ allow procedure type to change. What ever attributes can │ │ survive should. This is an alternative to being able to │ │ directly change the proc. type │ │ 3) Add macro support to generator & dictionary builder, │ │ (like editor) │ │ 4) Show more useful info in dictionary, and │ │ LINE UP COLUMNS │ │ a) file : name,prefix,driver then description │ │ b) fields: name,type,picture,attributes,validations │ │ then description │ │ c) keys : name,type,attributes then description ... │ │ x) in the past (Prodigy) I've talked about multiple │ │ views for dictionary along the general lines of │ │ the two views in generator │ │ y) I would also like to see FILL fields used in │ │ dictionary builder │ │ 5) When selecting keys in generator, make ALL │ │ information viewable at least show field components !!! │ │ a) Same goes for selecting keys in the relationship │ │ section of dct. │ │ 6) I support the field dictionary ideas, │ │ a) if nothing else, add support for the LIKE feature of │ │ the language. │ │ b) support field ^gets, so can copy a field │ │ (or tagged list of fields) from one file to another. │ │ 7) Give some indication that a save is actually being │ │ performed when do a file-save (in dictionary [and │ │ elsewhere]). │ │ 8) Dictionary, TAG a file as deleted until save dct, I │ │ ACCIDENTALLY hit my keyboard, pressing (I assume) │ │ delete and another key thereby succeding in blowing │ │ an entire file away. I used a ^Get from the .BCT to │ │ restore, but somehow that was too accidental. │ │ 9) Add ^G support inside of generator for clarion.app │ │ (template.app) │ │ 10) Don't use enhanced/blink to around inactive windows in │ │ editor because, I enabled blink in screener, went to a │ │ source window, alt-2'd and found the inactive window │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0666 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/25/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: bill brobeck 71071,2707 │ │ Here's some more bugs & stuff 1) The insert key in the │ │ field properties of memory vars of a module brings the │ │ cursor back to beginning of the entry and does not go into │ │ insert mode. │ │ 3)The edit of a computed field doesn't seem to allow the │ │ inserting of parenthesis. │ │ 4) Make & run from the module worsheet will make, but will │ │ not run. │ │ 5) The browses do no seem to recongiize picture statements. │ │ I think its the format statement in the procedure that │ │ calls the browseaction function. │ │ Suggestions: │ │ 1) It might be nice to be able to quickly change a local │ │ var to a global var by pointing and shooting... │ │ 2) How about a fixed column in a browse. │ │ 3) how about showing the load size of an exe somewhere. │ │ Q & A : 1,2,3,4 AND 5 are fixed. All other reports are │ │ suggestions. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0701 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/31/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Goldberg Mark 75250,2551 │ │ Here are few suggestions for the generator │ │ 1) Add support for copying varibles from one procedure to │ │ another │ │ 2) Add support for file by file control of the create vs. │ │ halt │ │ 3) also add file by file control of the opening mode │ │ (read-only ...) would be nice to have a cached mode, useful │ │ for small read-only files. │ │ 4) consider, having a procedure call that be defined on a │ │ file by file basis that handles error conditions (on │ │ opening) │ │ 5) Add defaults control for new fields, things like SHADOW, │ │ INS, IMM, ... │ │ 6) Add a helper hot-key, that allows you to edit your help │ │ while in screener. Or add support for help editting from │ │ within clavid. │ │ 7) Make source and data (main screen buttons) available │ │ from within screener. │ │ 8) Make the dictionary availble from within generator │ │ make it read-only if you must, but add it. │ │ 9) Add a generation switch with culls out unused files that │ │ are in the dictionary. This will go a long way toward │ │ sharing a single dictionary amongst several applications │ │ that only share a few files. │ │ !vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv │ │ vvvvvvvvv! │ │ Q) what is being done to facilitate new defaults (colors) │ │ and new dictionary settings ? │ │ !^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ │ │ ^^^^^^^^^! │ │ -- Once again, that's enough for now. │ │ -- Mark Goldberg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0736 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 4/02/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ problems creating a field that contains an apostrophe. │ │ ex. in creating the field(generate expression) │ │ phn:state&''' showed as phn:state&'''' in the │ │ computed field screen. this is a little confusing, but │ │ works fine at runtime. │ │ ex. generate expression - phn:state& 'a'a' - got generated │ │ as phn:state&'a''a' which is correct but aat runtime the │ │ field got displayed as FLa' a - the space after the ' │ │ is incorrect. ^-***RUNTIME PROBLEM*** │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1047 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/16/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas E. Johnson 71543,1566 │ │ 2) Besides the field for entering an include file, might a │ │ source button be added (like the Setup or Edit Procs for │ │ Pushbuttons) so that one might enter the prototype right │ │ then and there, rather than having to go into the editor. │ │ 3) Some colors on this window do not seem to correspond │ │ with the appropriate elements in the style file - the │ │ title, and border colors are not as I would expect from the │ │ style file I am using. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1118 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/30/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When a formulas are generated, they execute in order of │ │ entry. There is not way to rearrange the order in which │ │ the formulas are calculated other than deleting and │ │ re-entering in a different order. This is important when │ │ one field relies on the results of another field. │ │ R&D: Formula free-format option in 3007. Order of defined │ │ formulas is maintained/compiled in Btrieve sort order. │ │ Thisorder will be able to be changed by the user in a future │ │ release of CDD. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1194 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/12/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be real nice if I could reorder my formulas so │ │ that a formula can be based on another formula. As in a │ │ nested conditional field. The only way to do this now is │ │ to change the names of the fields cuz they will appear in │ │ alphabetical order. This prevents me from using the names │ │ for the fields that I would like. │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1223 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Bruce Wojak (who has been very helpful in reporting │ │ bugs) requests that we allow more #prompts in the template. │ │ We spoke at the developers conference indicating that we │ │ would allow the ability to scroll the procedure properties │ │ window allowing room for more prompts. Bruce is doing some │ │ extensive template developement and I am assuming these │ │ will be made available as third party add ons. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1654 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Mike Hanson requests that #MAP and #PROJECT be recognized │ │ when they are in the main program section of the program so │ │ he can add his libraries to the template. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1676 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/29/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Johan Kotze 100075,73 │ │ I am busy with an application under CDD3003 (about 50 │ │ procedures) and I have deleted a browse procedure. Now I am │ │ unable to view then modules. If I select module view, I get │ │ an error message - 'Procedure Header Missing - Invallid │ │ Data in App File'. I also cannot rename the app file or │ │ generate source. I have had this problem before, and got │ │ round it by creating a new app and copying all procedures. │ │ This is very time consum- ming though. Could you not supply │ │ us with a program that can fix corrup- ted app files?. (In │ │ the same manner as chkdsk fixes bad disks). This would │ │ really help us programmes a lot. │ │ Johan │ │ R&D: In 3004 the app file is saved prior to any make. This │ │ should keep the app from getting corrupted. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1863 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 │ │ After adding a module in Module View (3004), it is │ │ impossible to change the module properties without deleting │ │ it and starting again. The property choices are disabled if │ │ one attempts to make these changes directly. Also, it would │ │ be nice if the Module Structure Include File field could be │ │ made to accept a Section parameter rather than just the │ │ file name. Not real painful, but somewhat annoying. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1883 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: KC Shore 76470,3544 │ │ I noticed a problem with the way clarion processes formula │ │ fields in a report it processes them in alphabetical order. │ │ this could pose a problem as you might have a formula that │ │ requires an othe rformula to complete. │ │ Example │ │ -> holdPC = ( win / coin-in) * 100 │ │ the structure in the report would be as follows: │ │ coin-in = rpt:coin-in + 100 │ │ holdPC = ( win / coin-in ) * 100 │ │ win = rpt:win + 500 │ │ in order to get the report to run properly you would need to │ │ rename 'WIN' to some thing that starts with 'A-G' this │ │ could pose a problem if you were not aware of it, I think │ │ the be st solution would to allow you to set the order like │ │ you did in clarion 2.1 with fields by using the GREY + or │ │ GREY - key. │ │ R & D : Will be addressed in 3.1. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1940 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ Well, you're (partially) right. Here's what it's doing. │ │ If I create an application called \CLARION3\X\TEST.APP, and │ │ use: Application Name: F:\CLARION3\X\TEST.APP │ │ Template File : F:\CLARION3\X\CLARION.TPL │ │ Dictionary File : F:\CLARION3\X\CONTACTS.DCT │ │ Styles File : F:\CLARION3\STYLES.STY │ │ Help File : │ │ First Procedure : Start │ │ CDD will create a dummy \CLARION3\X\CLARION.APP file, and │ │ use that for the DEFAULT app. The CLARION.APP file that it │ │ creates is only 3072 bytes and like you said, it doesn't │ │ have the report variables defined and that's what's causing │ │ the compile errors. │ │ So it looks like I need to copy the │ │ \CLARION3\CLARION.APP to wherever I have the CLARION.TPL │ │ file, in this case \CLARION3\X. │ │ I guess this isn't really a bug. │ │ I just don't know why it doesn't display a warning message │ │ saying it's "About to create the file "template.APP" │ │ Continue? Yes/NO" if it can't find the default template.APP │ │ file in the same subdirectory as the template files. It's a │ │ bit dangerous for it to go ahead and create a dummy │ │ CLARION.APP without warning. It may not be what the user │ │ expects. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1945 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dave Willow 70020,575 │ │ In order to keep my CDD files clean, I have flaged all of │ │ the distribution files as Read Only. However, when I open an │ │ application and CDD 3004 asks me for the template, I get │ │ anI/O Error. It appears that CDD opens the template files │ │ for read & write. I don't see any reason why CDD woul d │ │ want tohave them opened that way. │ │ If there is no reason for this, I would like to │ │ request that the template files be opened in a Read Only │ │ manner. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1962 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/22/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 │ │ the following enhancement for #MAP in the template language │ │ #MAP(Include File, <Section Name>) │ │ Include File - As presently defined │ │ Section Name - An optional string constant containing the │ │ name of the section of a file to INCLUDE in the │ │ application's MAP Structure. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2000 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 7/27/93 │ │ Reported In : 3005 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If the user selects "Generate Source", shouldn't AppGen │ │ generate source regardless of the "Conditional Generation" │ │ flag? It seems to me if they went to the trouble of │ │ selecting "Generate", they REALLY want to generate source. │ │ Alternatively, we could add a "Generate ALL" to the │ │ pulldown menu or sub-dialog which would allow you to do │ │ thiswithout affecting the "Conditional Generation" flag. │ │ This would also eliminate the need for a "touch" utility │ │ for an application. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2055 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/06/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ I am making some template modifications where I need to get │ │ the MSG attribute text from an OPTION field. I am unable to │ │ do so. The application generator generates a screen field │ │ for the database field but not for each radio button │ │ (OPTION). So, the database field does not have a message │ │ attribute (just the radio button does) and does not generate │ │ any value in the %ScreenFieldMsg symbol. │ │ Is there any way to get the message text for a radio │ │ button ? │ │ Fred Schmitthammer │ │ Professional Practice Systems, INC. │ │ (310)804-7674 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2064 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/09/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user reported that after deleting numberous procedures the │ │ size of his app file did not change at all │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2095 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/10/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User would like the ability to copy global variable from │ │ one app to another │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2216 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/25/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: R.Radcliffe 72460,3560 │ │ Add two more options on the View (Procedure/Module). │ │ First would order procedures by name - no connecting lines. │ │ This would make it easier to find procedures. │ │ Second would order by type of procedure │ │ (Form/Browse/Source,etc.) then name - no connecting lines. │ │ This would make it easier to find types of proecures. │ │ Example, if you need to make a change on all report │ │ procedures. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2519 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 10/01/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests a global "reapply default colors" as well as │ │ a procedure by procedure reapply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2596 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/07/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ where is the records()? │ │ R&D:Was implemeneted in free-format entry of expressions │ │ and then had to be removed... will be added in 3.1... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2688 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 10/18/93 │ │ Reported In : 3005 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests that Template and Dictionary line in the │ │ generator allow for just the file name therefore defaulting │ │ to the current directory instead of requiring the full path │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2912 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark Goldberg 75250,2551 MSG#:37648 │ │ Suggestions: │ │ 1) Appgen, file-save should leave the scroll bar where it │ │ was, vs. going to the first procedure. │ │ 2) Add support for string structures in appgen screener, │ │ or if entry,skips are really the way to go, then a default │ │ color should be applied to skip'd fields vs. real entry │ │ fields. │ │ 3) Make it simple to copy color setting from one │ │ field to another in screener. Remember how ^A could be used │ │ to set the 'normal' field color in 2.1's screener. That │ │ would be nice, as well as being able to put my cursor on a │ │ field, press a hot-key to set the default 1-5 colors, and │ │ then another hot-to apply those colors to the field │ │ currently under my cursor. If this is too hard, then allow │ │ us to directly enter the color codes when in the color │ │ setting window, vs. having to go to the styles listbox, │ │ which has no locator, or to the color selection grid. │ │ 4) Add a toggle to │ │ disable auto-prompt creation, on field creation │ │ 5) As earlier │ │ noted, add support for editting the field label, this would │ │ be a major enhancement, by allowing field copies to be │ │ useful. This would also support field name changes in the │ │ dictionary. 6) Make │ │ it possible to tell the style number (the actual color │ │ number and more to the point the style description) for │ │ non-fields that are on the screen. Ex: tracks, text typed │ │ on the screen, paints etc. This could be done by showing │ │ the screen structure, much like the ^F screen. │ │ 7) Show the style number (better yet the sytle │ │ description), on the track window in addition to the visual │ │ cue of what color it is currently mapped to. │ │ 8) Have listboxes support the scroll-lock key, │ │ for our code as well as CDD's code. │ │ 9) The output of a compile should │ │ automatically be stored in an output text file. It would │ │ have the name as the .pr but with a different extention. │ │ Failing that, there should be redirection support when the │ │ print button is pressed, so that a file name can be │ │ specified. 10) A compile │ │ should beep when completed │ │ 11) Standard │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2988 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ralph Johnston 71033,135 MSG#:41633 │ │ In addition to the ordering feature (for formula fields), I │ │ would suggest some way of looking at them in the order │ │ theywere entered (or at least in the order they will be │ │ calculated). Now I believe they are sorted │ │ alphabetically, which is nice, but not useful in │ │ determining evalutation order. Thanks... │ │ ..Ralph │ │ R&D: On the schedule for 3.1... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3010 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 11/10/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests that we add the facility to copy the pulldown │ │ structure between procedures. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3122 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/22/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:43675 │ │ The AUTO attibute on a variable is not supported through │ │ the APPGEN. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3244 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 12/08/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Your application is missing a template file. If you do a │ │ make and run, you are informed about 10 times that you are │ │ missing that template file, and the TODO template is being │ │ used. Can this be changed to inform the developer just │ │ once that they are missing a template?? │ │ R&D: Will be implemented in version > 3007... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3296 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/13/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Leschak (CompuSyste 71461,471 MSG#:46334 │ │ problem with template language in handling PROJECT/MAP │ │ commands. │ │ i have a set of templates which has a │ │ PROJECT(mylib)/MAP(mylib.inc) statements referencing a lib │ │ in a module. so if i were to go into the project/module │ │ info, as expected, the insertion of 'mylib' had been │ │ entered to the module list. │ │ in my procedure listing, i have inserted an external │ │ module which also references 'MYLIB', and also referencing │ │ MYLIB.INC. but i get duplicate definitions when i compile. │ │ the reason for this is that when it inserts the 'mylib.inc' │ │ from the MAP () command, it places it in the modules map │ │ andnot the program. when i create an external module, it │ │ will place this in the program's map. i can see the │ │ reasoning for this, and can work around it, but though │ │ that a more reasonable approach would be to check to see │ │ if the MAP('mylib.inc') has already been included in │ │ the programs map structure (via other MAP() commands or │ │ via external libsdirectly in appgen ctrl-l)) , and if so, │ │ then do not includehere. │ │ hope i make sense. │ │ jsl │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3509 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 1/12/94 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Helmut J. Schwarzin 73140,2732 MSG#:49763 │ │ When trying to move a Queue field in Global memory in │ │ AppGen it won't move. It will move the fields inside the │ │ Queue Group but not the Queue group itself. │ │ From Greg_W: Suggestion: To be able to move the bottom or │ │ top of a Group or Queue over fields. Instead of moving │ │ the fields into the Group or Queue. │ │ Greg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3551 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/20/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from end user │ │ in the formula generator when user is choosing a clarion │ │ function it would be nice to have a locator field for the │ │ function name instead of having to keep hitting page down │ │ to get to the correct one. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3562 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When choosing a range limit field, is it posible to get a │ │ listing of just the fields of the acess key that was │ │ selected in the files pushbutton? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3714 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/07/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 5) When in the expression generator one does NOT check │ │ 'use │ │ expression generator' the prompts for the formula's and, │ │ in │ │ a conditional formula, the condition stay disabled, │ │ although │ │ one can enter the text field. │ │ 6) Suggestion: place a button for template help in the │ │ formula │ │ editor, so one can more easily get help while filling in │ │ the │ │ formula class. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3809 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/14/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:55071 │ │ I have often wanted a way to specify the mode in which a │ │ file is opened within the developer environment. │ │ How about having somewhere to specify such information - │ │ perhaps in an application's global properties. │ │ For doing the 'alias' lookups you could open the alias │ │ files read-only. The main file would be opened │ │ read-many write-one mode. │ │ Regards, │ │ Randy Rogers │ │ Keystone Computer Resources │ │ From Greg_W: I'm not sure if this is feasible or not but I │ │ figured I log it as a suggestion for a future release. │ │ Let me know if you not sure what he is suggesting. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3832 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Andy Stapleton 75110,2467 MSG#:54926 │ │ Well, I Tried it and got the "This Function Not Allowed" │ │ As a Suggestion for next release. │ │ Allow the Free form Formula section to do SET,GET │ │ Functions.... │ │ AnyBody Else have more functions they would like │ │ to ADD... │ │ The reason to add these functions allows the │ │ developer to access the same type of functions your using │ │ in the EBROWSE without having to mantain several file │ │ structures and File Handles ..... │ │ I Think This would be a FANTASTIC │ │ enhancement of the System..... │ │ The TEmplate change would have to │ │ Include a LOOKUP statement and Check to see that the Fields │ │ MATCH..... │ │ LET ME KNOW HOW YOU FEEL AND WHAT │ │ PROBS WE CAN FORSEE │ │ Andy <<Cowboy>> │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4113 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30071 RevisedDate : 3/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ken J Horii 76340,1234 MSG#:59812 │ │ 1) CLARION.RED will *NOT* redirect BACKUP FILES to the │ │ \BKP subdirectory. │ │ 2) CLARION3.EXE will *NOT* execute the CONTACTS.EXE in the │ │ \BIN subdirectory. │ │ 3) CLARION.APP will *NOT* allow me to make the PATH │ │ (drv:\subdir) a variable from a configuration file *.INI or │ │ *.CFG. │ │ Greg, the above is the cause of all my current questions │ │ forCDD3.007.105. Should you and Bruce find all this trivial │ │ andbeyond the scope of CLARION DATABASE DEVELOPER please │ │ informme of you decision and I will quit! │ │ TIA... KJH 10MAR94 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4245 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In local data for a procedure I would like to Copy a Queue. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4254 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 62908 S8/3.0 Support │ │ 28-Mar-94 10:14:29 │ │ Sb: Compile Crash /Suggestns │ │ Fm: Mark Goldberg 75250,2551 │ │ To: Debby Herman 72662,475 │ │ There should be a simple way to show the value of a radio │ │ button'd field using appgen's screener. Currently I have to │ │ exit screener, go nto the data otheron, create a field │ │ LIKEit (simulating the like as appgen doesn't support │ │ the like attribute) and then place the field OVER the │ │ original field, exit the data section, return to │ │ screener and then place the field on the screen as an │ │ entry field, mark it as a skipped field, and then change │ │ the color from my entry color to my display color, and then │ │ press esc when the prompt comes up, then ^K to my display │ │ prompt color and key in the display prompt directly on the │ │ screen (I don't use prompts on display fields, because I │ │ don't want the hot-letter to show and effect flow, when │ │ I can never actually select the field). │ │ a) allow modification of the data │ │ section from within the field selection │ │ screen (after I've pressed │ │ insert/entry field) b) add like support to the │ │ data section (and data dictionary) │ │ [I understand there are │ │ issues surrounding the order of field │ │ declaration] │ │ c) support a default color │ │ for display fields [consider a screen │ │ structure type: display vs. entry/skip] │ │ d) remove hot-letters │ │ from skip'd prompts (sorry if done in 3007.x) │ │ [in general allow a │ │ prompt to have NO hot-letter] │ │ Additional suggestions: │ │ a) add exit without │ │ save from the data section b) add Relational │ │ Integrity to field re-naming between the data-section │ │ and screener │ │ c) allow the field │ │ names to be editted within screener ex: unit_type │ │ -> lcl:unit_type or unit_type[1] -> unit_type[2] │ │ d) allow the │ │ field type to be modified for a field within screener │ │ (probably │ │ only useful if display becomes a seperate field type) │ │ (well, how │ │ about entry <-> radio button ?) e) move │ │ prompt editting inside of the field screen (at │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4429 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/18/94 │ │ Reported In : 3008 RevisedDate : 4/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Select any procedure in your app. Notice the button labeled │ │ "Procedures"? Press Alt+E to select it. A list of │ │ procedureswill appear. Add any procedures to that list and │ │ they stay in sequential order, as opposed to alphabetical. │ │ If the listgrows to dozens of procedures (as in my case), │ │ it's a major pain to find one. Now, press the TABKEY until │ │ the LIST has focus. Now press the hot key to add a │ │ procedure. After adding it, press the hot key for │ │ CHANGE. After changing it, try to select a different one. │ │ YOU CAN'T. You have to tab back to the list before you │ │ can scroll. │ │ R&D: 1. Alphabetical sort on that list is a good idea, on │ │ the list for 3.1. │ │ 2. Selecting an operation through a hotkey (Alt-h in │ │ this case for Change) also selects the button... │ │ thats just the way it is. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4501 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/22/94 │ │ Reported In : 3008 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:67389 │ │ >> No, there are still checking the input for syntax │ │ errors and user >> defined functions are not accepted. ... │ │ Ah well, back to the embed. │ │ Could you please add accepting user defined functions in │ │ Forumulas to the suggestion list? │ │ Also, I would like to request that some thought be │ │ given to this _protect the developer_ attitude (perhaps a │ │ 2.1 remnant) which seems to raise its ugly head every once │ │ in awhile in the CDD design philosophy. A switch to turn it │ │ off would certainly be acceptable to those who do │ │ not desire to be hindered by this software development │ │ safety net. │ │ Douglas │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5323 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/30/94 │ │ Reported In : 3009 RevisedDate : 8/30/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion for 2.1 app import function │ │ Section │ │ Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When importing procedure from another application, I'm │ │ prompted for every duplicate procedure with a screen that │ │ says: " Duplicate Procedure: Replace Skip Cancel" This is │ │ fine if I'm importing just one or two procedures, but if │ │ I'mimporting a dozen or more procedures, it's a pain having │ │ to answer this question each time. In fact, as I write this, │ │ I have OS/2 in the background importing a dozen or so │ │ procedures. Every 15-30 seconds I have to quit this and │ │ pop over to the other window to say "replace". It's a hassle │ │ that can be easily avoided. │ │ What I'd like to see is another option added to this │ │ menu that says: "Replace All". When this is selected, I │ │ won't be asked any more questions and it will automically │ │ replace theexisting procedures. How about it? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3469 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 1/05/94 │ │ Reported In : 3006 RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Graphics Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Scott Lowry 72322,2735 MSG#:47506 │ │ Yes, I did get your reply to my message of a month ago re │ │ Graphics Library problems. After more trials and errors, I │ │ think I can make this briefer than it would have been │ │ before. │ │ > you should only link in support for the graphics │ │ modes you use │ │ First, I think you're saying, and it appears to │ │ behave as though ALL graphic drivers that you're wanting to │ │ support get LOADED into conventional lower memory as soon │ │ as any graphics library procedure is called. That explains │ │ why the program ground to a halt after calling same, all of │ │ a sudden having 200K-300K less memory to operate in. If │ │ thisis true, it's a terrible step backward from 2.1 where │ │ you could link all drivers into the program, but load │ │ only the one you needed with the SETVIDEO(GETVIDEO()) │ │ statement. If there is something I can do to link all the │ │ drivers, but load only the one called for, please tell │ │ me how. For now I've dropped Hercules support, which I │ │ can probably get awaywith, but I must have CGA and EGA/VGA │ │ and loading both thesedrivers is taking up a lot of │ │ precious memory. (With thousands of users I don't │ │ have the luxury of "linking in support for the graphics │ │ mode you use"). Incidentally, sincedropping the Hercules │ │ support the program no longer goes into "crawl" mode, │ │ taking 7 seconds to load 50 records into a LIST box. (That │ │ problem occured in regular CDD non-graphicLIST box screens │ │ anytime after a procedure using the graphics lib had │ │ been called, even though one had RETURNed from that │ │ procedure). │ │ Second, │ │ the overlay manger seems to have a problem with │ │ procedures that use the graphic library, as the program (my │ │ app) will crash with an "out of memory" error on a very │ │ arbitrary and unpredictable basis when such are called. If │ │ Ireduce my memory by loading a TSR, then the problem │ │ becomes more frequent, and still unpredictable. There is no │ │ such problem on procs that don't use the graphic lib. │ │ Has this been reported as a bug? Is it being fixed? Is │ │ there a work-around? │ │ Third, there's a non-documented anomoly that │ │ creates an immediate System Halt crash if you try to do │ │ a 'Make and Run' when your project file has 1) the .OBJ │ │ stub that eliminates Hercules support (probably any │ │ .OBJ) placed before the CLA files, and 2) the 'pack' │ │ link option is 'Off', and 3) the debugger option is │ │ not being called. It took several hours to run that down, │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2061 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/09/93 │ │ Reported In : RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user suggests the ability to change the colors for the │ │ selector bar and also the ability to open a screen without │ │ a border │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2160 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/19/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul M. Blais 72103,111 │ │ Since I first posted the message, I have pinned it down as │ │ follows. If I take the "Checkbook" example app, and use │ │ setr gb to bring up appgen with custom.clr, I can edit the │ │ app ch ange the colors and get proper results in the final │ │ exe colors. When I load custom.clr and run in appgen my │ │ colors reflect the custom.clr colors. When I work on my │ │ present ap p with custom.clr & GUI the custom colors appear │ │ in appgen,but do not appear in the GUI exe program as in │ │ appgen. I hesitate because the GUI interface does │ │ appear to change the colors very slightly in any case. │ │ In short, my GUI appruns the exact same way with or without │ │ custom.clr l oaded with setrgb. As best I can tell, │ │ VGAColor does NOT work withGUI. And ba sed on the color │ │ allocation fore & back color along with the light version │ │ of the color and gray it seems that making VG A color work │ │ properly could take some trickycolor mixing even if it did │ │ work. You would have to keep the rela tionship between │ │ light and dark colors the same in anyrevis ed pallete and │ │ even then ... │ │ Suggestions: │ │ 1-More documentation │ │ 2-A Clarion.app that │ │ conforms to the GUI standards │ │ R&D: The VGA Color Kit and GUI currently do not work with │ │ each other. This might be addressed in the future │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2199 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/24/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ repeat & point structures do not get a gui effect │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2377 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 9/23/93 │ │ Reported In : 3004 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants to be able to unload gui before running │ │ command.com and then restore it before going back to his │ │ application. when command.com is run the dos screen is in │ │ graphics mode │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2981 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/08/93 │ │ Reported In : 3006 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dave Willow 70020,575 MSG#:40483 │ │ I'm unable to get the "3-D" selection cursor with REPEAT │ │ structures or list boxes with the COLS attribute. Help? │ │ Also, with the COLS attribute in a list box, the horizontal │ │ scroll bar is a mess. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2989 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Greg Salyer 70731,2752 MSG#:41465 │ │ How about a putting a default "click-to-close" box in the │ │ upper left hand corner of a GUI app? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3571 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 1/21/94 │ │ Reported In : 3007 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ One more is when making a field display only and it has a │ │ prompt attached to │ │ it, why allow that prompt to display as a underscored item │ │ as if you can select │ │ that item? I know that you can place a space ' City' and it │ │ shouldn't display │ │ it as a hot item on the screen, but still. :) It's │ │ disabled... It shouldn't │ │ have the underscore there in the first place. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4422 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/18/94 │ │ Reported In : 3009 RevisedDate : 4/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User would like the ability to turn the mouse cursor off │ │ but still keep the mouse active. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4944 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 7/14/94 │ │ Reported In : 3009 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ gui2 - user wants ability to disable hot keys for buttons, │ │ prompts etc │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4962 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 7/19/94 │ │ Reported In : 3009 RevisedDate : 7/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │ GUI 2 - FIELDCOLORSON doesn't change Prompt colors │ │ Section │ │ GUI Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I have GUI2 and am able to change colors upon Select for │ │ alltypes of prompts and fields except for the _prompts_ on │ │ entry fields, am I doing something wrong │ │ Did you use the function FIELDCOLORSON ? │ │ Yes, when you select an entry field the prompt doesn't show │ │ in it's selected colors. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1591 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/18/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Hardware Specific │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a user had two video cards in his machine so he could use │ │ two monitors (one vga, the other monochome). the │ │ environmentalways detects the vga card. should the │ │ environment respect the mode command and look at the mono │ │ card if modebw80 is set? Vid works fine with his two │ │ monitors because it has a /s6 switch, but the envronment │ │ always uses the vga card. user reg. no. 224253 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2038 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 8/04/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Hardware Specific │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Vaughn Cox of Digital Solutions reports that alot of his │ │ customers use Cirrus Logic vesa adapters (model CL-GD5426). │ │ However CDD does not work with them. Could we get one of │ │ those boards here to test? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1169 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 5/10/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from end user - to be able to search the help │ │ file (in his generated application) for a keyword. also │ │ wuld like the ability to link one topic to another topic. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1332 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/24/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ For future versions of CDD, I'd like to see: │ │ 4a) HELP search capability. I find it impossible at times │ │ to find what I'm looking for. I know what the keyword is, │ │ like "Locator", but the current help screen doesn't │ │ have a button into it. I'd like to see a ^S command that │ │ would search the help.txt file for a given word or │ │ phrase, then pull up the help screen. This would make │ │ the help system a lot more powerful. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1508 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RT DateReported : 2/18/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Press F1 then ALT-S to bring up the Sections List. Move │ │ the highlight bar to some other Section. Press ALT-T to │ │ display the Topics List for that Section and the Topics │ │ List displayed is from the Section that you got when │ │ you pressed F1 originally. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1987 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/26/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 │ │ When creating a help system, for each HELP-ID one has to │ │ fill in the title and the textfile. │ │ I think in 90% of the cases this info remains the same for │ │ subsequent HELP-ID's. Is there no way to standard fill │ │ thesefields with the previously entered value? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2210 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/25/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ Here's a couple of suggestions. Instead of using "Secti │ │ ons" and "Topics" for the mouse buttons, which most new │ │ user will find confusing, why not label them "Related │ │ Topics" and "Help Index". That's what I did for my │ │ application and the help is a lot easier to understand. │ │ Ascii help files also poses a problem when the applicat │ │ ion is distributed. If I distribute a compiled CDD │ │ application on a BBS, someone can easily go into the │ │ help file and change the text, then resubmit it on │ │ another BBS. He could change my name and address, and │ │ put unsavory comments in the help file. There's enough │ │ problems with viruses, let's not encourage more │ │ meddling. There should be a way to encrypt the help │ │ file via a check box so this doesn't happen. Maybe in │ │ 3.1? │ │ Barry... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2261 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 8/30/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Title will get the Section name from the text file if │ │ you place <<section>> on that line. Why don't we take the │ │ section name if you leave it blank. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2319 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/10/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ Is there any way to change the physical size of a help │ │ screen ? The reason I need this is because the GUI sets the │ │ disp lay to 30 line mode and my help screens look short. My │ │ appl ication screens looked that way until I changed the │ │ physical size to 30 lines. │ │ Fred │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3095 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 11/18/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ help files, the text files for the help a user wants an │ │ attribute to help to indicate where to look for help so │ │ that he does not have to hardcode the path for the files │ │ nor will he have to have the text files in his path, so │ │ that the help text can belocated as he changes directories │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3852 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is desirable to have the ability to copy one helpid to │ │ another since the only things that _might_ be different │ │ would be the id itself and the topic. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3917 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/19/94 │ │ Reported In : 30071 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:56014 │ │ The same hot key is used for cOlors and Ok in the help │ │ system 'Update Help List Box' dialog. Most other places │ │ 'L' is the hot key for color. I suggest that this screen │ │ be changed accordingly. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3921 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/21/94 │ │ Reported In : 30071 RevisedDate : 2/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:56314 │ │ I think, a SEARCH button in the help system would be very │ │ useful to allow the enduser to search for the occurence of │ │ atext in the help text. thank you. Richard M. Brisslinger, │ │ Tutzing, Germany │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3945 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : J DateReported : 2/23/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3.0 user wants ability to chain from one help file to │ │ a particular help id of another within the help system │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4366 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/12/94 │ │ Reported In : 3008 RevisedDate : 4/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marjolein Katsma 100276,2414 MSG#:65410 │ │ >> There is no facility in CDD to design help at runtime │ │ like 2.1. There is no runtime like the processor.<< │ │ You shouldn't need a runtime to design helpscreen at │ │ runtime - why not a .DLL that you can explicitly refer │ │ ('link' with a .LIB to your program) while the program is │ │ still in its development stage. I'm sure that could be │ │ done. │ │ Could you log this as a suggestion, │ │ please? │ │ Marjolein Katsma o taxon │ │ /|\ │ │ o o o │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4737 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/26/94 │ │ Reported In : 3008 RevisedDate : 5/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Help Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglass Smith 70712,3650 MSG#:72971 │ │ Is there a way to import help screens from various hlp │ │ files? I have 2 or 3 Hlp files that I would like to │ │ combine into a single hlp file, if there's an easy way to │ │ do this other than recreating each one at a time, please │ │ let me know. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0428 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 4/08/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SETTEXT() - Repositions mouse to approx position 1,1 │ │ Could this be modified to save the mouse(x,y) │ │ and if it is within the range of the new │ │ SETTEXT() then to reset the mouse(x,y) to the │ │ saved (x,y)? │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0476 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/18/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Language problems: │ │ Using the SELECT(field,queue pointer) version of the │ │ SELECT command for a list box frequently generated │ │ undesirable results. Fixed │ │ When defining hot keys for pushbuttons codes like │ │ EnterKey and EscKey seem to work fine but things like 'H' │ │ or 'S' do not. │ │ Linker problems: │ │ I get an "unexpected group definition" error from the │ │ linker fairly often. The error will usually go away if I │ │ change the amount of code in the module file. At worst I │ │ can usually get by with deleting a procedure from my │ │ application and re-create it. When I do this APPGEN places │ │ the re-created procedure in a different module which seems │ │ to eliminate the error (at least temporarily). When the │ │ error reappears it is usually in a different module and │ │ does not seem to be directly related to any specific code │ │ segment. I am primarily using browse, form, screen, and a │ │ few source templates. │ │ In version 2.1 compilation would stop if the program │ │ module contained an error. In version 3.0 every module is │ │ compiled and optimized regardless and a link is attempted │ │ even if one or more of the modules had an error. This can │ │ be very time consuming. Use Abort Debug Switch │ │ Environment suggestions: │ │ The shortcut keys used by Topspeed are somewhat different │ │ than those used by Clarion. It does not seem fair to insist │ │ that the Topspeed users suddenly adopt Clarion conventions │ │ nor vice versa but a consistent interface would be very │ │ helpful. Your use of a style file to handle the use of │ │ colors in Clarion programs is extremely useful. A similar │ │ approach to defining the available shortcut keys throughout │ │ both environments would be very helpful. Good, hard to do. │ │ End of problems and suggestions (for now). │ │ I do have a question. Which is more important when │ │ looking for a computer to develop Clarion 3 programs, more │ │ memory or a faster CPU? I have a 386-20 with 2meg of ram. │ │ Compile times can get rather extreme even on a small │ │ project. I apologize for the length of this message but I │ │ hope that you find my comments useful. You have an │ │ excellent product here, keep up the good work. --> │ │ Both our helpful. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0674 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 3/26/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Can't pass a report detail,header, or footer as external. │ │ *DETAIL not supported as an external parameter │ │ *HEADER " │ │ *FOOTER " │ │ Will this be supported. │ │ Q & A : You can pass the report but not the entities inside │ │ the report. │ │ R & D : For version 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0780 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/06/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Welch 76702,1402 │ │ Hello Bruce. You called me about 2 weeks ago to compliment │ │ me on the interface I have created in my demo program │ │ xTracker. I see that Clarion 3 handles fonts differently │ │ than 2.1. I have gotten my fonts working with 3.0 except in │ │ the case of executing a RUN. The problem is that the fonts │ │ clear back to standard. My suggestion is to add aparameter │ │ to the RUN and RUNSMALL that would cause the fonts to not │ │ be reset. Currently all program I am writing use my own │ │ font kit. I run my own C programs and some 3rd party │ │ programs in windows in my Clarion programs so that the user │ │ never knows he is in another program. Resetting the fonts │ │ destroys the look of my screens. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0786 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 4/06/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Low Level Keyboard IO change. The program now works like │ │ version 2.1 in that the grey asterix ( '*' on the numeric │ │ keypad) cannot be used when entering into a string entry │ │ field. │ │ This would be a nice addition to the keyboard handling as │ │ the users may want to use this key when entering a file │ │ mask on the FILE template. '*.*' │ │ Q & A : 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1039 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/15/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Hugh E. Aaron 71562,221 │ │ Is it possible to modify the PRINT(string) procedure to │ │ accept a device attribute. │ │ For example: PRINT(string,device). │ │ This change would allow me to modify LTC to support │ │ devices other than LPT1. I could send you the names of a │ │ lot of devoted Clarionites (i.e., my customers) who would │ │ like this change. │ │ Thank you for considering these suggestions. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1681 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/29/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Advantage Software 100116,3350 │ │ L.S. │ │ At the moment, TYPE(@LF) cause a LineFeed/CarriageReturn │ │ pair (<10,13>) to be sent to the Standard Output (usually │ │ the screen). As the standard output may be redirected to a │ │ file, however, please consider changing this pair to the │ │ DOS textfile standard CarriageReturn/ Linefeed (<13,10>), │ │ so one can type e.g. PROGRAM > DUMPFILE.TXT │ │ on the DOS command line. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2007 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/28/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Thomas D. Stevens 71726,367 │ │ >> Hmmmmm... the V3.0 LRM states 1 to 65,535 on page 3-10. │ │ So, maybe ALL() >> should return 65,535 is no parameter │ │ is passed. │ │ Or better yet, why not have it default to the length of the │ │ destination string? Could you add this as an R&D suggestion │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2125 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/13/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gary Finlay 100270,3006 │ │ The problem is that the accounting software only allows any │ │ of the following characters to be entered as an account │ │ reference 'ABCBDEFGHIJKLMNOPQRSTUVWXYZ1234567890'. That is │ │ the alphabet in upper case and the numbers 1-0. │ │ I can write a function to check the contents of the │ │ field _after_ it has been accepted but I'd like it to be │ │ more elegant than telling a user that s/he has entered a │ │ wrong character. In other words check it on the fly. If a │ │ wrong character is typed - then don't allow it there and │ │ then as it's being entered - in fact don't even let it │ │ appear in the field. I'm rewriting the app. which I wrote │ │ many moons ago in TAS. In TAS a line of code to cover the │ │ above would look something like the following... │ │ enter(CUS:CODE),upper,mask('ABCDEFGHIJKLMNOPQRSTUVWXYZ12345 │ │ 67890') │ │ If a character other than contained in the mask was typed │ │ into the field the speaker would beep and it would not │ │ appear. │ │ To Greg. ----------- │ │ Field entry in CDD has a large number of │ │ parameters. Any hope of one more to include an entry mask? │ │ Could you pass this idea on to those who matter for │ │ consideration in a future release of CDD? │ │ Gary Finlay (Dublin, Ireland) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2128 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/13/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: LARRY TEAMES 73150,104 │ │ Does CDD's IDE allow for setting the EXTERNAL attribute for │ │ a variable (other than thru hand coding the entry in the │ │ data area, which then eliminates the ability to call it in │ │ thru other IDE screens with CTL-F)? │ │ I understand (I think) that you're saying to use │ │ EXTERNAL in the DLL, not the main program which will call │ │ it, but we still use the IDE to create the DLL. │ │ Do you anticipate support for the EXTERNAL │ │ attribute when creating a variable via the IDE approach? │ │ Larry Teames -- Creative PC Solutions -- AZ │ │ CUG │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2170 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/20/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Patrick Donnelly 73730,1215 │ │ Perhaps add the Unsigned Bshift (UBSHIFT) and leav e the │ │ present Signed version (Or make the Signed Bshift "SB │ │ SHIFT"). I dont't think everyone will be happy unless │ │ there are both 'Flavors' of BSHIFT, Just my thoughts, │ │ Pat │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2305 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/07/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Gary Finlay 100270,3006 │ │ It would be a good idea to provide a means to │ │ UnLoadBorder()in a future release of CDD so that people who │ │ want to so don't _have_ to buy the API kit? │ │ Gary Finlay (Baile Atha Cliath, Eire) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2470 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/27/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 │ │ If you want to enable all pulldown items try │ │ Enable(-1,?Most_left_and_lowest_pulldown_item) │ │ Might there be something else more generic? In most │ │ situations I think your suggestion will help but when it │ │ comes to templates ... │ │ Suggestion: Allow some way of determining the │ │ last pulldown item. Kind of like Fields() which returns │ │ the number of fields on a screen but doesn't work on a │ │ pulldown. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2500 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/29/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: ed steinberg 72425,1402 │ │ Array initalization: how 'bout 'lowing 'em to be initaliz │ │ edby xx,xx,xx,... on the Initial Value line. Strings could │ │ be 'abc','def',... │ │ From Greg_W: │ │ Example: │ │ myarray string(5),dim(3),('yes','no','joe') │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2589 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/07/93 │ │ Reported In : 3005 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a Checkbox has text associated with it. A user would like │ │ to have the ability to give it no text so that when the │ │ checkbox is selected, only the three characters that create │ │ the checkbox are highlighted. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2676 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/18/93 │ │ Reported In : 3005 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ eject subtitle title -- these compiler directive are said │ │ to do something for a clarion listing in the 3.0 manual. │ │ Where can i get a clarion listing? If nowhere, do we plan │ │ on creating this? If not, Can we mention that these │ │ statements do not do anything? │ │ QA: This may be done in a future release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2679 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/18/93 │ │ Reported In : 3005 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you try to link in some Modula-2 code into a Clarion │ │ program in overlay mode you get linker errors. Below is │ │ some test code that shows the problem: │ │ MODULE Test; │ │ IMPORT FIO; │ │ VAR │ │ f : FIO.File; │ │ BEGIN │ │ f := FIO.Open('Fred'); │ │ END Test. │ │ ---------Project file--------- │ │ #system auto exe │ │ #model overlay │ │ #compile %main │ │ #set tscla=on │ │ #link %prjname │ │ -------Error Messages---------- │ │ SYSTEM$TRANSFER is unresolved in file ro_m2.lib │ │ SYSTEM$NEWPROCESS is unresolved in file ro_m2.lib │ │ SYSTEM$CurrentProcess is unresolved in file ro_m2.lib │ │ SYSTEM$initprocess is unresolved in file ro_m2.lib │ │ __getTID is unresolved in file ro_m2.lib │ │ R&D: This is because the overlay and dynalink models of the │ │ TopSpeed MODULA-2 libraries are built to support │ │ multi-thread programming. This is not the case with │ │ Clarion libraries and hence the problems follow. We are │ │ consisdering some options for making the two systems more │ │ compatible, but in the mean time, you may want to consider │ │ using the static (xlarge) or extended models which are not │ │ multithreaded. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2832 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/01/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Patrick Donnelly 73730,1215 MSG#:39664 │ │ RE: Clarion V3 Language Reference P 13-14 "Valid numeric │ │ characters are the digits 0 through 9, a leading minus │ │ sign,and a decimal point." I also note the the 2.1 manual │ │ (3rd rev) P13-15 is similar but allows for leading spaces. │ │ A possible solution would be a change to the │ │ Language and adding a optional parameter specifying a │ │ Numeric base oran "S" for scientific. Any charecter not part │ │ of the specified base would return false. For │ │ example, if base was 16 then alpha "A" thur "F" would also │ │ return true, whereas abase of 8 would return false for an │ │ "8" or "9". │ │ This suggestion comes from the fact │ │ that NUMERIC returns true when there is an E in the │ │ string. ie, '1234E456' │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2870 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/02/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GERALD ME 100267,1023 MSG#:40025 │ │ ROWS and COLS return the number of rows or columns used by │ │ the current active window, not the windows structure that │ │ pass to the function. │ │ From Greg_W: I duplicated this bug test file 2870.zip │ │ R&D: This requires a compiler change because the compiler │ │ does not pass any parameters ro the ROWS and COLS │ │ functions. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3011 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/10/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Ward R. Johnson 70164,3136 MSG#:41848 │ │ Does the dynamic index support offset/length parameters, │ │ such as: │ │ build(pre:dynakey,'+pre:zip_code',offset,len) │ │ where, if offset was 0 and len was 2 might give you an │ │ index based on the first two numbers in a zip code field. │ │ Please say yes, or, "we'll have that in 3007." <g> │ │ -Ward Johnson 09-Nov-93 8:43a PDT │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3084 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JH DateReported : 11/17/93 │ │ Reported In : all RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would really be neat if the OPT attribute for KEY and │ │ INDEX could have an optional parameter pointing to some │ │ other field (or fields) in the record. (e.g. I would like │ │ to look at customers in name sequence but only if he owes │ │ me money.) │ │ CUST_KEY KEY(CUS:NAME),OPT(CUS:BALANCE) <- new │ │ CUST_KEY KEY(CUS:NAME),OPT <- work like now │ │ CUST_KEY KEY(CUS:NAME),OPT() <- same as no paran │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3104 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 11/19/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a request was put in to have an extra parameter for the │ │ help statement to give another help id for a default screen │ │ in case the other help id has not been created yet. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3156 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/29/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:44267 │ │ Can it be placed on the suggestion list to have a function │ │ that will change the field() return like the setkeycode() │ │ changes the keycode() ? │ │ Suggestion for a function SETFIELD() to set the value │ │ returned from FIELD(). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3510 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 1/12/94 │ │ Reported In : 3006 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: DOUG ANDREWS 73740,2622 MSG#:49781 │ │ program │ │ num decimal(10,0) !happens with Decimal(11,0) also. │ │ code │ │ num = 9876543210 │ │ t" = format(num,@n_10) │ │ ask │ │ When I run this code (using 3006), I get a floating point │ │ error. The error occurs when the format is executed. If │ │ you change the format token to @n_11, it works OK. │ │ I tried it in both protect mode and dynalink. │ │ Thanks Doug Andrews │ │ R&D:Doug this is a result of the compiler optimizing the │ │ code generated so that you don't have to use temporary │ │ floats for all internal calculations (which would slow your │ │ program to a crawl). When the compiler sees @n_10 it │ │ takes a chance that the number will fit in a long (much │ │ faster than float). Unfortunately even an unsigned long │ │ will only fit 4294967296. Consequently, when the │ │ conversion function in FORMAT tries to store it in the │ │ temp. long it causes an overflow exception to indicate that │ │ the number can not be represented. The @n11 works because │ │ the compiler knows full well an 11 digit decimal can never │ │ be represented by a long, and so full float arithmetic is │ │ used. You might say the compiler should not assume that an │ │ arbitrary 10digit number will fit into a long, we will take │ │ this under advisement. Thank you. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4172 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30071 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:61342 │ │ Your reference to this use of a list box reminded me that │ │ I've been meaning to request the ability to scroll lock a │ │ list.. If we could lock the scrolling mechanism, it would │ │ save the user from having to press the UP/DOWN arrows 20 │ │ times to initiate movement and navigate the list. │ │ For those instances where record selection wasn't │ │ desireable(e.g., viewing an ASCII file), this new list │ │ attribute/feature would be very helpful. It would │ │ also negate the need for a highlight pointer, │ │ which seems a little out of place when only "viewing" text. │ │ Since the Clarion help system also uses the list box │ │ technique, it would also benefit from scroll locking, │ │ (though hypertext links would need to be enhanced to │ │ include an alternate (and possibly more industry standard) │ │ reference to hot points. │ │ Mabe R&D can give this some │ │ consideration for "a future release of CDD". │ │ Thanks, │ │ Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4173 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I wish I could "Re-Alias", but alas, no such function │ │ exists. Hence this │ │ thread. You see, the problem is that the called function │ │ has no idea what │ │ alias (if any) exists for a given keycode. It can Alias │ │ whatever it needs, but │ │ it can't restore the alias table to its prior condition │ │ upon exit. Then the │ │ calling procedure's aliasing is potentially destroyed. The │ │ calling procedure │ │ could certainly reset any aliases it has set following │ │ _every_ call to any │ │ function or procedure that might reset alieses, but what a │ │ nightmare to try to │ │ maintain that beast. This is, IMO, much needed │ │ functionality, unless I'm │ │ missing something. Thanks! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4208 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion for a CENTER attribute for a screen variable │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4324 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 4/07/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants the ability to pass a RECORD to a function │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4372 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/13/94 │ │ Reported In : 3008 RevisedDate : 4/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John T. Giles 72142,1223 MSG#:65213 │ │ How about a new command called BulkNext. Is would go │ │ something like BULKNEXT(file,queue,quantity). This would │ │ make the reads in a browse faster. It could also be use for │ │ the batch system as well. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4838 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 6/15/94 │ │ Reported In : 3009 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3.1 suggestion - how about a progress indicator option on │ │ the build statement, either indicating percenage built, or │ │ the key currently building. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4927 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 7/11/94 │ │ Reported In : 3009 RevisedDate : 7/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like to be able to use variables for a pulldown │ │ ITEM. ITEM(myvar),... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5266 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/16/94 │ │ Reported In : 3009 RevisedDate : 8/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ PRINT statement change to suppress CRLF │ │ Section │ │ Language Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Larry Teames 73150,104 │ │ >> And are you wanting the PRINT('somestring') not to send │ │ a CRLF or PRINT(detaillabel) not to send a CRLF on certain │ │ lines with say a nocrlf >> attribute. │ │ This is EXACTLY what we've been asking for since before │ │ 3002! If you've done much work with CPD or CDD related to │ │ LASER PRINTERS, you understand the problem. Although I │ │ don't go overboard on DotMtx printers, others do, and the │ │ CrLf issues gets in the way there also. │ │ At least with a "NoCrLf" attrib, we (the developers) │ │ would be back in control. It's understood that we may │ │ create problems for ourselves if we don't handle its │ │ use appropriately, but that in itself would be a │ │ major stride forward. │ │ Actually, in CDD, it would be preferable to │ │ have the "NO CrLf Attrib" available in Reports (where │ │ Device is already supported), AND to have an optional │ │ parameter added to the PRINT() statement: │ │ PRINT(SomeData[,DEVICE]) <- add │ │ the *optional* Device parameter │ │ If necessary, leave it to us │ │ "whiners" to come up with a way to deal with the │ │ (probable) extremely long "control" strings in the view │ │ template (ascii driver). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0676 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TM DateReported : 3/26/93 │ │ Reported In : 3002 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ List Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Locator, Selector, and Filter support would be useful. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1267 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ List Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ double-click to change?? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4322 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/07/94 │ │ Reported In : 3008 RevisedDate : 4/07/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ List Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jon B. Bushey 71521,2267 MSG#:63840 │ │ It would be REALLY, REALLY nice to have an EMBED in the │ │ list template, in the QUEUE used for the screen. It should │ │ be right after the LINE, which is the string displayed on │ │ the list box. The embed would allow more fields to be │ │ added to the queue. The fields could be used for sorting, │ │ marking, tagging, etc. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4360 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/12/94 │ │ Reported In : 3008 RevisedDate : 4/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ List Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 MSG#:64107 │ │ Shouldn't the List procedure have a check-box for "Disable │ │ Memo Access" like the browse does? │ │ --David │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0774 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 4/05/93 │ │ Reported In : 3002 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion for embed after update procedure │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1270 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ TEMPLATES IN GENERAL :: If a template supports the formula │ │ generator there should be an embed for this: there is one │ │ in some of the templates but not all. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1325 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/24/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Martin Wehlou (Cactus) 72047,2444 │ │ Paul, │ │ About message strings in the templates: I don't know if │ │ it's feasible, but if all message strings could be gathered │ │ together into one of the template files as equates or │ │ something, it would help. For us guys writing programs for │ │ a non-english audience, we have to change *all* template │ │ files. Not just once, but for each language version of our │ │ apps. │ │ Lotsa sweat... │ │ Bears thinking about, doesn't it? │ │ --Martin │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1404 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/31/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ even though we have relationships for lookups,; provide an │ │ old style lookup field so they can do a lookup with out │ │ coding it by hand each time. This could be useful for that │ │ second lookup as in two fields in one file trying to make │ │ use of that same lookup to one field in another file. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2044 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 8/05/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion by user -- why not checkopen all files in the │ │ other data section of the file skematic -- If I placed a │ │ file into that section to place a field on the screen that │ │ file will have to be opened. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2207 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/24/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 │ │ An example: │ │ Two files: Items and Categories. The Categories file has │ │ two keys, primary key is autoincremented (i.e. the record │ │ number), second key is based upon a category description. │ │ The Item record has a field that contains the "Category │ │ Record Number". This number is of no interest to the │ │ end-user and will be hidden from them. The relational link │ │ is in this "hidden field". The User will always see the │ │ categories presented by description. This is NOT an │ │ uncommon way to link lookup data. │ │ The templates as they exist for 3004 │ │ appear to assume that the actual link fields will be on the │ │ screen. As a result, the "hidden" links are destroyed by │ │ the secondary lookups coding. │ │ Its possible to work around the │ │ problem, but IMO the templates should be able to handle │ │ these simple relationships correctly. │ │ --David │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2361 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 9/21/93 │ │ Reported In : 3005c RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From Scott Smiley - Suggestions for Browse: │ │ Why not call the Update form in all cases of NoRecords? If │ │ you are entering records from a 2ndary Browse it is │ │ confusing for a user to call the Update form for the first │ │ record but not any of the subsiquent records when using a │ │ range limit on secondary browses. │ │ Of NoRecords │ │ If Records(%Primary) │ │ Select() │ │ Else │ │ Updateform │ │ End │ │ ..... │ │ MultiPage Template: │ │ In the of ?Cancel why not call the RelationalDelete │ │ instead?It is possible to add secondary records while │ │ adding a parent record then cancel the parent record. │ │ Q&A: This was not concidered in the original │ │ design of the templates, I guess the same would be true │ │ for the FORM Template also. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2487 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/28/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Crenshaw 75110,531 │ │ Can you tell me if there is any plans to add Range From and │ │ Range To support in the Browse, Select, and Validate │ │ templates. I know you can do that with a filter but I want │ │ a range based on the key. │ │ EX: key with 2 elements, last name then first name. │ │ I need a browse that can display records between a range │ │ based on the first element of the key. │ │ In it's current implementation the range field is │ │ an exact match only. I managed to circumvent this by adding │ │ a check box that allows me overide the default range check │ │ then add and embedd point for my own range check. The reason │ │ that I won't use a filter is TOO SLOW , I want to hit on │ │ the key dispthe records and get out of there. │ │ John Crenshaw CIS 75110,531 CPD 2108/CDD │ │ 3004/LPM 2.1 NavCis Windows NavCIS SE v.1.01 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2592 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/07/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ wants the lookup to act just like 2.1 where it ALLWAYS goes │ │ into the table even if it is correct. and it would be nice │ │ if it went to the closesest match. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2613 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 10/13/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestion by a user: │ │ In BROWSE.CLA under ProcessForward and ProcessBackword, he │ │ suggest it should say IF ~ERRORCODE() OR ERRORCODE() = 43 │ │ to handle held records. │ │ If you need further information, refer to project 2458. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2693 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 10/18/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestions from a user: │ │ 1. I would like for the Global Data Sections Embedded │ │ source point to be moved from after the program's file │ │ definitions to before the file definitions. I n my │ │ program, I INCLUDE a source file in the global data │ │ section's embedded source point. This source file has file │ │ NAME variables which must be declared before the file │ │ structures. I am INCLUDEing thes varibales rather than │ │ defining them in the application generator so that I may │ │ share these varibale definitions with several other │ │ programs. I can see no harm in moving the embedding point │ │ and hope that you will find this to be a good suggestion. │ │ I would also like to suggest that the Document External │ │ Source Modules procedure type be modified so that it will │ │ allow files to be entered in the FILES screen. I have │ │ several source modules which are shared by several │ │ programs. For reasons I will not go into, these modules │ │ require the file definitions they use to be with the main │ │ program file definintions. Since some of these modules use │ │ files which are not used anywhere else in the program, I │ │ need some way to tell teh application generator to include │ │ the file definitions fo these modules. I can see no │ │ adverse effects from enableing th Files button to allow │ │ files to be included in the program source. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2791 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/26/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:38853 │ │ Has any thought been given to using a style file to create │ │ the screen colors in clarion.app? Now, to use style files, │ │ I have to recolor every screen in the clarion app any time │ │ there is an update. If you guys used a style file for │ │ these screens, then we could easily create our own from │ │ the one that was used for clarion.app. │ │ Regards, │ │ Randy Rogers │ │ Keystone Computer Resources │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2811 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 10/28/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When using change template form a browse to a list, it is a │ │ straight converstion except for the fact that the list uses │ │ line for the "from" for the list box and the browse uses │ │ queue. We might want to consider changing this to make │ │ them compatible. Or maybe we could generate a generation │ │ error #error to alert them of this. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2922 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Make a globle Access Mode Variable, assign it, │ │ %AccessMode:Glo:AccessMode Byte(%AccessMode) │ │ 2. Change the CheckOpen prototype to: │ │ CheckOpen(*file,<bytes>),byte │ │ 3. After the check open function to: │ │ CheckOpen Function(File,AccessMode) │ │ Code │ │ If ~AccessMode │ │ AccessMode = GLO:AccessMode │ │ END │ │ Open(File,%AccessMode) │ │ ........ │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2991 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 7/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Wayne Freeman 76314,2100 MSG#:41496 │ │ I've taken care of a shortcoming in the InitFields routine │ │ in Clarion5.tpx, and I thought I'd share it with you. │ │ The shortcoming is that if you want to set an initial │ │ value on a dimensioned field, the generated code is missing │ │ all appropriate subscripts, causing syntax errors. │ │ Here's the original template code: │ │ #GROUP(%InitFields) │ │ #IF(%InitRoutine = 'TRUE') │ │ InitializeFields ROUTINE │ │ #FOR(%Field) │ │ #IF(%FieldInitial <> %NULL) │ │ %Field = %FieldInitial │ │ #ENDIF │ │ #ENDFOR │ │ #ENDIF │ │ Here are my proposed changes (worked for me): │ │ InitializeFields ROUTINE │ │ #FOR(%Field) │ │ #IF(%FieldInitial <> %NULL) │ │ #IF(%FieldDimension1) │ │ Loop Idx1# = 1 to %FieldDimension1 │ │ #IF(%FieldDimension2) │ │ Loop Idx2# = 1 to %FieldDimension2 │ │ #IF(%FieldDimension3) │ │ Loop Idx3# = 1 to %FieldDimension3 │ │ #IF(%FieldDimension4) │ │ Loop Idx4# = 1 to %FieldDimension4 │ │ %Field[Idx1#,Idx2#,Idx3#,Idx4#] = │ │ %FieldInitial End !Loop Dimension 4 │ │ #ELSE │ │ %Field[Idx1#,Idx2#,Idx3#] = │ │ %FieldInitial #ENDIF │ │ End !Loop Dimension 3 │ │ #ELSE │ │ %Field[Idx1#,Idx2#] = │ │ %FieldInitial #ENDIF │ │ End !Loop Dimension 2 │ │ #ELSE │ │ %Field[Idx1#] = │ │ %FieldInitial #ENDIF │ │ End !Loop │ │ Dimension 1 #ELSE │ │ %Field = │ │ %FieldInitial #ENDIF │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3007 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/10/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nik Johnson 70733,2247 MSG#:41923 │ │ 1) Suggestion: To be able to check for the existence of │ │ whether there was any embedded code. │ │ #if embed1 │ │ add this code if this embed was used │ │ #end │ │ The value of CDD3 lie in the ability to create and debug │ │ templates (macro-programming) rather than creating and │ │ debugging individual programs (micro-programming). Doug's │ │ idea of having "standard" code which can optionally be │ │ replaced by an embed is a really good one, and the │ │ language should support it. │ │ 2) While you're at it, could you ask whoever generates file │ │ structures to include the comments from the dictionary? We │ │ really don't put them there for our health ... they have │ │ value in the generated code. -Nik │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3045 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/12/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:41606 │ │ Debby, │ │ Is there a way to reference an #EMBED in templates such │ │ that one could do the following: │ │ #EMBED('Custom Embed Point') #IF('Custom Embed Point' │ │ = %NULL) DO SomeRoutine #ENDIF │ │ Douglas │ │ R&D: 3.1 design change for #EMBEDs will extend the syntax │ │ to: #EMBED(%symbol,description)... it has debated if this │ │ will enable the #EMBED to be expanded through symbol │ │ reference!?!? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3094 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 11/18/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ As a developer, I need Global Hot Procedured that can be │ │ defined in the Global section of the app. For example, I │ │ may want a Calculator to be available in every procedure, I │ │ want to declare this procedure and assign a hot key once. │ │ BTW, LPM has this feature. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3121 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/22/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:43570 │ │ There does not seem to be a way to *see* the Queue Prefix │ │ inthe Templates, even if something was in │ │ %ScreenFieldQueue. │ │ FROM VINCE: Yes, this is true... this highlights the larger │ │ issue of not being able to access individula data items │ │ in general! This may be addressed in the future. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3161 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/29/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick LaBanca 71172,2250 MSG#:44342 │ │ It would be nice if templates that read records based on │ │ filters would only search the key based on the range │ │ specified (assuming that your filtering on a key component) │ │ Example: │ │ access key: date_key │ │ begin range: glo:begin_date │ │ end range: glo:end_date │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3206 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/03/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rod Mills 70471,65 MSG#:44791 │ │ I've noticed that many of the Template types (such as │ │ Screen) that allows you to define Pulldown Menus do not │ │ havethe Sticky Menu code. Will future revisions have this │ │ code, and if it hasn't been planned, could you pass my vote │ │ to thefolks in development? Thanx! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3219 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/06/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marjolein Katsma 100276,2414 MSG#:45202 │ │ 1. #PROMPTs in #GROUPs. │ │ The more I do with the templates, the more I │ │ realise that having the possiblity of #PROMPTs in #GROUPs │ │ is absolutely essential for a truly interactive template │ │ language. I suppose the Template Processor uses │ │ the #PROMPTs in a template to 'format' the properties │ │ window for the type of procedure defined by that template. │ │ Since the inclusion or not of a #GROUP can be dependent on │ │ conditions not know at the time of processing the │ │ template chain, I suppose it's impossible to include │ │ #PROMPTs from a #GROUP in that same window. So here's my │ │ suggestion: Have the template processor format a 'child' │ │ window for each #GROUP that has any #PROMPTs - this child │ │ window can then be popped up at design time if and when │ │ the conditions for inclusion of that particular #GROUP are │ │ met. │ │ 2. #SETting a default for a #PROMPT. I tried to do this, │ │ and found it didn't work: use #SET to give a 'default' │ │ value to a user-defined symbol. After that, use a #PROMPT │ │ _for that same user-defined symbol_ to let the programmer │ │ change the default value set by #SET if desired. │ │ I found first of all, that the entry field for the │ │ #PROMPT came up empty, i.e. the #SET value did not appear. │ │ Secondly, when I did fill in the entry field, I found that │ │ what took effect was the value from the #SET statement; the │ │ entered value was ignored. I see no reason why this could │ │ not work; such a 'default' mechanism is completely │ │ consistent with the concept and syntax of the template │ │ language and would be very useful, e.g. where naming │ │ conventions are important but may have to be overruled in │ │ special cases. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3223 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 12/06/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Where is the percent symbol for reclaim attribute and the │ │ charcter count such as 20 for a string filed? │ │ R&D: All needed built-in template symbols will again be │ │ addressed in the next release > 3.7... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3363 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 12/21/93 │ │ Reported In : 3007b RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the folowing templates have hotletters being used more than │ │ once: │ │ browse : a e d l │ │ form : a n i │ │ pulldown: s │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3589 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/24/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I suggest we increase the size of REPORTDEVICE. Currently │ │ it is a string(30). The filename takes half of this and │ │ does not leave much room if current directory is nestled │ │ within some subdirectories. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3711 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/07/94 │ │ Reported In : 3007 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 53336 S8/3.0 Support │ │ 02-Feb-94 17:46:31 │ │ Sb: 3.007(1) templates │ │ Fm: Advantage Software 100116,3350 │ │ To: sysop │ │ L.S. │ │ This list shows all uses of #IF and #ELSIF (in this │ │ order) │ │ in 3007.1 *.TP? files, where there is a check on a string │ │ constant with letters in it, and where the Template Symbol │ │ is │ │ not UPPERed. │ │ While this might be correct in those cases where the │ │ Template │ │ Symbol is system-assigned only, it is quite certain │ │ incorrect │ │ when the value can be user-assigned (like │ │ %ScreenFieldUse). │ │ e.g., when a user enters the field-equate label of the │ │ cancel │ │ button as ?cancel in stead of ?Cancel (like I myself │ │ happened │ │ to do once), the #IF(%ScreenField = '?Cancel) will │ │ evaluate │ │ FALSE, where #IF(UPPER(%ScreenField) = '?CANCEL) would │ │ evaluate TRUE. As many Template Symbols (like field equate │ │ label) are given a default value, which most users seldom │ │ change, this error might go untrapped for some while... │ │ The [numbers] show the original line number in the │ │ template. │ │ The ------ lines show the name of the template file. │ │ In this list I have not made difference between system (or │ │ template) assigned symbols and user-assigned symbols. │ │ See text file of his list 3711.zip │ │ R&D: This will (soon) no longer be a concern as │ │ evaluations in the template will be case insensitive. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3953 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/24/94 │ │ Reported In : 30071 RevisedDate : 2/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 57197 S3/2.1 Support │ │ 23-Feb-94 20:24:30 │ │ Sb: #57096-2 Tables on 1 Screen ? │ │ Fm: David Silver 74145,1546 │ │ To: Debby Herman 72662,475 │ │ There is a file on this bbs called clrlst.zip. This file │ │ demonstrates the ability to have conditional colors in a │ │ list box. However the example is pure hand code and not │ │ verywell documented. In any event I attempted to apply the │ │ technique to a module created by the app generator using │ │ thebrowse template however each time the code passes │ │ through the borwse procedure, the color reverts back to │ │ normal. I traced through the browse procedure and found │ │ this was occuring at the accept statement. The browse │ │ procedure is very poorly commented and thus will be │ │ difficult to modify. My question was , perhaps your new │ │ template developer could point me in the right direction to │ │ change the browse template to accept conditional │ │ colors for the list box. David SIlver md │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4050 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 58516 S8/3.0 Support │ │ 03-Mar-94 18:02:51 │ │ Sb: ScrnFlds.Tpx Made Clear │ │ Fm: Douglas Johnson 75310,2035 │ │ To: Debby Herman 72662,475 │ │ For Tom Moseley: │ │ A small point, but perhaps a help in maintenance - │ │ GROUP %PrimeLookup in ScrnFlds.Tpx contains the following: │ │ #ELSIF(%LocateField) │ │ #FOR(%File) << │ │ #FIX(%Field,%LocateField) << │ │ #IF(%Field) << │ │ #SET(%LookupFromFile,%File) << │ │ ... check a bunch of stuff ... │ │ #BREAK │ │ #ENDIF │ │ It seems to me that the same thing could more easily be │ │ accomplished │ │ by getting rid of the FOR Loop and simply having: │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4052 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas Johnson 75310,2035 MSG#:58750 │ │ If one takes the #PROTOTYPE('') out of the templates, then │ │ the programmer has control over it. It looks just like │ │ another #PROMPT and I'd like to be able to use it in │ │ exactlythe same way - that is, have the contents in a │ │ %Prototype symbol just like %Primary, %PrimaryKey, │ │ %Procedure etc. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4144 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Richard M. Bri~linger 100120,1622 MSG#:60533 │ │ Hello, there seems to be a buggy situation when viewing a │ │ report on screen. The problem comes up if you - use the │ │ variable REPORTDEVICE as parameter for the DEVICE() │ │ attribute of the report (this happens by default in │ │ CDD) - use REDIRECT and VIEW to view the report on screen - │ │ and this in a directory with a long pathname │ │ what happens is: │ │ REDIRECT generates a temporary filename │ │ preceeded by the path; in my case │ │ 'C:\CLARION3\EASYMAIL\RPT00001.$$$' and puts this filename │ │ into GLO:FILESPEC The report then │ │ copies GLO:FILESPEC to REPORTDEVICE As REPORTDEVICE │ │ is declared in CLARION.APP as a string(30), the filename │ │ is truncated to 'C:\CLARION3\EASYMAIL\RPT00001.' So ,the │ │ report creates a file 'C:\CLARION3\EASYMAIL\RPT00001' The │ │ VIEW procedure now tries to open the file with the name │ │ given in GLO:FILESPEC and stops with the errormessage │ │ 'Cannot open file 'C:\CLARION3\EASYMAIL\RPT00001.$$$' │ │ Short │ │ consequence of the long story: the variable REPORTDEVICE, │ │ declared in CLARION.APP in REPORT and PRINT must be │ │ string(64). │ │ Richard M. Brisslinger, Tutzing, Germany, CDD30072 + │ │ GUI │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4149 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/18/94 │ │ Reported In : 30071 RevisedDate : 3/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jerry L. Petri 72633,3345 MSG#:60367 │ │ As of 3007.2, the list template is missing the following │ │ functions to make it more usable. │ │ The list template does not have "Case no records" exit. │ │ The list template does not have Locator capabilities, │ │ need both regular & incremental. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4185 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/23/94 │ │ Reported In : 30072 RevisedDate : 3/23/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm:Marjolein Katsma 100276,2414 │ │ List of Suggestions and findings.... │ │ File: 4185.zip │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4283 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/04/94 │ │ Reported In : 30072 RevisedDate : 4/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Marjolein Katsma 100276,2414 MSG#:63860 │ │ There is no symbol for the RECLAIM attribute on a File │ │ either; should work just like %FileCreate (and be named │ │ %FileReclaim). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4414 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/18/94 │ │ Reported In : 3008 RevisedDate : 4/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:65735 │ │ Subject: Variable filenames in Clarion 3.0 Data Dictionary │ │ When using Clarion 2.1, we reuse a single global string │ │ variable (gFileName) as a filespec for _every_ database │ │ file opened. This saves us from having to declare a │ │ separate 64 byte string for every file (usually dozens). │ │ We need such variable filenames because our │ │ software operates on a network disk with unpredictable │ │ drive letters and paths being used from time to time. │ │ Can you please advise how we continue │ │ might do this using the 3.0 data dictionary and the code │ │ generator? The filespec field in DD may be a contstant or │ │ variable, but there doesn't appear to be any way to manage │ │ the generated code so that it sets the actual filespec at │ │ runtime. If there currently isway, please enter this as a │ │ suggestion. │ │ Thanks, │ │ Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4637 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/10/94 │ │ Reported In : 3008 RevisedDate : 5/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The template language needs %RecordLen and %FieldLen │ │ variables, which would return the number of bytes of │ │ storagerequired. Alternatively, the function SIZE could be │ │ supported in the #SET statement. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4646 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/11/94 │ │ Reported In : 3008 RevisedDate : 5/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Don L. Galbreath 71544,2563 MSG#:70644 │ │ >> In a Screen Template, a Display is now very inconviently │ │ being issued after every Field Edit Embed. │ │ >>> This template code can be found on line 161 of │ │ SCRNFLDS.TPX. Image field always get displayed when a │ │ DISPLAY statement is executed. │ │ Thanks for pointing me to SCRNFLDS.TPX. │ │ At least now I can edit it to DISPLAY(?). However, I have │ │ tried not to modify the templates for this App. I │ │ understand the Image field is always re-displayed, but this │ │ code was not in 3006. │ │ After looking at SCRNFLDS.TPX: │ │ OF %ScreenField │ │ #<! Completed %ScreenFieldUse field │ │ %ScreenFieldEdit #<! Generate Edit │ │ Code DISPLAY #<! DISPLAY │ │ new value #ENDIF #! END │ │ (If Edit Code...) #ENDIF #! END (If Entry Field) │ │ Since │ │ this is "A" (read single) field edit, would it not be more │ │ appropiate to have DISPLAY(?) or DISPLAY(%ScreenField)? I │ │ could always put DISPLAY in my %ScreenFieldEdit if I needed │ │ it. │ │ ...Don │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4902 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/01/94 │ │ Reported In : 3009 RevisedDate : 7/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Misc. Templates │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I noticed on the Redirect screen the user can select "File" │ │ then if they accidentally hit ENTER or Select "Ok", they │ │ bypass entering the file name and the output gets sent to │ │ LPT1: instead of to a file. │ │ If "File" is selected, the user should be forced to enter a │ │ file name or the user should be given the opportunity to │ │ select a different destination (LPT1:, SCREEN, etc.). They │ │ should not be permitted to exit with a blank file name if │ │ "File" is selected. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0216 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Something to consider for XTRACE.TXT's and sporadic │ │ reboots: │ │ On my system, I have multiple copies of HIMEM.SYS and │ │ different versions of SMARTDRV. If the versions used didn't │ │ "ship together", I have all kinds of trouble, including the │ │ "General Protection..." messages and immediate re-boots. │ │ This happens on two different machines. │ │ I'm using only DOS 5 memory management, with HIMEM, │ │ EMM386, DOS=HIGH,UMB, etc, and have no problems if I use │ │ those that came with DOS 5. However, if I try to use a │ │ later version of SMARTDRV (the EXE version that came with │ │ MASM 6, for example), it'll reboot me as soon as │ │ CLARION3.EXE is started. If I return to using SMARTDRV.SYS │ │ that came with DOS 5, no problems even if using DEVICEHIGH. │ │ Using later versions of HIMEM.SYS seems to cause │ │ intermittent problems, too, which may be partially due to │ │ the mismatch between HIMEM and EMM386 versions. I'd rather │ │ use the later version of SMARTDRV (better, faster, │ │ write-caching, etc.), but I can't seem to with CDD 3. I │ │ guess the moral of the story is use consistent versions of │ │ matching drivers and utilities. │ │ Tony Kirk (AKA,CTJ) │ │ Q & A : May be resolved with XBCAST +-. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0343 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/12/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Will there be a 3.0 equivalent to the 2.1 Cross Reference │ │ utility? It would seem an essential part of the environment │ │ since without knowing the calling relationships between │ │ procedures it is hit and miss to decide how to consolidate │ │ procedures into the same module. Is this a function │ │ performed by the TS Profiler or will that be left to 3rd │ │ party developers? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0378 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/16/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Following are several requests for CDD 3.0. │ │ - I have a field on my data entry screen, with a USE │ │ variable. I want to find out what File this variable is │ │ part of. It seems like the natural way to do this would be │ │ to put │ │ #FIX(%Field, %ScreenFieldUse) │ │ and then to access %File. However, the "dependent │ │ multivalued symbols" only seem to work top-down, not │ │ bottom-up (as I am doing). Is there any way to determine │ │ the %File of a %Field without looping through all the files │ │ and fields with a #FOR loop? │ │ - It would be nice if the Generator had a switch so that │ │ #EMBED statements in the template DO NOT generate EMBED │ │ statements in the code. Sometimes I want to use embedded │ │ code to work around an issue and I can't because it assumes │ │ that my embedded code will be actual code statements rather │ │ than, say, a single variable name. │ │ - It would be nice if the Screen Field Properties allowed │ │ for an extra slot into which I could put my own │ │ information. Call it a "comment" or something, and make │ │ sure it can be accessed by the template. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0437 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/23/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Has any thought been given to assigning a KEYCODE to the │ │ ALT key when pressed by itself, so that instead of ESC(or │ │ other current keycode), a user can press the ALT key by │ │ itself to activate a Pulldown structure? │ │ This may not be in the strict definition of CUA compliance, │ │ but it is a de-facto standard, with Windows and most other │ │ "CUA" compliant progs using ALT alone to activate the menu │ │ bar. │ │ File this under the suggestion column, not as a bug or │ │ complaint. │ │ Thanks, │ │ Jerry Murdock - Atlanta User's Group │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0459 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/18/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On LR 3-31 it is stated that a file NAME attribute without │ │ a constant or variable defaults to the label of the │ │ declaration statement on which it is placed. │ │ Might it be suggested to R&D that the following be added: │ │ A file NAME attribute which ends with '\' APPENDS the label │ │ of the declaration statement on which it is placed. │ │ One variable, which contains only the path, could then be │ │ used for all files grouped within that one directory. This │ │ would be especially useful on a network where data files │ │ may be in several different directories over a couple │ │ of volumes with various access rights. Furthermore, the │ │ path to each directory could then easily be specified and │ │ maintained in an INI file. │ │ Does it make any sense to you? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0468 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/01/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ CDD is designed to be extremely extensible, with all sorts │ │ of provisions for adding external capabilities -- one │ │ application at a time. │ │ I believe CDD needs something very much like the database │ │ driver registration process, where I can specify a │ │ prototype for a function or a procedure, and specify the │ │ library that contains that function or procedure. │ │ Say I write (or download, or buy) a .CLA file or .DLL that │ │ contains a function, CALC(), that displays a calculator, │ │ takes no parameters, and returns a long into the currently │ │ selected field. │ │ I should be able to register that function in a Language │ │ Extensions Database (LED), then call it from any program. │ │ At code generation, CDD should recognize the call as │ │ unresolved in the current map and search the LED for a │ │ function or procedure prototype that matches the name and │ │ format of the call. The map and .PR file would then be │ │ modified to resolve the reference. │ │ In our example, I could specify CALC() as the setup code │ │ for a field. I would not have to change the .PR file or add │ │ the call to the map UNLESS I wanted to use a CALC() │ │ function different than the one registered in the LED. CDD │ │ would note that the call was unresolved, consult the LED, │ │ and add the call to the map and .PR file. Program │ │ compilation and linking would proceed as normal from that │ │ point. │ │ This would save any programmer considerable time during the │ │ development process, and would encourage the development │ │ and use of language extensions, in all forms. │ │ This would also eliminate a lot of duplication or │ │ shuffling. Once I develop a VIEWFILE procedure, for │ │ example, I could register it in the LED and stick a .DLL or │ │ .LIB or .CLA/.PR pair in \CLARION3\LIB. From that time on, │ │ I can use it in every program just by calling it. If I get │ │ a better VIEWFILE, I just replace the old one. If I want a │ │ special VIEWFILE for this particular program, I complete │ │ the design locally, the call is no longer unresolved, and │ │ the LED is never consulted. │ │ Oh, yeah, while I'm asking... the LED registration program │ │ should take command line parameters, so I could obtain a │ │ library from someone, run a batch file, and go to work. │ │ If a match to the current registry is found, offer an │ │ option to replace the current entry, ignore the new entry, │ │ or leave both in the database. At code generation time, if │ │ more than one entry is found in the LED for a particular │ │ call, display the libraries that contain both calls and let │ │ the developer select the one to be used. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0479 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/02/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Last week in the user group, in my millionth Clarion 3 demo │ │ to them, a fellow in the group made an interesting │ │ suggestion, towit: why not have a list box mix and match │ │ interface for piecing together template files? You could │ │ double click or press enter on the file you wanted to chain │ │ into the template you were building and a "process" button │ │ would ask you for a new name for the template and then take │ │ care of writing a comment in the first file and placing the │ │ correct "CHAIN" statements in the rest. The dialog might │ │ look like this: │ │ +--------------------------+------------------------------+ │ │ | Source Files | New Template: ACCOUNT | │ │ +----------------------------------------------+ │ │ | CLARION - Master file |CLARION - Clarion Master Defs │ │ | | CLARION1 - Browse (Def) |CLARION1 - Clarion Browse │ │ | | CLARION2 - Form (def) |MYTEMP1 - Special Functions │ │ | | CLARION3 - Menu (Def) | │ │ | | CLARION4 - | │ │ | | Pulldown (Default) | │ │ | | CLARION5 - etc | │ │ | | CLARION6 | │ │ | | CLARION7 | │ │ | | MYTEMPL | │ │ | | MYTEMPL1 | │ │ | │ │ +--------------------------+------------------------------+ │ │ | Select from Source with Mouse | PROCESS | │ │ | │ │ Mark │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0512 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/05/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There comes a time in every programming cycle when "wants │ │ and desires" go on a "wish list" for future enhancements. │ │ At some point in time, the development cycle has to stop to │ │ give way to the Quality Control cycle. │ │ I think CDD has reached that point. │ │ In 3001 we were given some pretty decent new features. │ │ However, many of them had problems. For those of us │ │ committed to using CDD, we can work around the problems. │ │ Its time to stop ADDING things. Put the programmers on │ │ HOLD. Give CDD to Quality Control and let them have it for │ │ as long as they need it. Keep the programmers around for │ │ "bug fixes" but stop them from implementing new features. │ │ Remember. There is always Batch 3001 (the real one, not the │ │ Pre-Release one). New features can be added AFTER CDD hits │ │ the streets. I'm thankful for the new things that │ │ Pre-Release Batch 3001 added (especially the File Selection │ │ Template), but I would have gladly paid the $29.95 upgrade │ │ fee to use the new features (especially for an upgrade that │ │ is bug free). │ │ I think Clarion needs some DEDICATED Quality Control │ │ people. Not to say that you folks are not trying, but the │ │ bugs in the 3001 patch SHOULD have been caught by the folks │ │ in QC. If Clarion is relying upon Alpha Testers to QC the │ │ program, then they might want to think about replacing the │ │ Alpha Testers. │ │ Can you put a word in to Bruce and say that it is time to │ │ quit ADDING new features and time to start getting the │ │ program out the door? Since an AD was placed in one of the │ │ Programmers Journals (I too read the ad), Clarion is either │ │ going to have to Produce CDD or give the people that work │ │ the Order Desks a raise. And if CDD goes out like it is │ │ now, we are going to have to buy you a coffen LONG before │ │ you should be placed in one. │ │ It seems that one of the places Clarion is lacking is │ │ Quality Control. A programmer involved in the development │ │ can't be a QC person. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0587 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/16/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: John Crenshaw 75110,531 │ │ Paul, │ │ I agree, with you as far as data conversions having the │ │ source code is a much better solution. However I have had │ │ several problems with clients where source code would not │ │ have fixed the problem. Freqently I have clients who for │ │ what ever reason, have had the file server crash and endup │ │ damaging a datafile. The program would return an error │ │ about an invalid data file, CSRT would barf out, but cfil │ │ would repair the file. The question is in a case such as a │ │ 'damaged file' what should we do to attempt to repair that │ │ file, or was I really just lucky that CFIL worked. │ │ John │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0604 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/17/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Goldberg Mark 75250,2551 │ │ Hello Everyone, │ │ Following is a list of suggestions compiled at our last │ │ user group meeting. │ │ 1) Generator:Forumala:Formula Classes: Force UPR on data │ │ entry (otherwise template doesn't work) │ │ 2) Add MSG to pulldowns │ │ (it was felt that people would simulate pulldowns as │ │ in C21 to accomplish MSG's) │ │ 3) Add support for printing graphic images and loaded │ │ symbols (my appologies if we overlooked this support) │ │ 4) Documenation: │ │ a) Add a single index for all books │ │ b) need better examples, more complete examples that can │ │ be key'd in and tested │ │ c) include documenation as a file so that it can be │ │ searched d) Include a sample app that highlights different │ │ concepts e) Include a sample app that uses every one of the │ │ template procedures │ │ 5) Generator: Have simple checks performed as doing │ │ programming ex: check if quotes should be there or not │ │ (help label must be in quotes, initial values are not │ │ in quotes..) │ │ And a Question: │ │ 1) When displaying an image, what graphics mode are we put │ │ into ? Can we control the mode, (1024x768,1280x1024 ...) │ │ -- Mark Goldberg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0645 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/23/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Jeff Moyers 70254,2434 │ │ Could we please have the ability to assign the result of a │ │ conditional directly to an Integer type variable (BYTE, │ │ SHORT, or LONG)? For example, it is much easier to write │ │ (and to read, IMHO) : │ │ HOT = (TEMPERATURE <> COLD) then it is to write │ │ IF (TEMPERATURE <> COLD) │ │ HOT = TRUE │ │ ELSE │ │ HOT = FALSE │ │ . │ │ Every reasonable language I can think of allows this │ │ construct; C, Pascal, even lowly BASIC, to name a few. I │ │ cringe every time I have to write one of those five line │ │ assignments, when I know it COULD be said in just one line. │ │ Please, please, please???? Thanks!! │ │ Jeff │ │ There are 2 Replies. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0647 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/23/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ In 2.1 when a file/field attribute changed it was passed on │ │ to the forms and tables in the apps. In 3.0 the dictionary │ │ is just used as a snap shot at the time the field is placed │ │ on the form. After it is placed on the form it can only be │ │ changed if it is deleted/replaced or changed by hand. This │ │ is no good. It would be best to use the dictionary as │ │ a one stop shop for all attributes. I guess it would │ │ update the attributes during the template processing. │ │ When a app is in the appgen the dictionary it uses is │ │ locked and cannot be edited. This is not good. As far as I │ │ can tell it is only used for reference when placing fields │ │ on the screens or for key/file info. It would be better if │ │ it would open read only so it can be changed. │ │ I know we are only using a pre-release copy however, it │ │ would be nice if all screens can be exited with the same │ │ keys. For example, to exit the file screen in a table it │ │ takes an alt-x then an alt-o to get out of the procedure │ │ properties screen. It should all be alt-o. │ │ I sent an earlier message stating that you could not relate │ │ more than one file to another file. (i.e. file A to file B │ │ once) Richard called me and told me why this was done. I │ │ can however think of many reasons why I would want to │ │ relate two files more than once. │ │ Regards, │ │ Fred Schmitthammer │ │ Professional Practice Systems, INC. │ │ (310) 804-7674 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0684 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/29/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Nik Johnson 70733,2247 │ │ 1. It turns out that one symptom I had attributed to a │ │ fried .APP is really due to a corrupted editor options │ │ file. If you erase \clarion3\edit.opt the system returns to │ │ "normal". I'm not sure what caused the options │ │ file to be corrupted. │ │ 2. When updating a project file redirection entry, if you │ │ press "insert" to be able to add a path, the system │ │ completes the field and processes an "insert" for a new │ │ record. That probably wasn't what the designer had in │ │ mind. │ │ And a couple of questions: │ │ 1. If you follow the directions in the manual for creating │ │ a .LIB from generated Clarion code, it includes │ │ everything from Clarion's libraries too. This not only │ │ gives you a 900k library for one small procedure, it also │ │ causes duplicate symbol problems when you go to use the │ │ library. │ │ 2. The directions for creating a DLL work better. But I │ │ haven't a clue as how to use a DLL in another APP. Am I │ │ missing a page, or are you? │ │ 3. There is an #IMPORT command in the template which is │ │ (as near as I can tell) not documented anywhere. Either │ │ because of #IMPORT or in spite of it, an INCLUDE of │ │ BROWSE.INC appears in the generated code. The context of │ │ the #IMPORT statement gives no clue to how BROWSE.LIB, │ │ BROWSE.PR or BROWSE.INC will be used. I hope this is │ │ not the leading edge of the "magic" code with which │ │ Designer drove many of us bananas. │ │ If I remember the promise correctly, the logic is in │ │ the template, not in the generator. │ │ And an observation: │ │ 1. We're betting (with you) that a reasonably bug-free │ │ CDD3 will make a big impact on the marketplace. Your │ │ approach to improving productivity strikes me as a great │ │ deal more promising than some of the alternatives out │ │ there. (If object orientation is half of what it's cracked │ │ up to b how come so many who are touting it seem to be so │ │ far behind schedule.) │ │ But productivity is a total thing ... it's what you can │ │ get done in a day, a week, or a month, counting all of │ │ the factors. You're tempting people to put a great deal │ │ of effort into an APP file, and to date it's not clear │ │ that this is a safe repository. Worse, there's enough │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1059 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/19/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Bradley R. Olson 72103,136 │ │ Okay, I know you're still working through 3.0, and I │ │ applaud it. But I wish...O how I wish...that you had a │ │ Clarion for UNIX too. Think of it, coming full circle: │ │ Clarion was an attempt to put better-than-mainframe tools │ │ on a PC, now you could put them back on the mainframe, │ │ except this time the mainframe is a grown-up 486 or better │ │ PC. With Novell's new acquirement, this could be exciting │ │ for you. │ │ Of course, I'm sure people are already badgering you for a │ │ Clarion for Windows too. I forsee many sleepless nights │ │ ahead... │ │ R&D: Sometime after CDDOS2... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1101 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/27/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 │ │ Within a SCREEN in the AppGen one can modify the default │ │ colors from the Pull Down Menu. │ │ However, any fields that have been changed previously can't │ │ be modified. They all have to be modified manually (which │ │ is a disaster: Prompts AND fields). Of course something can │ │ be done with the Style statements and files, but this │ │ influences ALL colors in that source module. │ │ Wouldn't it be handy to have a menu selection RESET ALL │ │ COLORS TO DEFAULT? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1274 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 5/18/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ wants screen blanker │ │ R&D: Try "After Dark". │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1477 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/11/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in the system information window a user wanted to be able │ │ to print out this information. maye a print pushbutton? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1860 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: TYRONE F. BAKER 72124,1054 │ │ In place of the formula generator I would suggest the │ │ following helps be made available inside each of the source │ │ hook windows. A popup data list like the Files Button. A │ │ popup list of clarion funcion & procedure prototypes with │ │ short explanations. A popup list of color style codes and a │ │ popup list of keycodes. │ │ I would also like to see a couple extra attributes. │ │ A string field attribute possibly called WIPE that would │ │ cause a field to clear like the numeric types do with the │ │ INS attribute if the first keystroke on that field was a │ │ visible character. A numeric attribute possibly called │ │ CURRENCY that would insert from the far right and │ │ push left like mostbusiness calculators do. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1937 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 7/20/93 │ │ Reported In : RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ if a duplicate bug report is entered, is it possible to put │ │ in the memo which number it is a duplicate of so that we │ │ may track to see if it has been corrected │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1952 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It would be nice to be able to draw thin borders using the │ │ CTRL-T options! │ │ R&D: Cannot happen. I have no way of "unloading" borders │ │ (similar to the reason that symbols are unloaded at the │ │ beginning of screen formatter) and no way to determine │ │ whichcharacters are remapped. It would be nice, though. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2316 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/09/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 │ │ Please pass on to R&D that it would be nice to have the │ │ helpid's in the application generator to be longer. Perhaps │ │ 25 or 30 characters. Fred │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2524 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/04/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like us to take all text from his screens and │ │ throw it into a text file for him incase he wants to use │ │ this as the new form of help. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2525 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/04/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Kind of like the ship list, user desires that we create the │ │ ability to automatically save the fileswhich it would take │ │ to recreate this exe for purposes of a backup. │ │ A batch file was suggested at the time to the user. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2570 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/05/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: George Williams 70436,1643 MSG#:34671 │ │ clatmp=c:\ dosent work as a parameter when executing the │ │ program now. Seems as if the only way clatmp= works in the │ │ set command. A step backward? It used to work...sigh... │ │ Also, I know that I am nagging, but really, really, really │ │ need it to work from the .ini file...please? │ │ R&D:Unfortunately, this is a time consuming feature to │ │ implement, and yours is the only request. I suggest you │ │ make your appeal directly to a higher court (ie:BB) or │ │ consider using a .BAT file to start your program as we do. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2973 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 11/08/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the memory window has been changed to something new not │ │ referencing houses and lot sizes, this is good since that │ │ never meant anything to me, but the xms and ems memory │ │ available always says zero. Good chance that this is not │ │ true. │ │ R&D:Looked at this, w/out major changes the only info │ │ re:ems/xms available to library under new ovl/dll loader is │ │ direct access to EMM. Thus, because loader is using all │ │ or sometimes (under Vid) nearly all ExtMem, EMM reports 0. │ │ Same is true under extender, all memory, including disk is │ │ treated as "conventional" memory. Static model will give │ │ more meaningful values. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3070 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/16/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: david zaremba 70042,1446 MSG#:42624 │ │ Is there anyway to obtain the Btrieve layouts of the .APP │ │ and .DCT file for creating documentation of projects ? Can │ │ these be licensed or a non-disclosure statement signed ? │ │ The current methods for printing these files are pretty │ │ primitive and work intensive. If not, please forward a │ │ request for better project documentation tools to │ │ R&D. Thanks. │ │ David Zaremba │ │ 70042,1446 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3086 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 11/17/93 │ │ Reported In : 3006 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Need the ability to have choices as menu items as well as │ │ radio buttons. For example: Field -> Is A Dealer?:X No Yes │ │ takes less room on the screen than │ │ Is A Dealer ( ) No ( ) Yes │ │ R&D: This is a design decision for 3.0 - it will be up to │ │ Bruce to decide if he wants to add this after all. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3173 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 11/30/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ lemglue should get sent with the product in the future │ │ since it is needed with the comm lem │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3210 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 12/03/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark Rayburn 73062,2111 MSG#:45225 │ │ I would very much like to see the following enhancements to │ │ the Clarion 3006 product. I would also liketo STAY OUT of │ │ the Apps Gen business forever! Thanks in advance for your │ │ consideration. │ │ Productivity Improvements │ │ ------------------------- │ │ 1) A tool of this type and technology should allow copying │ │ any program or data portion from one place to another. I │ │ should never have to go through a data entry excercise more │ │ than once (this is NOT a good use of anyones time). │ │ Therefore, I would like to: a) copy Local Data to Global │ │ Data & vice versa. b) copy portions of Data from one │ │ Application to another. c) copy Procedures from one │ │ Application to another. │ │ 2) It would be nice to drop "bookmarks" or "anchors" at │ │ various development points (max of 6? 1?). That way, a key │ │ sequence or command line argument could take me to that │ │ exact location. The ShiftF4 feature is nice, but with the │ │ above change, I could save: <down arrow>, <down arrow>, │ │ <Enter>,AltU,<down arrow>,Enter,<page Down>, <page Down>, │ │ etc. Software tools should remove the mundane. Along these │ │ same lines, type-ahead is inconsistant in CDD. You can │ │ *usually* type-ahead until you have to press an Enter key, │ │ but not always. I hate waiting on screens. I've been to the │ │ screen dozens of times, I know how many down arrows, Alt │ │ whatevers, etc I need. Why must I wait for the thrill of │ │ SEEING the screen again before making my selection, again? │ │ Ican't even go back to the application I was just working on │ │ without waiting for the CDD logo screen to appear (I really │ │ do like the screen, but hey, must I see it before I can │ │ seleShiftF4?). So could you: a) Give the CDD programmer a │ │ way to go back to a SPECIFIC spot? (Specific like │ │ Application, Procedure, Source point, & line) b) Allow │ │ type-ahead always. c) Give the CDD programmer a way to "go │ │ to" the main Procedure Worksheet taking all the "good" │ │ (Ok/Exit/Esc-X-Enter/AltF-X- Enter) responses without the │ │ CUA finger gymnastics. At least this path generally takes │ │ type-ahead (bless you). │ │ Feature Enhancements │ │ -------------------- │ │ 3) I have used other packages, and I think the List Boxes │ │ inClarion are the easiest and the most flexible for │ │ scrolling information. However, when I just need a box for a │ │ Lookup, things are not so easy (from the Application User │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3555 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like to suggest that the changes.doc file be │ │ renamed to chang06.doc, change07.doc so the old changes.doc │ │ file does not get overidden with the new one. │ │ QA&E: Can't you people make up your MINDS???? I suppose │ │ you want your cake and Edith too! │ │ We have not done this in the past and I doubt it will │ │ happen in the future. │ │ We suggest that the user backup ALL volitile files prior to │ │ Install/Patch! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3919 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/19/94 │ │ Reported In : 30071 RevisedDate : 2/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Request by user: It would be helpful if CDD could │ │ incorporate its own QBE. It is just a suggestion. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4038 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 3/04/94 │ │ Reported In : 30071 RevisedDate : 3/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When the cursor is placed on a memo field at the first │ │ column of the existing first line and you press <enter> in │ │ insert mode, it will not move the current line down... in │ │ other words, there is no way to insert a line before the │ │ first line of a memo field unless you press the space bar │ │ to move the line down -- reported by Proj 2878 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4153 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/21/94 │ │ Reported In : 30071 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Dan Luther 71121,417 MSG#:60647 │ │ I would like to see the following additions to Clarion: │ │ A way to view the database dictionary within the Clarion │ │ editor, cut and paste would be nice. Perhaps a way similar │ │ to the "Choose Variables" in the screen layout box. That │ │ waythe database layout, local and global variables would │ │ alwaysbe on hand for reference. │ │ A nice way to print out the local and global │ │ variables when defining them. │ │ Better support for "OVER" and "EXTERNAL" │ │ attributes in the Data definitions screen. Support in VID │ │ for variables not declared within the Data screen (i.e. │ │ in an EMBED section). The end-user report writer (that │ │ was promised long ago) │ │ Perhaps external editor support? I use Multi-Edit 7.0 │ │ and have written some support macros for Clarion; these │ │ are nice; A command-line Clarion compiler. A full set of │ │ Clarion commands, │ │ procedures, and goodies in the on-line help. │ │ Slowly but surely, I'm │ │ being "weaned" from the application designer; It serves its │ │ purpose well, but I just can't think of anything │ │ marketable that can be completely written in the designer │ │ just using templates. │ │ I'd like to add the following: │ │ SQL support. Think about this for a minute, read the first │ │ page any issue of PC-WEEK or whatever weekly computer │ │ newspaper you get, and think of the │ │ potential profit from a(n) SQL driver. │ │ The Paradox 4 driver (please...) │ │ Support for user-defined data structures. Although this │ │ would require some kind of API, it would simplify a great │ │ deal. I started some time ago on a field input routine that │ │ would have a rich input mask. Although I never completed │ │ it(writing it in Clarion was... well, an exercise in │ │ frustration) I plan on implementing it as a C routine as │ │ soon as I have some time. │ │ In addition to the support for "OVER" and "EXTERNAL" │ │ attributes in data screens. I'd like to see support for │ │ "LIKE", and better handling/copying │ │ of "GROUP"s. Here's the scenario: │ │ A file called "CUSTOMERS" has 2 phone number fields: │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4209 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 3/24/94 │ │ Reported In : 30072 RevisedDate : 3/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user - run time halt for access to unopened │ │ files │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4508 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : MD DateReported : 4/22/94 │ │ Reported In : RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ f │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Problem? Maybe... │ │ In Print Filter, if there is something in the text field │ │ that is invalid (but you haven't completed the field yet), │ │ then click on the "Use Expression Generator" checkbox, it │ │ won't let you out of the text field until you clear out the │ │ invalid stuff. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4663 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 5/13/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ template language-- user suggestion : to have a global │ │ symbol containing the names of all the procedures │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4744 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 5/31/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user suggestion -- default MSG attribute for fields in │ │ dictionary │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4763 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 6/03/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User request: Could you implement a monochrome styles file? │ │ This would be used when the monitor is b/w but the card is │ │ color. For example, IBM Think Pads │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4862 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 6/21/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User would like the LASER.CTL and PRINTER.CTL to be │ │ updatedto include various printers. For example, │ │ HPIVp,HP3si. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5271 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 8/17/94 │ │ Reported In : RevisedDate : 8/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ general suggestions │ │ Section │ │ Miscellaneous │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Suggestions from Ed Cook: │ │ 1. Temporary code generation file - suggests changing name │ │ of file from 'code.$$$' to 'nameofapp.$$$' to facilitate │ │ generating multiple app modules simultaneously. │ │ 2. Screen styles files - have a style file associated with │ │ a screen instead of a global file. │ │ 3. Access files/field list within editor on embedded source │ │ points │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2802 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 10/27/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ MultiPage Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ on the multi page template if you click on the OK button │ │ and there is a required field on a pageof, you will be │ │ brought over to the correct pageof procedure but the │ │ message at the top of the screen says 'PAGE 1 of 2' when │ │ you are really on page 2. when you are on page 2 and click │ │ on LAST PAGE button is saves the record and brings you back │ │ to the browse that originally called it │ │ R&D: Problem 1: Display of Page Corrected │ │ Problem 2: Please change to suggestion (Ability to │ │ stop Non-Stop select on MultiPage). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2958 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/07/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Operating System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Harrison A. Curtis 72730,1402 MSG#:40594 │ │ Changing from APPEND to PATH fixed the missing TXT files │ │ when requesting HELP. Evidently, CLARION isn't processing │ │ the APPEND along with the PATH when searching for the │ │ CLARION directory. │ │ Problem: Clarion doesn't recognize or search any APPENDed │ │ paths. │ │ R&D:3.0 does not make direct use of APPEND. This was a │ │ feature addes to DOS2.1 to enable programs written for │ │ DOS1.x and CPM to run under a heirarchical directory file │ │ system. APPEND, thus, can be used to trick programs into │ │ thinking a file, which is in a remote directory, is in the │ │ current directory. Unless there is a compelling reason why │ │ this featur should be added, no changes will be affected. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4790 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/09/94 │ │ Reported In : 3008 RevisedDate : 6/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Operating System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Greg Newberry 71022,2300 MSG#:73707 │ │ Thanks for the comment on OS/2. I have put both of the │ │ settings to ZERO and it doesn't seem to affect the CPU │ │ usage. │ │ It would be nice if you could talk the │ │ programmers into giving up time slices in the polling loops │ │ for all Clarion Products so that they worked better under │ │ Windows or OS/2. If I can do it in a BASIC app, anyone │ │ should be able to │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3282 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 12/13/93 │ │ Reported In : 3007 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Page of Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user -- on pageof procedures the user would │ │ like OK and CANCEL buttons (to act the same as the │ │ multipage procedure) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3989 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TM DateReported : 2/28/94 │ │ Reported In : 3007? RevisedDate : 2/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │0 │ │ Section │ │ PenDOS Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Mike, │ │ When using the up-carat gesture on a pen field, it would be │ │ nice to have the field's prompt displayed so the operator │ │ knows what needs to be entered. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4612 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/04/94 │ │ Reported In : 3008 RevisedDate : 5/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ PenDOS Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Silver 74145,1546 MSG#:69122 │ │ Greg, I understand what you are saying about data │ │ compression in the binary memo field but dont really │ │ understand. There is an example in the clairon users manual │ │ where I can import the information of a pcx file into a │ │ memo field. I did this and it works. Then I used │ │ essentially the same formula and exported the data from the │ │ memo field to a file which was pretty much the same as the │ │ pcx. At least it looked like the pcx file only slightly │ │ shorter. Therefore at least for this technique │ │ there was no data compression. I tried the same for a memo │ │ created with pendos and gui libraries. The handwriting │ │ displays fine but I cant export it to the other file type. │ │ Now I understand about proprietary techniques but │ │ there must be something that I can do with data besides │ │ just display it on the screen. It should be at least │ │ printable or exportable. What I intended to do with it was │ │ fax it to a fax machine and the only thing preventing that │ │ at this point is getting it into a form which will permit │ │ faxible output. So how about providing a library to │ │ decompress this memo? David Silver │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4759 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/02/94 │ │ Reported In : 3008 RevisedDate : 6/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ PenDOS Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 74442 S8/3.0 Support │ │ 01-Jun-94 18:06:55 │ │ Sb: #74395-Pen Binary Type │ │ Fm: Fred Schmitthammer 76436,3511 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ Please consider this a request for signature capture / │ │ recognition for the │ │ PenDos libraries in the future. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4846 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/16/94 │ │ Reported In : 3008 RevisedDate : 6/16/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ PenDOS Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 15-Jun-94 09:27:23 │ │ Sb: #76405-Pen Lib Keyboard │ │ Fm: Fred Schmitthammer 76436,3511 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ Perhaps the developer can change the PenDos library to turn │ │ on pen entry on a screen by screen basis. For example, if I │ │ want a screen to allow Pen entry I would put LoadPen() in │ │ the setup for the screen. Then when exiting the screen I │ │ would use UnloadPen(). This would allow me to add Pen │ │ support to a standard application. │ │ Can you ask him if this is possible ? │ │ Regards, │ │ Fred │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0185 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/01/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When generating source code, show path of .CLA's being │ │ generated in Project Window. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0670 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/26/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Patrick Donnelly 73730,1215 │ │ It would be nice if there was an option to stop │ │ compiling after the main module if it contains any errors │ │ (or at least have a CTRL-BREAK just stop the compile and │ │ not blow you back to DOS). It's usually useless to compile │ │ a whole slew of modules if the main one has a error. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1237 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: │ │ This user has > 100 clarion applications for use in their │ │ corporation. The files are on the network and he wants to │ │ use DLL's. │ │ PROBLEM: these programs may all have been made over a │ │ several year period. Since he will upgrade his version of │ │ CDD throughout that time and have different DDVCLA.DLL's he │ │ would like to be able to have different versions of this │ │ file for whichever version that he has compiled the .EXE in │ │ originally. │ │ -more- │ │ Example: │ │ Accounts.EXE was compiled Dynalink in version 3002. │ │ Reports.EXE was compiled a year later in version 3009 │ │ and copied onto the network in the same directory as │ │ Accounts.EXE. The DDVCLA.DLL in this directory can not │ │ be from both 3002 and 3009. So the user would like some │ │ way to link 3002CLA.DLL and 3009CLA.DLL instead. │ │ R&D: The 3009 version of DDVCLA should be backwards │ │ compatible, so he should not need 3002. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1253 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Project system (Directory Pushbutton) │ │ When viewing the .RED file it may be a Local or a System │ │ Redirection file. │ │ Please display the full path and name of the current .RED │ │ file on the screen somewhere. │ │ GDF - Sounds reasonable. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1256 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 'Called From This DLL Only' Checkbox. │ │ Since this option makes variables in this module public or │ │ private could we use the words 'public' or 'private' in the │ │ text to make it more understandable to programmers. │ │ GDF: │ │ Then, in the 'Advanced Module Settings' listbox, scroll the │ │ word 'Public' next to those modules which have the checkbox │ │ turned off? This way you will be able to tell which │ │ modules are public without the extra keystrokes. Is there │ │ room in the listbox for this? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1329 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/24/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: K.Fleming(Reliable Net.) 72230,535 │ │ When a Make is complete, and you select the "Ship List" │ │ button, that's a really handy list...what'd be even handier │ │ than the "Print" button on the Distribution Files window │ │ would be a "Copy To..." button that asked for a destination │ │ path and then copied all of the listed files there. │ │ Kevin Fleming, Reliable Networx, Phoenix, AZ │ │ There is 1 Reply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1334 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 5/25/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests that after a compile where errors are found │ │ that the highlighted button should be the Edit Errors │ │ button. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1383 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 5/28/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggest that we include the btrieve tsr in the ship │ │ list if they are using the btrieve file driver │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1665 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Are there any plans to change the CDD project system so it │ │ does not change a project file that it does not understand ? │ │ I have configured my CDD/Topspeed enviornment so I can │ │ compile any Topspeed language I have under my Clarion │ │ enviornment. However, the darn CDD project system always │ │ changes my project files ! If I had my wish, I would │ │ want the power of the Topspeed project system with the │ │ front end of the CDD project system. │ │ R&D: The Clarion Project System is only a Subset of the │ │ TopSpeed Project system. At present there are some things │ │ that you will not be able to accomplish in the Clarion │ │ Project System that can be done w/ the TopSpeed Project │ │ System. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2288 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 9/02/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Target filename: It would be nice to provide a path here. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2689 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 10/18/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ changing a lib name from the module worksheet adds this new │ │ name to project system but does not remove the old one. │ │ R & D : If the lib is placed in the project through the │ │ templates or generator, it must be changed there. │ │ Good suggestion for better error trapping in a │ │ future release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2909 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : SF DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Clarion project system is throwing a lot of unnecessary │ │ and sometimes disadvantages lines into the project file. │ │ For example the following project file was created for a │ │ new protected mode application with debugging: │ │ #system auto exe │ │ #model extendll │ │ #pragma data(stack_size=>8192,threshold=>0) │ │ #pragma optimize(cpu=>86) │ │ #pragma debug(vid=>full) │ │ #pragma link_option(map=>on,case=>on) │ │ #compile TEST.CLA /define(GENERATED=>on) │ │ #compile TEST01.CLA /define(GENERATED=>on) │ │ #link TEST │ │ threshold=>0 I do not know what this will do. I hope the │ │ project system ignores it. │ │ cpu=>86 This causes worse code to be generated than │ │ necessary │ │ map=>on and case=>on These are the defaults so do not need │ │ to be in the project file. │ │ BC:"threshold" is used to avoid exhausting segment size, 0 │ │ is a dubious value, I'll have a look at that. "map and │ │ case" are not always defaulted correctly by tsprj.txt, │ │ especially when vid comes into play, explicit declaration │ │ does not hurt. cpu=>86, is probably an artifact from │ │ making the project in a real model, or having the switch in │ │ the default clarion.pr. It is overriden by tsprj so does │ │ not degenerate the code, although it might be more │ │ appropriate to reset it when extender is selected. Ok. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2937 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/05/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Fred Schmitthammer 76436,3511 MSG#:40445 │ │ I have a project file that is over 255 chars long. The CDD │ │ 3006 project system cuts the line off at 255 chars. Is │ │ there any workaround for this? If not I would like to │ │ report it as a bug. │ │ R&D:There is no workaround for allowing lines of this │ │ length in the project system. But I suspect the reason the │ │ line is so long is because you have maxed out the automatic │ │ export feature for creating DLL libraries. To work around │ │ this I recomend that you freeze your export file and manage │ │ it manually. To do this; create an "Overlay Control File" │ │ module in your project called "projname".EXP, the file │ │ already exists in your working directory. The project │ │ system will no longer use the "Called From This DLL Only" │ │ check box to determine your exported items, you will have │ │ to manage these in the .EXP file using the text editor. │ │ Notice that the fact that you are exporting items from so │ │ many modules is highly unusual and you may want to consider │ │ "privatizing" those modules which you will not be calling │ │ directly from another DLL or EXE. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3492 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 1/11/94 │ │ Reported In : RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Add Ons section of the Make system, IF one addon has │ │ an error we do not get any of the ones that were sucessful. │ │ This slows the testing of fixes down. │ │ It would be nice that if an Add On was successful that it │ │ was moved to it's proper location. Then allow the next one │ │ to be made. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3554 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Project System │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like the ship list to include the styles file if │ │ the app will be using one │ │ QA&E: The ship list is getting its infomation from the │ │ PROJECT System not the CLAs. It would be ridiculous to │ │ expect it to read thru ALL of your CLAs to find everything │ │ you may or may not need to ship. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3023 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Pulldown Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from end user - wants to be able to define a │ │ hotkey procedure on a pulldown. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2951 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/05/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Pulldown Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:40206 │ │ Greg, │ │ Why don't pulldowns use the thin borders when 'half' is │ │ selected for the pulldown frame? │ │ Regards, │ │ Randy Rogers │ │ Keystone Computer Resources │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1406 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/31/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report - Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ No error is being issued but if I have a report from the │ │ app gen that is labels two accross and I am suppressing │ │ when blank for a line and only one of the labels needs to │ │ suppress and not the other the suppressing does not happen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1933 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 7/20/93 │ │ Reported In : 3005A RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Report - Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In 2.1 you were allowed to have multiple reports open at │ │ the same time. For example reporta device = Lpt1 and │ │ reportb device = lpt2 │ │ The only problem w/ this was if whilst printing on lpt2 │ │ something happened the reportb would be intermixed w/ │ │ reporta. │ │ Is it a problem??? Or was it a feature of 2.x that has │ │ been FIXED in 3.0. There should be some type of warning or │ │ something if this is the case. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2349 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 9/20/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report - Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User is requesting that when we send out a report , we │ │ don'tsend the trailing spaces, just the CRLF like the ascii │ │ file driver does. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4730 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 5/25/94 │ │ Reported In : 3008 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report - Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User wants ability to strip the CR/LF off when printing a │ │ control string. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4959 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 7/19/94 │ │ Reported In : 3009 RevisedDate : 7/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Hidden attribute in DCT isn't used by RW. │ │ Section │ │ Report Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the dictionary editor there is a check box for Hidden │ │ which is supposed to restrict viewing/editting of data │ │ usingthe Database Manager. I'm not talking about the HIDE │ │ field attribute. │ │ In the Database Manager fields which have this │ │ "Hidden" checked do not show! │ │ This in itself provides field level restriction │ │ from outside (non-app) utilities. Seems like it │ │ should carry-overto the report writer. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5209 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 8/05/94 │ │ Reported In : 3009 RevisedDate : 8/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Suggestion for Reports │ │ Section │ │ Report Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggestion: │ │ Provide an additional Band Property that is the same as │ │ ALONE for the Title Page but does not formfeed and does not │ │ place a page header above the Title Page. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5338 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 9/01/94 │ │ Reported In : 3009 RevisedDate : 9/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Request for a Left Margin setting for reports │ │ Section │ │ Report Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: │ │ Would like to see a left margin setting for a report the │ │ same way the pagelength is set. │ │ ------------------------Work Arounds-------------------- │ │ At the beginning of the report, send the ESC │ │ sequence to setthe left margin. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3234 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 12/07/93 │ │ Reported In : 3006 RevisedDate : 7/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Report Formatter Editor and Generator. user would like to │ │ beable to see the band lables in the formatter without │ │ going into the band properties screen. │ │ I changed this status to a problem as it is a problem. For │ │ one it is removing funtionality from 2.1 to 3.0. Anyone │ │ designing an extensive report will fight with this problem. │ │ Debby │ │ From QA&E: Look at the status line in the formatter, it │ │ displays what BAND the cursor is in currently. This may be │ │ addressed at a later date. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4164 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 3/21/94 │ │ Reported In : 30072 RevisedDate : 8/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Overprint Next w/ Control field in Editor/Formatter │ │ Section │ │ Report Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when placing a control field on the report, you do not │ │ have the option for overprint next from the control field │ │ screen │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4249 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 7002 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The option for overprint next is in a different place for │ │ the editor vs the Generator. Could we make it consistant? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4250 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 3/30/94 │ │ Reported In : 30072 RevisedDate : 3/30/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ the entries for USE & LABEL are in reverse order for TEXT │ │ fields when compared to CONTROL and DATA fields. │ │ Could we be more consistant? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0849 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 8/10/93 │ │ Reported In : 3000 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Tools pulldown, Color Chart should be dimmed like it is │ │ when you select Draw Track from the Edit pulldown. Won't │ │ hurt to have it active but just thought I'd mention it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2728 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 10/20/93 │ │ Reported In : 3005 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Not really this category but it will do. │ │ When you create a new detail section which consists of a │ │ blank line with no fields or text it will not print even if │ │ fixed attribute or seperate attib. │ │ R & D This is currently the limitation of reports. If the │ │ Fixed attributed is on the detail section that you want to │ │ be separated from all is fine. │ │ Okay I accept the answer, but you can't change the status │ │ tonot a bug. It is a bug. We just can't fix it. It needs to │ │ bedocumented in corrects.doc or changes.doc, that you must │ │ add a dummy field to print a blank line. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3317 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 12/15/93 │ │ Reported In : 3007 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user should have the ability to not select a printer for │ │ PRINTER() on a report. If they use a CONTROL with a USE, │ │ this will not work when a printer is selected. For example │ │ CONTROL(10),USE(prn:boldon) where boldon contains the │ │ printer control seq. │ │ see soft_coded_rpt procedure and take the printer attribute │ │ out. without PRINTER() the control codes wil work │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4089 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DB DateReported : 3/10/94 │ │ Reported In : 3007 RevisedDate : 7/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When I place a field on a report (FROM THE REPORT │ │ FORMATTER IN A EMBEDDED SOURCE WINDOW), and I click on the │ │ down arrow next to the "Use:" field, I can only choose from │ │ data that was defined in the dictionary. I cannot choose │ │ from Global or Local data. The same goes for creating a │ │ screen in embedded source.. │ │ R & D - Do not understand. You can choose local/Global data │ │ from the APPGEN │ │ Tech - Please re-read slowwwwer. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2212 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 8/25/93 │ │ Reported In : 3005 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about a report with no body option / check box so that │ │ one may print a summary only report. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2370 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 9/23/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants to have a formfeed send if the user escapes from │ │ a report. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2831 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 10/30/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user - when group footer is reached a │ │ previous() is done to go back to the last record in the │ │ group, formulas are calculated before the previous() and │ │ should be done after the previous(). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2964 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/07/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Michael Dilday 70274,3125 MSG#:40903 │ │ It would be nice if you allowed reports to be sorted by │ │ fields from multiple files. Similar to Queries found in │ │ other database applications. │ │ A way of doing this would be to create a temporary │ │ file using Formula's. You could use the class field with │ │ "Sort1", "Sort2", etc. Maybe limit to 10. │ │ Mike Dilday -- TCUG │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3110 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 11/19/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ wants a formula class for the grand totals section of a │ │ report │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3695 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 2/04/94 │ │ Reported In : 3007 RevisedDate : 2/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion: allow the user an option to choose whether the │ │ title page should be numbered as page 1. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4384 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 4/14/94 │ │ Reported In : 3008 RevisedDate : 7/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Actuall the Clarion Screen in Clairon.app for the Report │ │ Template..... │ │ #: 65749 S8/3.0 Support │ │ 12-Apr-94 04:19:52 │ │ Sb: _Report suggestion │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman - Clarion 72662,475 │ │ Hi Debby │ │ Minor suggestion (3008) │ │ The default SCREEN for the report template in CLARION.APP │ │ has its top border created in half height block characters. │ │ This causes an unexpected & aesthetically unpleasing │ │ effectwhen you run with LOADBORDERS. │ │ I suggest that some other design is used - perhaps │ │ full height block characters with a heading inside it. │ │ Rob from Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4811 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : SA DateReported : 6/11/94 │ │ Reported In : 3009 RevisedDate : 6/16/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Report Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Reports w/ many formulas seem to take a long time to │ │ generate. Is there any way to make them faster???? │ │ RM - Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1174 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/11/93 │ │ Reported In : 3003 RevisedDate : 7/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ RWRUN │ │ Section │ │ ReportWriter Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: E.J. Tejera 71066,1361 │ │ RRUN was one of the best tools to "sell RW". After using │ │ the predefined reports, my clients almost invariably would │ │ order a RW. The RW runtime module was a very practical │ │ feature of v2.1. Please let R&D and marketing know. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1182 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/11/93 │ │ Reported In : 3003 RevisedDate : 7/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Report Writer as a DLL │ │ Section │ │ ReportWriter Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: E.J. Tejera 71066,1361 │ │ A really good idea would be to make the Report Writer │ │ available as a DLL! It could then be incorporated │ │ seamlessly into CDD applications. Since there are license │ │ implications here, a dll version of the RW could be made │ │ available as a separate product. Eric. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4513 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : MD DateReported : 4/22/94 │ │ Reported In : RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ ReportWriter Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Would be nice to show which line number you are on when │ │ viewing the report to the screen so that you have a better │ │ idea what it will look like on paper. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5215 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 8/08/94 │ │ Reported In : 3001 RevisedDate : 8/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Expand runtime range entry │ │ Section │ │ ReportWriter Formatter │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Please look into expanding the runtime range entry to │ │ include any field. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4984 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 4/21/94 │ │ Reported In : RevisedDate : 4/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ request came from Beta tester to add another command line │ │ parameter. The parameter would accept the filespec for the │ │ DCT file to override what is currently in the RWF. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5008 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/05/94 │ │ Reported In : b2 RevisedDate : 5/05/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about a hotkey to Run the report, now its three ket │ │ combos to run one. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5085 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/26/94 │ │ Reported In : 1 RevisedDate : 7/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │ Controls and Overprint │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is not possible to place a printer control without │ │ loosing a space. for example: │ │ HereIsALineThatShoudlBeBold,AndThenTurnIntoItalicsLater │ │ If I want to change at the Comma above I must include an │ │ extra space. You can do it w/ several lines and OverPrint │ │ Next but it doesn't help w/ the WYSIWYG stuff. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5087 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : QA DateReported : 5/26/94 │ │ Reported In : 3.0 RevisedDate : 5/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Allow the control codes to be printed, the Names be printed │ │ or not used at all. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5096 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : J DateReported : 6/09/94 │ │ Reported In : RevisedDate : 6/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The Laser.ctl and Matrix.ctl could use some updating - most │ │ common user suggestion │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5119 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/27/94 │ │ Reported In : 3.0 RevisedDate : 6/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Runtime │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Got "Unable to Run Report" after completing Tutorial 2. │ │ Boy,that's really a helpful message! Couldn't you try a │ │ little harder to identify the general area where you found │ │ the roblem? I tried all the usual suspects, no success. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0122 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 1/25/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Tracking could have the colors stop at the actual track │ │ character rather than at the character 'cell'. Example │ │ more 'Windowishy'. The DOS shell is DOS 5 is implemented │ │ as the above statement without being a bitmapped Windows │ │ program. │ │ R&D: We don't have a way to my knowledge of supporting this │ │ with our current screen library (other than the │ │ special thin borders, which is coming). Don, you may want │ │ to show this to Mike. Not in the release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1022 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 4/12/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when placing a point field in 2.1 you could actually see │ │ the space that it would be occupying. in 3.0 you cannot │ │ see where the point field is located when placing it on │ │ the screen. │ │ 3.1 ISSUE │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1028 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 4/12/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when changing virtual and physical screen size, the screen │ │ generator tries to make the size closest to the 43/50 line │ │ mode. this has some problems │ │ Version 3.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1102 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 4/27/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In Editor (probably Generator also) Screen Formatter. │ │ Button Text DOES allow a variable name to be entered, │ │ however it does not allow dimensioned variables. │ │ ie: StringVar is allowed │ │ StringVar[1] gives an error for an Invalid Field │ │ Name │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1242 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: │ │ Allow the Screen Formatter in the Application Generator to │ │ display the graphical Check boxes and Radio buttons when │ │ the environment's "Use Graphical Fonts" is turned on. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1252 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Pushbutton addition to screen. │ │ When adding a pushbutton to the screen structure, you may │ │ now enter either text for the button or a variable name. │ │ So, the entry field is innitialized to: ' ' │ │ with the cursor in the middle of the two single quotes. │ │ The user must hit the insert key to keep from overtyping │ │ the last single quote. Can this field default to INS mode? │ │ The user doesn't need to worry about overtyping the quote - │ │ if the string starts with a quote and the end quote is │ │ overwritten, an ending quote will automatically be placed │ │ at the end. │ │ Colvin │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1259 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Suggestion: Ctrl-W │ │ User was WOW'd by the + and - key usage on Ctrl-W. Would │ │ like to see resizing for Listboxes, Text fields and Image │ │ fields work the same way in future releases. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2017 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/30/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 │ │ Right, that's what I want, but the "Reorder Fields" │ │ commandis in a drop down menu while looking at the FORM │ │ screen and the "Auto-Reorder" is buried in the screen field │ │ processing accessed via Control-F. I couldn't immediately │ │ find it. It would be nice to have the "Auto-Reorder" │ │ (and Auto-Populate) next to the "Reorder Fields" in the │ │ same drop down menu... │ │ OR │ │ perhaps a 'checkable' option that as you move │ │ fields around on the screen using Control-M, either the │ │ underlying accept order changes also (2.1 style) or the │ │ accept order is static and remains unchanged. │ │ i.e. [X] Accept Order Static (or │ │ Dynamic) │ │ Choosing Auto-Reorder or Reorder │ │ Fields would ignore how the option is set. What do you │ │ think? │ │ --David │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2079 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 8/10/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ You cannot paint an area of a screen BrightWhite on │ │ BrightWhite. │ │ R&D: This may be fixed in a future release - it will be a │ │ fundamental redesign of screener to do so. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2124 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/13/93 │ │ Reported In : 3004 RevisedDate : 2/03/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user: when doing a make and debug and │ │ enable debug settings has not been marked, automatically │ │ have it do a make as if it was marked │ │ R&D: You would drive yourself crazy having to recompile │ │ the entire program each time. This is not a good idea. │ │ Maybe we could pop up a warning before continuing so you │ │ could fix the settings before attempting the run │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2925 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Stephen Swope 71525,1225 MSG#:40345 │ │ If your designing a screen in an Embedded Data area and │ │ wantto use the same Styles colors that you have for the │ │ application you need to Specify that same styles file in │ │ the Options for that screen (CTRL-O). │ │ Suggestion: It would be nice if the embedded source │ │ screen formatter defaulted the styles file to the one │ │ specified in the Applications Properties Window. │ │ Greg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3481 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 1/06/94 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The code support multiple alrt attributes on a field but │ │ the formatters only support one or a range. Users have │ │ requested that we support multi attributes. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3553 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/20/94 │ │ Reported In : 3007 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Editor │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like the ability to comment a screen in the │ │ source code like 2.1 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0267 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/05/93 │ │ Reported In : 3001 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When adding a fixed row, typing on the listbox, control \ │ │ does not change case. │ │ I know that is being picky but I'm just mentioning it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1089 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 4/23/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ under control O there is row and column for a fixed screen. │ │ We are allowed to put a variable in for these two entry │ │ fields or a constant but you cannot put one of each. │ │ These entries are not mentioned in the f1 help either. │ │ Q & A : Now fixed at Topic Level. Help is there. │ │ Current compiler does not support this - will │ │ retain as a suggestion for future support. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1277 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/26/93 │ │ Reported In : 3003 RevisedDate : 8/09/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Request for "free form" formula generation │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ 4) I sure hope there's another way of entering a formula │ │ for a Computed Field. Traversing menus to do "CLIP ( │ │ Con:FirstName ) & ' ' & Con:LastName" is incredibly awkward │ │ and slow. I suspect you've implemented this way so changing │ │ a Dictionary field will change the field in the formula as │ │ well. Am I right? If so, it may be worth jumping through │ │ hoops to get a formula written. If not, better allow for │ │ freehand formula entry. │ │ 5) When moving/marking text or a field on the screen, the │ │ TAB key should tab across the sceen. It would make marking │ │ text/fields much faster. │ │ 6) Procedure Properties/Template. Templates should have a │ │ locator field so pressing "B" jumps to the Browse template. │ │ Makes template selection faster. Ditto for when selecting │ │ file & field names from the list. │ │ 7) When designing a screen, for some strange reason Ctrl-P │ │ will close the Desqview window and all the screen work │ │ since the last save will be lost. This happens only when │ │ designing the screen. Ctrl-P has no mysterious effect │ │ outside of the Screen template. Ctrl-T also exits the │ │ SCREEN and closes the Desqview window. Are there any │ │ special Desqview settings I should be aware of? I'm using │ │ the QEMM settings as outlined in the DOCS. │ │ 8) When designing a screen, the blinking cursor gets lost │ │ when it is on top of a solid (blue) track color. │ │ 9) When compiling the CONTACTS application, I get the error │ │ message "ERROR-Unknown Procedure" and it points to │ │ ShowPhones. Yet, ShowPhones is defined as "ShowPhones │ │ (BROWSE)" in the Procedure Worksheet, but code is not │ │ generated for it in CONTAC01.CLA. What gives? The same │ │ thing has happened to someone else here that was trying out │ │ the tutorial from scratch. │ │ 10) Because you're using a screen font, some of the track │ │ characters will produce the incorrect character where they │ │ intersect (double line meets single line). If you're short │ │ of screen characters, why not use a small square or a │ │ dot to mark where the lines intersect? That way you're │ │ using only 1 screen character. It's better than seeing a │ │ "]" on the screen. │ │ 11) I find it awkward in a List Box to move a field by │ │ deleting it, then make room for it by deleting characters. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1710 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 7/02/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggests that when a field is deleted from a screen │ │ that you be alerted in some way, if you have embedded │ │ source on that field. It's easy to wipe out alot of work. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1955 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ allow a pause field to be used from the app gen │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1960 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 7/21/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests that space between the radio button and the │ │ text for the option be shortened. Claims that a screen with │ │ many buttons causes problems. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1980 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/26/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 │ │ No big issues, but perhaps some ideas to make the product │ │ even better. In release 3.004 you included my suggestion of │ │ 'Default colors' menu option in the screen formatter. In my │ │ applications I use various screen defaults, which is e │ │ specially useful if various screens display on top of each │ │ other. The colorscheme says something about the function of │ │ the screen (validate browse, inputform, warning, etc). │ │ It would be great if there would be a 'Save to disk' and │ │ import facility of screen defaults, so that in designing the │ │ screen one can choose from various predefined colorschemes. │ │ Is the Browse engine going to be changed such that it │ │ will react to PAGEUP in the last page of records? │ │ The conditional switch for the COMPILE directive is │ │ located under the DEBUG pushbutton of the CHANGE PROGRAM │ │ MODULE. Does that make sense? It has more to do with the │ │ compile options then with debugging?!?! │ │ In the first prerelease of CDD 3 the debugger │ │ showed the amount of memory used (or still available, I │ │ don't remember). That was an interesting feature which for │ │ some reason was left out???? It would be helpfull if one can │ │ search a procedure in the debugger which is not in the │ │ present module. If in CLAVID, one has to go out, start up │ │ CDD and check the procedure tree to see in which │ │ module it is. │ │ When adding or changing embedded │ │ code in the editor, it would be helpfull to have a list of │ │ local and global variables available!!!! Even beter: one │ │ that allows pasting them in the text. │ │ There are 2 Replies. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2081 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/10/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 │ │ The IMAGE field documentation indicates that the SCREEN │ │ have the GRAPHICS attribute. Neither the Application edito r │ │ or the COMPILER is detecting the error condition of │ │ omitting the required GRAPHICS attribute! Everything │ │ compiles ok and works except no GIF/PCX is displayed... │ │ 1. The COMPILER should have flagged the IMAGE │ │ field line as being in error since the SCREEN did not have │ │ a GRAPHICS attribute. │ │ 2. Application editor should have complained │ │ about me adding an IMAGE field to a screen that wasn't │ │ 'checked' as being GRAPHIC. │ │ I spent a lot time looking for this │ │ one...<sigh> version 3004 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2182 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/20/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Jung 72466,1526 │ │ I've been using the reapply default colors option, however │ │ you have to go to each screen.... I'm looking for a "gobal" │ │ reapply default colors. │ │ --David │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2339 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 9/17/93 │ │ Reported In : 3005 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user: wants to be able to create local data │ │ from within the screen designer │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2360 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/21/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: GLENN HARDIN 72611,1410 │ │ The DIM fields (that's DIM not damn) could stand some he │ │ lp.On a FORM using Alt-L for Auto-populate when you select │ │ the DIM field it should automatically increment the │ │ incremental counter to select the next iteration of the DIM │ │ field. Currently it is always [01] level that pops up │ │ for population. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3804 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/14/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3. Consider reversing buttons on "Button Field Properties" │ │ dialog window to │ │ show WHEN SELECTED first, and WHEN CHOSEN second (i.e., │ │ reverse them). This │ │ more closely mirrors what happens when the application is │ │ running and how the │ │ developer is thinking when designing the application. │ │ DH - I second this suggestion │ │ R&D (Colvin): This was the way it was originally done - I │ │ was told to reverse it to the way it is now. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3806 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Is there a switch to cause screen formatter to use │ │ "pressure sensitive" │ │ scrolling during virtual screen designs? On my system, the │ │ normal auto-scroll │ │ feature makes the screen move so quickly I cannot control │ │ it very well. (If │ │ not, move this under suggestions). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4224 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 3/25/94 │ │ Reported In : 3007 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests ability to disable skip on @t3 and @t6 │ │ R&D: These picture tokens are not explicitly supported for │ │ entry of data. Although it appears that they will work for │ │ entry, not every case actually works correctly, such as │ │ entering 12:30 and trying to get it to be PM instead of AM. │ │ In addition, to support these tokens would imply support │ │ for similar date tokens, which would in turn be far more │ │ complicated to implement. │ │ The inadvertant ability to get fields with picture tokens │ │ of @T3 and @T6 into generator screener by using populate │ │ will be fixed. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4526 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/22/94 │ │ Reported In : 3008 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark Goldberg 75250,2551 MSG#:67610 │ │ Appgen:Screener:^F:Source (Completed) │ │ make a change │ │ alt-f-x (save the change) │ │ esc (to exit ^F screen) │ │ Notice that the change to the source has been saved! │ │ If would suggest that ESC exits the ^F as if Cancel were │ │ pressed, but if any changes have been made then an are you │ │ sure y/n screen appears, just like what happens when │ │ esc'ing from the procedure screen (where the #prompts are). │ │ Mark │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4803 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BF DateReported : 6/10/94 │ │ Reported In : 3009B RevisedDate : 6/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Formatter - Generator │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ From a student in a previous class...allow a step locator │ │ on the track window.(Type an '!', move straight to that │ │ character) │ │ R&D: Good idea, but it's unlikely this will make it into │ │ the list for 3.1 at this point. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0120 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DP DateReported : 1/25/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Caps attribute...how about setting a switch that would │ │ provide an opportunity to turn on our caps support from the │ │ existing switch. We could stick in a quick template mod │ │ with a check box added to the form dialog. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0212 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ PUTSTYLES should NOT be a third-party enhancement. You have │ │ included three-fourths of a color management system in C3; │ │ to leave out the last quarter is simply sloppy. │ │ Third party enhancements should address things that are not │ │ part of the core language, not fix things that are wrong │ │ with the base system. That is why LPM is such a kludge │ │ (although a tremendously useful one... no offense, Dave). │ │ YOU decided that color management would be part of the base │ │ language, so give us all the capabilities we need to make │ │ use of it. Without PUTSTYLES, color management is only │ │ available at design time, not at run time... unless we │ │ expect our users to redefine their colors every time they │ │ run the program. │ │ Don │ │ PS: I happen to think that report redirection (screen │ │ printer disk) should be part of the core... but you decided │ │ otherwise. However, if you were to add printer redirection, │ │ would you leave the file viewer out??? I think not. I │ │ think this is analogous to leaving out PUTSTYLES! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0245 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/03/93 │ │ Reported In : 3001 RevisedDate : 4/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Can we change the default color of a checkbox away from │ │ white on black ? Especially since the screen is black on │ │ white. Basically the checkbox default color is ugly. │ │ Personal opinion. │ │ The radio buttons are in the same condition. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0414 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/18/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a user requested the ability to find out if the monitor is │ │ monochrome or color. │ │ Q & A - Look at hardware information under cshell. │ │ he was referencing in his code? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0467 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/01/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Picture Token │ │ I was (very) disappointed to see the lack of support │ │ for entering a Time value using @T3 "HH:MMXM" and @T6 │ │ "HH:MM:SSXM". This has been a thorn in my side with 2.1 and │ │ I was hoping it would be fixed in 3.0 but IT HASN'T. Why │ │ can't you make life easier on programmers who have to input │ │ time values? │ │ It means I have to convert Time fields which are stored │ │ as 24:00 and display them in the 12:00 format and set an │ │ input field for the AM/PM indicator. Then when the field is │ │ changed, convert it from the 12:00xM format back to the │ │ 24:00 format. If I have 3 or 4 time fields on a form, it │ │ becomes a big programming hassle with conversion routines │ │ on the setup line and the edit line for each time field, │ │ plus constructing memory variables to hold the AM/PM │ │ indicators for each time field. The only support that │ │ Clarion 3.0/2.x has to enter 5:30PM is to force the user to │ │ enter it as 17:30 hours, and how many end users out there │ │ know military time? It's about time Clarion supported @T3 & │ │ @T6 for data entry! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0853 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 4/08/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Runtime. Mouse Control of the Repeat Structure's Point │ │ Bar. │ │ Suggestion for version 3.1(ish): │ │ Have Repeat structures work at runtime the same as │ │ listboxes at runtime in regards to the use of the │ │ Right Mouse Button Screen Scrolling │ │ when above or below the mouse scroll. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0985 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 4/12/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ when help appears shouldn't the pulldown be dimmed so that │ │ I cannot select the action bar while showing help │ │ ----------------------------------------------------------- │ │ Is this a Problem? If you think so, enter it as a │ │ suggestion to change the help/screen libraries. There is │ │ no good way in the templates to intercept the F1 key when │ │ you have a HelpID declared. │ │ Screens are not dimmed (DISABLE()'d) either. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1151 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/07/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Douglas E. Johnson 71543,1566 │ │ With all this fuss over CUA compliance, the thought comes │ │ to mind that being able to toggle CUA on/off in one's Apps │ │ might be a nice feature. Might R&D look into allowing the │ │ CUA screen attribute to be set by a variable? Something │ │ like SET CLACUA=ON might do the trick. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1258 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GF DateReported : 5/17/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ RADIO BUTTONS: Allow the Skip attribute for these fields. │ │ GDF - Handy when using a radio button field as a 'Hot │ │ Field' for a Browse procedure. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1324 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 5/21/93 │ │ Reported In : 3003 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants to be able to design a pushbutton that takes on │ │ more than one variable for the text. │ │ ex. -------- │ │ | var1 | │ │ | var2 | │ │ | var3 | │ │ | var4 | │ │ -------- │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1551 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/15/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants to be able to have graphical virtual screens, │ │ understands all the penalties this might cause but he │ │ thinks it is essential for his application. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1568 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 6/16/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants use to return the actual row and col size of an │ │ existing pcx image so that they can display it correctly │ │ instead of guessing the size. Dan Richards works at │ │ National Gallery and is creating a database of artwork │ │ images. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1659 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/28/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: D. Fast 71652,2205 │ │ It Says... There is NOT a Color Attribute... This DOES NOT │ │ say there cannot BE one... I Guess it may have seemed as │ │ though I Hadn't read the Docs ... But; the Question WAS │ │ directed to R & D...Implying a Request for a Language │ │ Enhancement where the PRESENT Aspects of the Pulldown is │ │ LACKING. │ │ May I Re-Iterate the Query... │ │ Can the Pulldown Object be IMPROVED to INCLUDE a COLOR() │ │ Attribute for ITEM()'s ? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1683 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 6/29/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from user: when using the cols() attribute for a │ │ list box, he would like the ability to make a stationary │ │ column, basically fix a column so when you move right to │ │ other columns this one will stay in place │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1788 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 7/12/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Couldn't we post some type of error if the style file is │ │ not found - instead of just having the colors be crazy. │ │ Maybe GETSTYLES should post an error - file not found │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1859 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry McClure 75170,1100 │ │ Just a thought. Allowing the user to move the windows ar │ │ ound the screen with the mouse is an excellent idea. But why │ │ not go one step further and keep the same window locations │ │ the next time the application is run or the window is │ │ opened? This would probably mean storing the procedure name │ │ and window location in a database file. The x,y screen │ │ coordinates are retrieved from the file during the procedure │ │ setup. When the procedure exits, if the window location is │ │ different from when the window was first opened, the │ │ new screen coordinates are saved to the file. It might make │ │ for a nice add-on, like the VGA Color Kit. Call it Window │ │ Achors. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1874 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 1/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David Bayliss 100025,1577 │ │ When in _continuous_ select mode (IE when doing form │ │ validation) a PRESS cannot be used to enter data into an │ │ entry form │ │ Therefore if you have a field with a lookup as a │ │ SELECT routine it will not work if invalid data gets into │ │ that field. (The lookup template returns results using │ │ PRESS) │ │ DAB │ │ Q&A: This is due to the use of PRESS in the templates. │ │ Until they are changed this is going to happen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2045 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 8/05/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a user wants as an upgrade to the system; a virtual window │ │ vs a virtual screen. Meaning that part of the screen is │ │ fixed while the rest is virtual so that the buttons for │ │ exit and cancel never move. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2315 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/09/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 │ │ The Button shadow (if any) is always black. That doesn't │ │ make sense on a black screen. Can't you make CDD detect │ │ Black background and modify shadow to dark Gray │ │ accordingly? │ │ When used to using shadow/buttons │ │ (allways!) the Black screen in fact can't be used. │ │ From Greg_W: The suggestion: Allow │ │ for different colored shadows. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2372 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/23/93 │ │ Reported In : 3004 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Kurt Lamoreaux 75450,1545 │ │ I have just recently seen a copy of DacEasy Accounting ( │ │ 4.4) and I saw a vertical scroll bar that I like _very_ │ │ much. To bad CServe won't take extended characters. │ │ I'll have to just give a description of it. │ │ The scroll bar is always five rows long, no matter how │ │ many rows are scrolled, and it is placed at the middle │ │ of the scroll. The top character is ASCII(30) (up │ │ arrow). Clicking on this allows you to scroll up one │ │ line at a time. The next character is ASCII(177) (checker │ │ box). Clicking here issues a PageUp on the │ │ scroll. The middle character is ASCII(18) (up-down │ │ arrow) and is simply a divider (it does nothing. The │ │ last two are ASCII(177) and ASCII(31), and, of course, are │ │ the reverse of the top two characters. │ │ At first I thought that it looked │ │ rather strange, but as I used it, I saw right away that │ │ how intuitive it was, and how it removed many of the │ │ problems that are faced by trying to guess how long a scroll │ │ might be, and have it reflected in the scrollbar. │ │ I would like to see a version │ │ of this in CDD. If Clarion doesn't include it, I may │ │ try it myself (looks pretty easy to implement). Any one │ │ else have thoughts on this? │ │ Kurt │ │ There is 1 Reply. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2471 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 9/27/93 │ │ Reported In : 3004 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There's a problem with formatted pictures that has been │ │ around since 2.1 and it's made its way into 3.0. For │ │ example: │ │ val real x string │ │ code │ │ val = 1.234 │ │ x = format(val, @P<<#.#P) │ │ So what's wrong with this picture you say? │ │ Well, x has the value ".1" not "1.2" like it should. The │ │ "."is treated just like any insertion character and doesn't │ │ align the decimal point in any way. Why doesn't it? │ │ The "." should align the decimal point of the number. Or │ │ at least use another symbol to align the decimal, like the │ │ "~" symbol. Example: x = format(val, @P<<#~.#P) │ │ At least then we'd be able to use the @P picture with │ │ decimal numbers with some assurance that we'll see the │ │ proper number I realize there are some uses for non │ │ aligned decimals with the @P picture, which is why I │ │ suggested a decimal alignment character. So @P<<#~.#P │ │ will align the decimal with the ~ symbol, which just │ │ happens to be next to the "." (Imagine that<g>). So YOU │ │ don't have to change a thing, and I will be able to │ │ format real numbers "correctly"without having to use fudge │ │ factors like "*10". With the decimal alignment character │ │ "~", if someone changes the picture, he doesn't have to │ │ remember to change the "*10" to "*100" in every calculation │ │ in the program. │ │ Note: this is a suggestion │ │ submitted on Compuserve. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2474 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 9/27/93 │ │ Reported In : 3004 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 3004 - suggestion from user - having an equate for a │ │ mouseright2, there is one for mouseleft2 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2609 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/12/93 │ │ Reported In : 3004 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ There is no easy way to enter decimal values like an adding │ │ machine where 1234 = 12.34 . A reliatively simple function │ │ that every adidng machine and accoutant in the world uses │ │ but cannot be done in clarion without handcoding. This │ │ could be a time saver to anyone who enters many numeric │ │ values in a row. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2888 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/03/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Paul Smulders 72114,3357 MSG#:40054 │ │ If Scroll Lock is on in a virtual screen, the screen │ │ scrolls with the arrowkeys, which is a nice feature. │ │ If the screen dimensions are such that the width of │ │ the virtual screen is equal to the width of the physical │ │ screen (80 columns), the Left and Right arrow keys should │ │ maintain their original function. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2996 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user wants to be able to put checkbox fields on the screen │ │ without any text next to it. │ │ [√][√][√][√] or [√] [√] [√] [√] │ │ cannot put them together without a space between them, if │ │ you leave one space between them at runtime there will be │ │ two spaces. │ │ R&D: This is a suggestion, it was never designed to do such │ │ a thing. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2997 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 11/09/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ user would like the ability to move screens off the current │ │ screen to the point where there is only the 1 line of the │ │ screen left on the current screen so that you can look at │ │ something in the middle of the screen. user says that │ │ nortons, pctools etc. move screens like this. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3032 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : J DateReported : 11/11/93 │ │ Reported In : 3006 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ SHOWIMAGE would be even better if it did not S T R E T C H │ │ images - ie. if it maintained the so-called 'aspect ratio' │ │ by proportionately reducing the picture regardless of the │ │ size or shape of area given to display in, blacking out the │ │ unused space in the area specified. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3080 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 11/17/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It seems there has been a change t the Lib so that when a │ │ Program exits back to DOS the Screen is always cleared. │ │ A couple of users would like it put back to the old way. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3147 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 11/24/93 │ │ Reported In : 3007 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When entering Negative numbers there is currently no method │ │ in which the KB Operator can change a negative number to a │ │ positive number by pressing the - key. │ │ I think this could be a very nice improvement since most KB │ │ Operators are use to a calculator reversing the sign for │ │ them when they press the - key. Currently I the programmer │ │ have to add a HOT KEY and some code to pull this off. It │ │ tends to be awkward for the end users. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3332 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 12/16/93 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The attached file shows a problem when you try to use a │ │ listbox with a trn attribute so that a graphic image will │ │ show behind the listbox. Everything is okay unless you │ │ scroll the list - horizontal or vertical. The image retains │ │ the text previously displayed at that location. See file │ │ attached. │ │ R&D: That's a cute idea, but no way...this most certainly │ │ was never intended to happen or work like that. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3347 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 12/17/93 │ │ Reported In : 3007 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Perhaps in v3.1, when we can somehow programmatically │ │ address relative position and total "records" communication │ │ to/from the Listbox vertical scrollbar, I suggest we │ │ consider "dynamic" scrollbars. This would mean that if no │ │ records sit outside the bounds of what is displayed in the │ │ listbox, the respective scrollbar disappears. │ │ For example, if there is a 20 row Listbox, and there are │ │ only 20 total records (or less) in the listbox, the │ │ verticalscrollbar disappears. Likewise, if the listbox is │ │ 60 columns, and the maximum record size displayed is │ │ 60 columns(or less), the horizontal scrollbar disappears. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3508 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 1/12/94 │ │ Reported In : 3006 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Martin Wehlou (Cactus) 72047,2444 MSG#:49726 │ │ What would be very useful is another two keyin template │ │ characters. One to allow entry of only numeric keys 0-9, or │ │ nothing. The other would allow 0-9, decimal point, plus and │ │ minus signs. I'd like to use these to enter numeric │ │ codes into string fields, which have to be sorted as │ │ accounts. │ │ The currently available '#' and '<' characters don't │ │ fill the bill, as they both adjust the entered number, or │ │ prefill it with zero's. Of course, the entry can be checked │ │ in the code and rejected if not numeric, but that's not │ │ half as elegant as having the right keyin template to │ │ begin with. │ │ -- Martin [Cactus Computing bvba - Belgium] │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3574 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 1/22/94 │ │ Reported In : 3007 RevisedDate : 1/24/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ It is my understanding that if you have a monochrome VGA │ │ that we will still detect the hardware as color and use the │ │ color codes for color monotors from the styles file and not │ │ the mono colors. Is it possible to change this or give the │ │ user the ability to force the specific graphic mode. │ │ R&D: Try MODE BW80 to get mono styles. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3665 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/01/94 │ │ Reported In : 3007 RevisedDate : 2/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Danny L. Joe 75010,2427 MSG#:52750 │ │ Suggestion: Create new Clarion language statement to "fix" │ │ asection of a virtual screen. │ │ Clarion's virtual screen capabilities are one of its most │ │ appealing aspects in terms of enhancing end-user │ │ productivity. It's unfortunate that this area seems to be │ │ getting so little attention. With a little more effort, its │ │ usability could be improved dramatically. │ │ Imagine how useful a split virtual/fixed screen could be. │ │ Itwould put an end to the table/form, list/screen, │ │ select/edit, menu/screen combinations we've made our users │ │ endure for so long. You could have a list box on one side, │ │ and the virtual edit screen on the other and never have to │ │ leave that context. Also, a single set of edit control │ │ buttons (add, edit, delete, cancel, save, help, etc.) │ │ could be used to control multiple list boxes and fields on a │ │ single virtual screen. Right now, only a pulldown can │ │ offer this kind of functionality, because the existing │ │ virtual screen concept is to ego-centric (it effectively │ │ takes over the whole show until closed!) │ │ What do you think? I don't know how that part of │ │ the video library is constructed, but if it wouldn't │ │ require reimplementing the whole thing, this should │ │ really be given some _serious_ consideration. I know in │ │ CDDW what I just described will be extremely easy to do, │ │ even if I have to hand code it (thanks to the all-powerful │ │ "setproperty" statement). I sure hope CDD can play │ │ tag-a-long on this before too long. Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4055 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/07/94 │ │ Reported In : 30071 RevisedDate : 3/07/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 58846 S17/Priority Support │ │ 05-Mar-94 13:25:02 │ │ Sb: Word Wrap │ │ Fm: Scott Merritt 71140,2502 │ │ To: SYSOP (X) │ │ When are you going to finally fix the text field, object, │ │ whatever you want to │ │ call it. You know the problem. The routine inserts │ │ additional spaces into the │ │ wrapped string so that the only way it looks right is when │ │ the display area is │ │ the same dimension as the original text dimension. I can't │ │ believe it still │ │ works like this particulary when CDD is now capable of │ │ sharing a variety of │ │ data with other applications, DBMSs' and report generators. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4272 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Joseph A. Bouterse 70541,305 MSG#:63238 │ │ Using CDD 3007.2, an ENTRY field with a picture of │ │ @N-9.2 acts much different than CPD 2.1 and as described │ │ on page 3-19 of the LRM. Clarion has always had the │ │ strange way of throwing the minus sign clear to the left │ │ edge of the field during entry, but always │ │ brought it back to immediately left of the number once │ │ the field was completed. However, now it stays clear to the │ │ left of the entry field boundary after completion. This │ │ is very confusing to the user and certainly not the way │ │ I would expect (or want) it to work. Am I missing │ │ something, or can this be added to the 3008 to-do list? │ │ Thanks, │ │ Joe Bouterse Creative │ │ Solutions, Inc. Indianapolis, IN │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4281 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/01/94 │ │ Reported In : 30072 RevisedDate : 4/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: E.J. Tejera 71066,1361 MSG#:63480 │ │ Suggestion: Allow for deleting entire lines in memos │ │ without having to have wordwrap enabled. │ │ Message: │ │ Ah! we must be using the few that don't fit in "almost │ │ always" <g>. A good example is capturing technical (very │ │ formatted) output from outside sources. If wordwrap is on │ │ it will almost always <g> trash the column formatting. │ │ I very much need to be able to delete a line even if not │ │ using word warp │ │ Eric. PS. As the sage said : "Wordwrap or not delete a line │ │ from time to time you must" │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4405 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/15/94 │ │ Reported In : 3008 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rick Weiss 71764,1312 MSG#:65992 │ │ >Using a Keyin Picture of K#####|-####K a ZIP code enter as │ │ 60601 displays as 60601 but prints as 60601-0000. Shoudn't │ │ the the field display and print the same. │ │ >>REPLY> the keyin picture only deals with keyin'd │ │ characters and has nothing to do with printing. │ │ OK, I would like to submit this as a R&D │ │ suggestion then. Allow a pattern with a character that │ │ specifies that the following formating be ignored if the │ │ data behind the "|" is blank. In other words, allow all of │ │ the formating options in a "P" picture as a "K" picture. │ │ This would allow us to print the data in the same │ │ format that it is displayed using the K picture. │ │ From Greg_W: I created an Example that shows the fact that │ │ -0000 gets stored in the variable even if you don't enter │ │ values. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4746 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : JB DateReported : 6/01/94 │ │ Reported In : 3008 RevisedDate : 6/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User wants ability to disable hotkey letters for pulldown │ │ menu items │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4939 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/12/94 │ │ Reported In : 3008 RevisedDate : 7/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Lee G. White 74067,3441 MSG#:81898 │ │ PLEASE - PLEASE return the logic that existed in CPD2.1 to │ │ CDD3.0 or at least provide a flag so that the spacebar │ │ ZERO's a numeric field instead of inserting another 0. │ │ I've got several clients who are VERY used to this │ │ and are now VERY upset with me! │ │ Lee [LSi] }:\ (make it change to {:> , please!) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5178 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Display is not updating field if only colors change │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you want to change the COLOR of a field using SETCOLOR │ │ you must change it's value since DISPLAY will only update │ │ the Screen when the value changes. │ │ Suggestion is to allow some kind of "Forced" screen update │ │ just in case all you want to do is change the Color. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5181 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Suggestion for Field Clearing on Entry. │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Is there an "attribute" for a screen ENTRY field which will │ │ result in the field being "cleared" upon the first │ │ keystroke? I know you have seen this, as have I, in other │ │ applications...., the field is entered with a display of │ │ thecurrent contents and if nothing is actually entered (just │ │ a normal field completion key, e.g., "tab" or "enter") the │ │ contents are unaffected, but if any other key is entered, │ │ the entire field "blanks" and the entered keystroke │ │ is displayed waiting for following keystrokes. I │ │ "thought" I had observed this action someplace within the │ │ CDD application itself, but I can't find it again. │ │ I think it is quite common in "Windows" │ │ applications. │ │ If there is no such "attribute" in CDD, │ │ I believe it would be a welcome addition. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5203 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 8/04/94 │ │ Reported In : 3009 RevisedDate : 8/04/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Escaping from a screen with a req'd field │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User suggestion: │ │ Even though there is a required field on a non-CUA FORM, │ │ you still should be able to ESCAPE off the FORM even if the │ │ required field isn't filled in. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5287 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/18/94 │ │ Reported In : 3009 RevisedDate : 8/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Suggestion for single keystroke immediate field │ │ Section │ │ Screen Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Just in case a suggestion I made awhile back didn't get │ │ saved: It would be real nice if the IMM (or some new) │ │ attribute on ENTRY fields behaved like the IMM attribute on │ │ LIST fields (IMMediately completing ACCEPT after each │ │ keystroke rather then when the data reaches the end of the │ │ field). │ │ If you've ever used QUICKEN, you no doubt appreciate its │ │ QUICKFILL feature, which is also similar (in concept) to │ │ Microsoft Word 6.0's ability to correct spelling errors │ │ on-the-fly. Another analogy is a locator field without a │ │ list (e.g., virtual or unseen). │ │ Users would love to have this feature (QUICKFILL, │ │ SMARTFILL,etc.), but it is impractical to implement right │ │ now while ACCEPT is gobbling up all the users keystrokes. │ │ One could alert A-Z and 1-9, etc., but this is way too │ │ messy. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0209 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/93 │ │ Reported In : 3001 RevisedDate : 1/25/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ One of the things that has always bugged me about Clarion │ │ is the way it removes the leading 0 from a date. It makes │ │ reports look funny. I was hoping that version 3 would fix │ │ this, but not so. │ │ Can you add to the wish list, a new Date Option so that if │ │ we want the leading 0, we can have it? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0269 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/05/93 │ │ Reported In : 3001 RevisedDate : 1/25/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 8. Can't use hotkeys to activate "Change/Ok/Cancel" on the │ │ "Select Color for Entry Field" screens. Also, same problem │ │ on the lower buttons of the Track Draw selection screen. │ │ (Tested OK PAS) │ │ Suggestion: │ │ 9. P L E A S E !!!! make RADIO BUTTONS available on the │ │ PULLDOWN menu item type selection. Or else allow entry of │ │ source associated with menu items (toggles etc). Case in │ │ point, a pulldown choice of LPT ports to "check" the │ │ desired destination. It looses something in the translation │ │ if you have to go to a FORM/SCREEN procedure type │ │ (primarily due to the pulldown disappearing). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2850 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/01/93 │ │ Reported In : 3006 RevisedDate : 1/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark Goldberg 75250,2551 MSG#:39702 │ │ Suggestions: │ │ editor: alt-w-c file window should be much wider, as full │ │ paths are used. │ │ IDE: edit styles always brings up the IDE's style / │ │ default style vs. the style specified in the .APP (for │ │ appgen), or maybe the last style editted. │ │ editor: default replace checkboxes, seem like they │ │ would be better altered should default to replace │ │ within block (my preference) should default to │ │ replace all within block (my guess most peoples pref) │ │ Appgen: External Source (that points to │ │ .CLA's) should have the source button active and a │ │ method of pulling up the source file. (module) │ │ IDEA: An attribute of a field (in dct │ │ as well as data sections) should be if it is │ │ _usually_ a display field, then when adding this field in │ │ screener it would default to │ │ display. │ │ IDEA: Add a generator │ │ toggle, that will generate source code with _ALL_ │ │ embed points included even EMPTY ones. Why ? So that we │ │ can look at generated code for the current │ │ procedure and visually see where the embed points │ │ would be. This would be more natural than looking │ │ at the templates. Ok, so maybe this suggestion is │ │ streching it a bit. │ │ IDEA: Appgen: Add a universal color re-mapper (no not │ │ styles), but rather a way to change all of a color │ │ code to another code, this would be used for │ │ reconcilling code written under differently mapped styles │ │ files. │ │ cdd filename.btv (I use .btv for btrieve │ │ files) causes the editor to be loaded and a subsequent │ │ xtrace to be generated (mg: crash\xtrace.002) │ │ edit errors editor (W0): should be │ │ able to switch documents, I would find this useful to │ │ be able to check data structure, and map, etc. │ │ ooops: what do we do if we │ │ disable _all_ fields on a form ?? I did a │ │ disable(pre:field) vs. a disable(?pre:field) and it caused │ │ all fields to be disabled. (Except maybe, my main │ │ pulldown) I │ │ did do a disable(?pre:field), but I did it before the │ │ screen was open, thereby disabling the previous │ │ screen, although it recognized the new field equate, │ │ maybe a compiler warning is appropriate here, or │ │ maybe I should just be more careful. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3547 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 1/18/94 │ │ Reported In : 3007 RevisedDate : 1/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a few users have suggested they would like the ablility to │ │ copy screens, pulldowns, reports, local data and formulas │ │ from one procedure to another │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3628 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 1/27/94 │ │ Reported In : 3006 RevisedDate : 1/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Barry Smith 73072,3314 MSG#:52163 │ │ The big question. Why doesn't Clarion have a smoother │ │ upgrade path? A document saying "watch for these things │ │ whenyou move to 3007" would have made life easier. Also, say │ │ "this is like this now because ..." Agggh. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3707 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/05/94 │ │ Reported In : 3007 RevisedDate : 3/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User requests lft rt and center attributes for setmsg │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3761 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : RB DateReported : 2/10/94 │ │ Reported In : RevisedDate : 2/10/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about adding a new validation type to the │ │ dictionary and Screener similar to "Must be in List" except │ │ instead of Buttons, we have a drop down list box with a │ │ Arrow () at the end of the field. This would make the DOS │ │ product behave even more like the Windows product. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3780 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/11/94 │ │ Reported In : 30071 RevisedDate : 2/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Are the 'B' (sound on/off) and 'V' (screen blanker) │ │ switchesfrom earlier Clarion releases no longer supported in │ │ CDD 3? The sound on/off is impt to a number of our users - │ │ how can I get the equivalent of B=NO in CDD 3? -dave cohen │ │ Can we add the b=no ability. Through API? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3798 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/12/94 │ │ Reported In : 30071 RevisedDate : 2/12/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Hide mouse pointer when keyboard is accessed, revealing │ │ it again only when │ │ mouse movement is detected. This keeps it out of the way │ │ when it obviously │ │ isn't needed--very programmer friendly (hint). │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3851 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 2/15/94 │ │ Reported In : 30071 RevisedDate : 2/17/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A user would like to have embeds around doing lookups. │ │ This is desired for both the forms and browses. He is │ │ aware that he can change his own and has already done so. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3862 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : J DateReported : 2/16/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User wants ability to declare a group as external │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4067 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 3/08/94 │ │ Reported In : 3007 RevisedDate : 3/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ USER WOULD LIKE TO HAVe the help id's for a screen be │ │ defaulted to the procedure label. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4080 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 3/09/94 │ │ Reported In : 3007 RevisedDate : / / │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a user has the desire to take a data section from an │ │ embedded source and have it import to the data button so │ │ that he can use the screen formatter in the app gen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4116 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/15/94 │ │ Reported In : 30072 RevisedDate : 3/15/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ For any given field which has been #FIXed in %Field, there │ │ does not seem to be a %Symbol allowing one to verify the │ │ following: │ │ 1) Validity Checks Off 2) Cannot Be Zero Or Blank 3) Must │ │ Be True Or False │ │ Any ideas for accomplishing this WITHOUT %Field being used │ │ on a screen? │ │ Douglas │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4171 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/22/94 │ │ Reported In : 30072 RevisedDate : 3/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ : 61540 S8/3.0 Support │ │ 21-Mar-94 16:21:24 │ │ Sb: #61414-#case-insensitive Q sort │ │ Fm: Jeff Moyers 70254,2434 │ │ To: Greg Whitaker [Clarion] 76711,1035 (X) │ │ Greg: │ │ >> Storing the Upper of the field in another queue field │ │ is │ │ >> about the best suggestion I can think of. │ │ Thanks for your reply. This solution will work, BUT look at │ │ its potential │ │ costs. Consider a queue that has a 48 byte Name field that │ │ is your sort key. │ │ If I have a queue with 50,000 records (not at all uncommon │ │ in our application), │ │ and I have to duplicate that 48 byte string for sorting, │ │ that adds (48 * 50000) │ │ = 2,400,000 bytes (2.34MB) to my memory requirements. Yes, │ │ I could trim the key │ │ down some. Yes, I could use a temporary file. Yes, I could │ │ other things. But │ │ the ability to sort the queue case-insensitive is the only │ │ logical _solution_ │ │ to the problem; everything else is a workaround. │ │ In reality, in protected mode (we are), this will │ │ automatically get swapped to │ │ disk if memory is exhausted, but that _really_ slows things │ │ down. Adding │ │ another 4MB (to a base of 4MB) of memory, would cost our │ │ company approximately │ │ $28,000. (200 machines * $140/machine). This can't be that │ │ hard a thing for │ │ you guys to do, and I know I'm not the only person whose │ │ ever suggested it. │ │ Could we at least get it to be considered?!?. Thanks! │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4244 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 3/29/94 │ │ Reported In : 30072 RevisedDate : 3/29/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Sb: #dictionary not req. │ │ Fm: Jon B. Bushey 71521,2267 │ │ To: sysop (X) │ │ In Generator, the dictionary should not be required. There │ │ are many times when │ │ our programs do not require a dictionary. One example is a │ │ program we wrote to │ │ use the findfirst and findnext directory functions. It │ │ does not use any files. │ │ It simply builds a queue of matching file names. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4342 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/08/94 │ │ Reported In : 3008 RevisedDate : 4/08/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 64988 S8/3.0 Support │ │ 08-Apr-94 02:13:59 │ │ Sb: _Filespec 'BUG' │ │ Fm: Rob Mousley 100075,772 │ │ To: Debby Herman 72662,475 │ │ Hi Debby │ │ If you're in a LAN environment it is not uncommon to have a │ │ filespec like: │ │ SYS:\SubDir\Filename.dat │ │ We specify pathnames like this in filespec variables, no │ │ problem. But the │ │ validation in the dictionary when you try to hard code a │ │ file spec like this │ │ throws it out. │ │ The validation should allow for a drive 'letter' like SYS:. │ │ Rob from Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4357 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/11/94 │ │ Reported In : 3008 RevisedDate : 4/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 64709 S8/3.0 Support │ │ 06-Apr-94 18:20:01 │ │ Sb: Suggestion │ │ Fm: Danny L. Joe 75010,2427 │ │ To: Debby Herman 72662,475 │ │ Debbie or Greg, │ │ Please ask R&D to give us some way to have the IMM │ │ attribute in ALL field types │ │ cause ACCEPT to complete after every keystroke, as it now │ │ does in LIST and │ │ button fields. This will enable us to add an AUTOFILL │ │ feature to our entry │ │ fields, similar to the LOCATOR field on record lists. This │ │ is _very_ │ │ significant to our users (most competing products have this │ │ feature). │ │ Thanks, │ │ Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4369 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 4/13/94 │ │ Reported In : 3008 RevisedDate : 4/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ users would like to see updated matrix.ctl and laser.ctl │ │ files. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4431 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/19/94 │ │ Reported In : 3008 RevisedDate : 4/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 MSG#:66535 │ │ Debby>>With linker warnings you can go ahead and create the │ │ .exe. Select the Continue Button. │ │ Rob>>>> Ah yes, I know to press Continue, but the whole │ │ point is I don't _want_ to have to press continue to get │ │ passed spurious warnings that I want to ignore. CDD takes │ │ so long to regenerate & compile that one prefers to make │ │ coffe, go for a walk, whatever and to have the app up & │ │ running when one comes back! To have to press continue │ │ justadds irritation to irritation! That's why I'd prefer to │ │ have a switch saying 'Yes, I realise that the warnings │ │ are going to show, but I want to continue automatically.' │ │ Rob from Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4480 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : SA DateReported : 4/21/94 │ │ Reported In : 3009 RevisedDate : 4/21/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ 1. Load template varibles from generator. │ │ 2. APP layout and DCT layout to develope 3rd. party │ │ software. Auto Documentor Syntax checker │ │ 3. Clarion 3.0 driver is not consistant with the library │ │ name ???cla21.lib. │ │ 4. The copy function from Clarion can only Copy to .DAT │ │ names regardless of the name variable passed to it. │ │ Extention is ignored. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4549 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 4/25/94 │ │ Reported In : 3008 RevisedDate : 4/25/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ suggestion from end user │ │ wants to be able to pass a variable number of parameters to │ │ a procedure/function like an optional repeat in C │ │ pass a field as an entity-parameter │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4608 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 5/03/94 │ │ Reported In : 3008 RevisedDate : 5/03/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 69337 S8/3.0 Support │ │ 02-May-94 09:00:44 │ │ Sb: #68869-Multiple Forms for Brows │ │ Fm: Alan L. Schoolcraf 73133,2624 │ │ To: Debby Herman 72662,475 │ │ Debby - │ │ PMFJI but, at DEVCON 93, I talked to Bruce about │ │ allowing a parameter │ │ for RUN that would leave the files open and not lose the │ │ pointers. This is │ │ needed for instance if you want to RUN from a button on a │ │ browse. Bruce │ │ thought this was already there and when I told him it │ │ wasn't, he had me talk │ │ to one of you guys about getting it done. │ │ Do you know if it's in the works? │ │ ALAN │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4872 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 6/27/94 │ │ Reported In : 3009 RevisedDate : 6/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 78734 S9/3.0 Discussion │ │ 24-Jun-94 15:54:03 │ │ Sb: Need *.STY inCLARION.RED │ │ Fm: Barry McClure 75170,1100 │ │ To: Debby Herman 72662,475 │ │ Debby, │ │ Is there a reason why we can't have a redirection │ │ directory for │ │ styles files? Like: │ │ *.STY = ;F:\CLARION3\x │ │ I find I have a lot of duplicate mystyle.STY files in │ │ several │ │ subdirectories. They each get updated independently │ │ and is a │ │ hassle to maintain. If they're like me, I think a lot │ │ of │ │ programmers may work with 1 or 2 styles for most of │ │ their programs. │ │ Having a central location of styles is the way to go │ │ and will │ │ eliminate a lot of duplicate style files. │ │ I know what you're going to say. "Why not just enter │ │ the │ │ complete path name for the style file from the options │ │ menu and │ │ have it point to a subdirectory where all the styles │ │ are kept?" │ │ This creates a problem when the programmer is about to │ │ release a │ │ new copy of the software. He (or she) is going to have │ │ to change │ │ it and recompile the app because the user's program │ │ expects to │ │ find it in the current subdirectory and not in the │ │ style │ │ subdirectory. │ │ So how about asking R&D to put a "*.STY" in │ │ CLARION.RED? (pretty │ │ please.<g>) │ │ Barry... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4940 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/13/94 │ │ Reported In : 3009 RevisedDate : 7/13/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 82108 S8/3.0 Support │ │ 11-Jul-94 15:37:49 │ │ Sb: CDD Version Number │ │ Fm: Will Fastie 76655,1566 │ │ To: All │ │ Greetings, All: │ │ Is the version number (i.e., 3009 or 3.009) or a │ │ representation of it │ │ available anywhere within the runtime environment? If so, │ │ where? If it's │ │ stored in a variable somewhere, that's all we'd need. │ │ If not, a CVersion() function should be added to the │ │ system. │ │ Will │ │ Written on 11-Jul-1994 @ 15:20:45 EDT using Windows NavCIS │ │ PRO 1.21 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5162 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 7/28/94 │ │ Reported In : 3009 RevisedDate : 7/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Modify the Tree Display in Generator │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 85935 S8/3.0 Support │ │ 27-Jul-94 13:10:56 │ │ Sb: Suggestion for Generator │ │ Fm: Danny L. Joe 75010,2427 │ │ To: Greg Whitaker [Clarion] 76711,1035 │ │ Hi Greg, │ │ Please enter as a suggestion (for version 3.1 maybe?) the │ │ ability to expand(+) │ │ and collapse (-) the call tree in the CDD Generator. This │ │ is a great feature in │ │ CW, and would be extremely helpful to have in CDD as well. │ │ The existing FIND feature is helpful, but only if one │ │ remembers the name of the │ │ desired func/proc. Some of these trees can be _very_ long │ │ and are therefore │ │ quite difficult to navigate when the tree is fully expanded │ │ all the time as it │ │ is right now. │ │ Regards, │ │ Danny │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5186 │ │ Product : RW Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/01/94 │ │ Reported In : 3009 RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │ Suggestions for next report Writer │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Rob Mousley 100075,772 │ │ Some irritating things in CRW - please forward the │ │ following as siggestions for │ │ the next version: │ │ ----------------------------------------------------------- │ │ When placing fields from a file layout onto a report, you │ │ select a field from the list, the next time you hit CtrlF, │ │ the file layout pops up with the cursor on the next field - │ │ which is what you mostly want, great. Then you hit Enter to │ │ select the field. │ │ When selecting total fields, the same is not true. The │ │ system does not remember which total field you selected │ │ lastso you always have to scroll down to it, and then when │ │ you press Enter you're popped into the field editor. This │ │ is inconsistent and drives me (at least) round the bend. │ │ When placing fields, Enter = Select! │ │ -------------------------------------------------------- │ │ Please put locators on all possible system Browses eg │ │ Clarion function lists inside the formula editor - make it │ │ work like CPD2.1! - - │ │ ----------------------------------------------------------- │ │ The File driver selector screen that pops up when you │ │ selecta file to import is also an abortion... Try to │ │ mimimise the keystrokes needed & make those keystrokes │ │ logical. (No flames, I know this is version 1.0<g>, │ │ this is just feedback.) │ │ Rob from Chariot │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5187 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/01/94 │ │ Reported In : RevisedDate : 8/01/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Wants locator on color list in style file │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ #: 85360 S8/3.0 Support │ │ 25-Jul-94 11:31:28 │ │ Sb: Picking Colors in CDD3 │ │ Fm: Thom Gray 76244,2460 │ │ To: Support │ │ In the CDD3 application generator, when I'm selecting a │ │ color from the list of │ │ colors stored in the style file, a locator field would be │ │ *SO VERY HELPFUL*. I │ │ can't remember all those codes, but the names are │ │ meaningful. So sorting by │ │ alpha helps, but that alone doesn't come close to how easy │ │ it would be to pick │ │ those lil' suckers with a locator. │ │ Thanks! Thom Gray 76244,2460 │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5195 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/02/94 │ │ Reported In : 3009 RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ suggestion for array checking │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ I guess what I'm really asking for is if "Array Index │ │ Checking" │ │ is turned on, Clarion should at least tell you the │ │ line in the │ │ program the subscript was out of bounds. Don't you │ │ agree? Please │ │ pass this suggestion onto R&D. Thanks. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5197 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/02/94 │ │ Reported In : 3009 RevisedDate : 8/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ hotkey in environment to save app from anywhere │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Have some global HotKey that saves your file. Then every 5 │ │ minutes or so the developer can hit the HotKey & know that │ │ he's safe again. │ │ He wants this from anywhere at any level. In an embeded │ │ source window even not just from the application properties │ │ window. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5242 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : NA DateReported : 8/11/94 │ │ Reported In : 3009 RevisedDate : 8/11/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Cosmetic or user interface problem │ │ Synopsis │ │ System Halt Window │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User would like the abililty of the system stop window to │ │ go to the particular line that is giving problems │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5262 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : UK DateReported : 8/16/94 │ │ Reported In : 3009 RevisedDate : 8/16/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Suggestion or documentation error │ │ Synopsis │ │ Editor Suggestion │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ When you load a large file, it says on the botton of the │ │ screen the record number. Can it do the same when you │ │ save, so that you know the machine has not locked. The │ │ cursor stays in the same place while the save is taking │ │ place and you do not know what is going on. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5281 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/18/94 │ │ Reported In : 3009 RevisedDate : 8/18/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Template Language Suggeston │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ a suggestion from an end user is to have a templage │ │ language statment that would allow the template to check │ │ and see if there was embedded code added to a certain │ │ embed. THis would allow the template to include the embed │ │ code or generate some other code. │ │ ex. #if embedded('my embed section') │ │ #embed('my embed section') │ │ #else │ │ ... include this code ... │ │ #endif │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5293 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 8/19/94 │ │ Reported In : RevisedDate : 8/19/94 │ │ Fixed In : Status : Suggestion │ │ Origin : External │ │ Severity : Unassigned Severity │ │ Synopsis │ │ CRW as a dll in a Clarion Program │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ How about the possibility of creating DLL's/LIB's for CRW │ │ for incorporation into CDD app's. Just wondering whatever │ │ happened to the suggestion since I didn't get any response. │ │ Any idea if this might even be of future consideration? │ │ Just thought I'd ask - │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5317 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 8/29/94 │ │ Reported In : 3.1 RevisedDate : 8/29/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Does not operate as documented │ │ Synopsis │ │ Hot key access to different radio buttons │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Please provide hot-key access to different radio button │ │ options In the Constraints dialog in the dictionary editor │ │ when declaring relationships. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 5318 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : QA DateReported : 8/29/94 │ │ Reported In : 3.1 RevisedDate : 8/29/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Does not operate as documented │ │ Synopsis │ │ Field Pool │ │ Section │ │ Suggestion │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ If you are not going to add a field pool in the dictionary │ │ editor as was previously stated, could you provide a means │ │ to copy one field from one file to another so as to give us │ │ the ability to copy similar fields (pictures, validations, │ │ keyboard handling, etc.) to insure likeness between field │ │ for like fields. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0236 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PS DateReported : 2/03/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In the Validate template allow Multi component validations. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0278 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/06/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ A small problem that I have found while using the examples │ │ that came with 3.0 is that on a validation screen you can't │ │ get out without selecting something. │ │ SCENARIO - user inadvertantly makes a change to the first │ │ letter of a field that makes it invalid. Validation table │ │ pops up. Users doesn't remember what was in the field │ │ before. (In 2.X you could just escape and the original │ │ contents would be undisturbed). In 3.0 you must select │ │ something even if it may be incorrect. The templates should │ │ be changed to allow a cancel button on the validation │ │ screen. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1339 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 5/25/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The validate does not go to the closest match of what they │ │ typed in, like it did in 2.1. │ │ RND:Working on it...it is a bit complicated with the │ │ BrowseAction/ResetFirst interaction. Thought it was done, │ │ but found a bug when setting past the last record. │ │ Soon...but not 3003. │ │ R & D : Suggestion/Enhancement │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2189 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 8/23/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ validate on a field with IMM skips the field after the │ │ field being validated │ │ field1(imm) field2(imm) field3(imm) │ │ after validate on field 1, cursor appears on field 3, and │ │ field 2 is skipped │ │ Q&A: This is going to happen all the time because of the │ │ use of Press() in the Templates. Remove the IMM from │ │ fields that are to be validated. Because of the │ │ Press(value); Press(TabKey) usage in validate. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2297 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : GW DateReported : 9/03/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The validate template has no facility for escaping or │ │ aborting the validate. │ │ I'm reporting this as a bug only because the function is │ │ not available not because it's broken. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2325 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 9/15/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: David L. Shapiro 72122,330 │ │ Concerning validate procedures, you should ask if I want to │ │ automatically move to the next field (include "press(T │ │ ABKey)" code) on the procedure properties window. This is │ │ need so that validates work with multiple immediate fields. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2569 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 10/05/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ Validate Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Scott Smiley 75610,2212 MSG#:34693 │ │ can we get immediate locators in validate template like the │ │ browse and select in 3005d? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1634 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 6/23/93 │ │ Reported In : 3003 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VGA Color Library │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The VGA COLOR KIT doc should mention that the *.CLR needs │ │ tobe ditributed with the finish app. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0186 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 2/01/93 │ │ Reported In : 3001 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Watch Arrays in VID..... │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0469 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : ?? DateReported : 3/01/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User Claims that Vid will not work if his IBM token ring │ │ drivers are loaded. he has 3000. │ │ R & D : We are using INT 63. This will be fixed in a │ │ future release. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0941 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: E.J. Tejera 71066,1361 │ │ 1-.VID seems to crash a lot, is there a trick in the setup? │ │ I can crash VID by: a-.pressing F5 (always) │ │ b-. asking for an out of scope value (sometimes) │ │ c-.ALtF6 (sometimes) │ │ BTW, stealth and CLAVID simply do not get along in my │ │ Gateway 2000 4DX2-66V, while every other app (including │ │ CDD) works fine. │ │ 2-.^E rearrange fields does not always work, specially on │ │ screens with many fields. │ │ 3-.On quitting the program, the DOS prompt is not displayed │ │ at pos1 (left of screen), but rather at whatever position │ │ the cursor was last in the compiled program. │ │ 4-.CLAVID will not totally release either extended or │ │ conventional memory. If I load CLAVID repeatedly, it will │ │ eventually allocate (and fail to release) most of the │ │ computer's memory. │ │ 5-.CLAVID, serch string popup often displays garbage. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1046 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 4/16/93 │ │ Reported In : 3002 RevisedDate : 4/27/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark Goldberg 75250,2551 │ │ Is it possible to step through code inside of an include │ │ when running in Clavid ? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1248 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 5/14/93 │ │ Reported In : 3003 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ watch variables - trying to watch a decimal field, get │ │ message 'Variable not watchable (structured type)' │ │ examine variables - trying to examine a decimal field, │ │ comes up as an array of hex values │ │ R& D : Enhancement for future version of CLAXVID. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 1890 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : PB DateReported : 7/16/93 │ │ Reported In : 3004 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ in vid you can choose or examine a global group or each of │ │ the individual fields in the group. if i want to look at │ │ the individual fields in group from a file, i have to look │ │ at the entire group. i also cannot set watch variables on a │ │ field within a group │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2926 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 11/04/93 │ │ Reported In : 3006 RevisedDate : 11/04/93 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Randy Rogers 75730,1337 MSG#:40404 │ │ It would be nice not to have a VID key combination that │ │ displays the same basic information as Alt= does at run │ │ time? │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 3670 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : CS DateReported : 2/02/94 │ │ Reported In : 3007 RevisedDate : 2/02/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ Fm: Mark W. Coil 76627,1532 MSG#:52470 │ │ I'm using 3007.1 now and just discovered a problem with │ │ debug. If you change a source file, and then run Debug │ │ without doing a make first, Debug crashes the system when │ │ it tries to read the changed source. This occured within │ │ Windows 3.0 and froze windows as well. However, Windows │ │ wasable to recover by terminating Debug with Ctrl-Alt-Del. │ │ Of course, you wouldn't really want to do debug without │ │ doing the Make first, but it can happen inadvertently. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 4950 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : BN DateReported : 7/15/94 │ │ Reported In : 3009 RevisedDate : 7/22/94 │ │ Fixed In : Status : Suggestion │ │ Origin : Internal │ │ Severity : Unassigned Severity │ │ Synopsis │ │ Ctrl Break not showing which line had executed in VID │ │ Section │ │ VID │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ In when running an application in CLAVID, after doing a │ │ CTRL+BREAK, the line that was executing should be the │ │ highlighted line. │ │ ------------------------Work Arounds-------------------- │ │ Press the space bar to execute one more line of │ │ code. The Highlited line of code will now be │ │ correct. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 0368 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : TB DateReported : 4/09/93 │ │ Reported In : 3002 RevisedDate : 4/26/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ View Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ View -- when the warning screen appears and tells you that │ │ you might have to wait..... how about a way to abort │ │ looking at it like pressing cancel instead of ok -- │ │ ----------------------------------------------------- │ │ Upgrade suggestion : Have a Function similar to ShowWarning │ │ which returns a byte: 1 - OK │ │ 0 - Cancel │ │ IF ~ConfirmScreen │ │ RETURN │ │ . │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2068 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/09/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ View Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ The view template doesn't consider fixed rows in the list │ │ when building the queue for the list. Can we do a little │ │ %screenfieldfix action in the view template. User has │ │ requested it. │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2085 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/10/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ View Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ On the View template screen if you switch text modes, the │ │ scroll bar move to the top of the file when the screen is │ │ redisplayed. Can we save the position in the queue and │ │ select(?list,position) │ └───────────────────────────────────────────────────────────────────────┘ ┌───────────────────────────────────────────────────────────────────────┐ │ ProblemNumber : 2086 │ │ Product : CDD Duplicate No.: 0 │ │ Reported By : DH DateReported : 8/10/93 │ │ Reported In : 3004 RevisedDate : 4/28/94 │ │ Fixed In : Status : Suggestion │ │ Origin : │ │ Severity : Unassigned Severity │ │ Synopsis │ │0 │ │ Section │ │ View Template │ ├───────────────────────────────────────────────────────────────────────┤ │ │ │ Problem Description │ │ │ │ User would like the ability to do a text search in the file │ │ that the view template displays │ └───────────────────────────────────────────────────────────────────────┘