List of Bugfixes in bwprint version 6.1c.06.01 BaanIVc: # 10404 (VHNT4703): BwPrint: Save and Save As... From: Source Manager Date: Fri, 10 Nov 2000 11:00:20 +0100 (MET) Release: BaanIVc Date: 2000/11/10 Script: MergeProject Project: VHNT4703 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) BwPrint does not have Save and Save As... functionality Problem Description (Technical terms) Serialize function is only implemented in one direction: input, no output Workaround None Test Procedure run BwPrint and use the new File menu options and the new toolbar button Affected Executables bwprint.exe bshell bw etcetera Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 94359 515167 50 BaanIVc: # 10604 (BDNT4853): BwPrint: height of lines with a barcode From: Source Manager Date: Wed, 13 Dec 2000 17:22:53 +0100 Release: BaanIVc Date: 2000/12/13 Script: MergeProject Project: BDNT4853 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) Height of lines with a barcode is too large. Height should be according to normal text height. Barcode must overlap the next few lines. Problem Description (Technical terms) When some time ago (project 1807) the number of lines per inch was made flexible, the space assigned to each line was set to the maximum space used by text, line drawing chars, and barcodes on that line. For barcodes, this was not correct. Workaround none Test Procedure use menu Help->Barcode test Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 106466 558776, 840924 20 BaanIVc: # 10352 (VHNT4649): BwPrint: confusion which printer will be used From: Source Manager Date: Mon, 6 Nov 2000 13:01:52 +0100 (MET) Release: BaanIVc Date: 2000/11/06 Script: MergeProject Project: VHNT4649 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) When a not-installed but existing network printer is specified in the bpf file, then it is used but not shown in the Printer Setup Dialog. Problem Description (Technical terms) The printer is only visible in the Printer Setup Dialog when it is installed first. When you use the Network... button of the Printer Setup Dialog and select a not-installed printer, then it is first installed and then becomes visible in the Printer Setup Dialog. The AddPrinterConnection call can be used to do the same from within BwPrint. Workaround None Test Procedure Use a bpf file with a not-installed but existing network printer on NT4 and see whether it becomes visible in the Printer Setup Dialog Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 102063 548194 30 BaanIVc: # 10344 (VHNT4688): BwPrint: store non-default charset in registry From: Source Manager Date: Fri, 3 Nov 2000 16:51:59 +0100 (MET) Release: BaanIVc Date: 2000/11/03 Script: MergeProject Project: VHNT4688 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) Customer cannot select his favourite font which has the Symbolic charset Problem Description (Technical terms) In Project 3660, the CF_SELECTSCRIPT flag was added to the Font Dialog, to guarantee that only a font with the correct CharSet (as determined by the locale setting) could be selected. Workaround nine Test Procedure Try to select a font with Symbolic charset, and see whether it is remembered correctly the next time that BwPrint is started. Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 104890 556178 20 BaanIVc: # 10290 (VHNT4565): Added support for new barcode library to bwprint From: Source Manager Date: Mon, 30 Oct 2000 08:52:29 +0100 (MET) Release: BaanIVc Date: 2000/10/30 Script: MergeProject Project: VHNT4565 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) Barcode type 39 is not printed correctly. Problem Description (Technical terms) - Distance in bars in barcode for type 39 is wrong - aspect ratio dialog doesn't work correctly (spin button) Workaround none Solution - new barcode version from DlSoft - fixed some bugs in the installer - moved axbarcode.ocx to $BSE\bin instead of winnt\baan\bin - fixed bug in aspect ratio dialog - display much more types of barcodes in barcode test Test Procedure - install a new portingset - run bwprint, do the barcode test in the Help menu - check barcodes - in the barcode.bpf file (generated at 2nd step), click right mouse button, and change aspect ratio. This should work now. Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 103223 840924 etc 20 BaanIVc: # 10263 (VHNT4623): BwPrint: set early default locale From: Source Manager Date: Tue, 24 Oct 2000 13:04:21 +0200 (METDST) Release: BaanIVc Date: 2000/10/24 Script: MergeProject Project: VHNT4623 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) BwPrint crashes on Windows 95 when specifying an unknown printer. Problem Description (Technical terms) BwPrint crashes during the emitted log message, because the TSS locale is not yet set. This is due to the addition of TSS-to-native conversion added to log_msg() in project bugf_VHUX3325 in the file \general\lib\al_1\al_log.c. Workaround None Test Procedure See Scopus defect 25887 Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 25887 868548,543878 30 BaanIVc: # 10156 (VHNT4530): Add arguments for barcode printing bwprint From: Source Manager Date: Tue, 10 Oct 2000 16:48:05 +0200 (METDST) Release: BaanIVc Date: 2000/10/10 Script: MergeProject Project: VHNT4530 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) There is no way to control checksum calculation and showing of check digit(s) in barcode, generated by bwprint. Problem Description (Technical terms) The bc$() function is used to generated barcode images. At this moment this function supports only the following arguments: barcode type (type), height (rows) and the barcode string itself (barcode). Workaround No workaround Solution Add 2 extra, optional, arguments to the bc$ function. So, the syntax of the bc$ function is now: string bc$( long type, long rows, string barcode(.), [long calc_chksm, long shw_chkdgt]) where calc_chksm: Calculate CheckSum In case set to 1: the barcode contains a checksum calculation In case set to 0: the barcode contains not a checksum calculation shw_chkdgt: Show Check Digit In case set to 1: the barcode string does show the checkdigit(s) In case set to 0: the barcode string does not show the checkdigit(s) Remark: In case the barcode does not contain a checksum calculation, it makes also no sense to set shw_chkdgt to 1. The arguments calc_chksm and shw_chkdgt are optional arguments. In case these arguments are not specified the bc$ function behaves in the same way it did before this modification. That means it will generate the following sequence (hex.): 1B 16 2x 2y zz zz zz .... zz Here: x = barcode type, y = number of bytes of barcode string, zz zz zz .... zz = barcode string In case these arguments are specified the bc$ function behaves in the modified way. That means it will generate the following sequence (hex.): 1B 17 2x 2y 2v 2w zz zz zz .... zz Here: x = barcode type, y = number of bytes of barcode string, v = calc_chksm, w = shw_chkdgt, zz zz zz .... zz = barcode string Furthermore modified bwprint to enable support of these 2 new arguments. In case bwprint detects the sequence 1B 16 .... bwprint behaves in the way it did before this modification. In case bwprint detects the sequence 1B 17 .... bwprint behaves in the modified way. That means it will also process the 2 extra new arguments, and turn on the property AutoParity (this is checksum calculation), and/or ShowCheckDigit, depending on the value of these arguments. Note: No modifications are made in filter, because there was no request for it. And filter will still work correctly because old way of working is still the same. Test Procedure Create reportfields having print expression using bc$. Specified fields using bc$ function with and without new arguments. Print this report and use Windows Printer to print this report, so bwprint will be started. Affected Executables bshell bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 103223 840924 20 510375 Comments To be able to compile report(script) or other 4GL program using bc$ function with this 2 new arguments, also a modified bic_global is needed, which supports these 2 extra (optional) arguments !!! So, deliver also a new bic_global together with porting set containing these modifications. BaanIVc: # 10131 (VHNT4000): Unknown devmode caused Access Violation in bwprint From: Source Manager Date: Fri, 6 Oct 2000 16:58:02 +0200 (METDST) Release: BaanIVc Date: 2000/10/06 Script: MergeProject Project: VHNT4000 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) Bwprint generates an Access Violation when printing and crashes. Problem Description (Technical terms) To determine the buffersize of the DEVMODE structure bwprint uses the function DocumentProperties. This function returns -1 because the DEVMODE is not filled. Secondly program tries to allocate -1 bytes, causing the Access Violation. Workaround not applicable Solution Now bwprint generates an error message "No DEVMODE for printer '%1' available." %1 is the friendly name of the printer. This problem occurs when something is wrong with the setup of the printerdriver. Therefor the printerdriver may need to be re-installed or updated . Test Procedure Try to print to a printer which is not correctly installed. Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 101636 544479 30 BaanIVc: # 10038 (VHNT4490): BwPrint: -a option (number of copies) does not work From: Source Manager Date: Mon, 2 Oct 2000 09:36:26 +0200 (METDST) Release: BaanIVc Date: 2000/10/02 Script: MergeProject Project: VHNT4490 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) -a option (number of copies) in BwPrint does not work Problem Description (Technical terms) Problem present since 6.1c.04.02. 6.1c.04.01 is ok. See Scopus defect 100278 Workaround None Test Procedure See scopus Affected Executables bwprint Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 100278 541357, 533290 30 BaanIVc: # 10022 (VHNT4172): BwPrint: barcode problems From: Source Manager Date: Thu, 28 Sep 2000 16:07:46 +0200 (METDST) Release: BaanIVc Date: 2000/09/28 Script: MergeProject Project: VHNT4172 Created on: BaanIVc Type: bugfix Problem: Problem Description (Customer terms) some barcodes are displayed incorrectly Problem Description (Technical terms) The problem occurs since 6.1c.04.01 The situation is still ok in 6.1c.04. In between a change was made from MM_TWIPS to MM_TEXT. Previously, the barcode ocx width and height were set in twips, but now in pixels. Workaround None Test Procedure Use barcode type 10 Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 99906 545736,545222,547663,485873,836672,526223,856634,866907,536492 20 BaanIVc: # 9628 (VHNT4200): Removed dutch resources From: Source Manager Date: Fri, 25 Aug 2000 14:01:49 +0200 (METDST) Release: BaanIVc Date: 2000/08/25 Script: MergeProject Project: VHNT4200 Created on: BaanIVc Type: porting specific change Problem: Problem Description (Customer terms) Removed some last pieces of dutch resources. Problem Description (Technical terms) Made file consistent with ERP. Workaround None Solution bwprint.rc: Removed dutch stuff Test Procedure None Affected Executables bwprint.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10)