|
Thanks jim -----Original Message----- From: Jim Langston [mailto:jlangston@celsinc.com] Sent: Tuesday, September 04, 2001 11:17 AM To: rpg400-l@midrange.com Subject: RE: Newby subfile question Jose, you are correct, it is DSPATR(BL), but... BL acts differently on a dumb tube and on a color display (client access type connection). According to what I am reading, you also have to specify DSPATR(HI) with DSPATR(BL) to get a red/blinking text. DSPATR(BL) would just produce red text. Your other option seems to be specifying the COLOR keyword. >From the online manual: http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/qb3auk00/2.1.2.16 ?ACTION=MATCHES&REQUEST=DSPATR&TYPE=FUZZY&searchTopic=TOPIC& searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT 2.1.2.16 Adding Color You can design your displays for use on display stations that show color. The DDS keyword COLOR allows you to specify the following colors for fields: green, white, red, turquoise, yellow, pink, and blue. This keyword is ignored if it is selected for a field displayed on a display station that does not support color. If the COLOR keyword is not specified in the DDS for the display file but the display station is specified in the display station description as a color display station, displays that you have designed for display stations that do not support color can also be used for the color display station. The keywords DSPATR(UL) and DSPATR(RI), if specified on separate fields, function the same as they do for the 5250 display station. However, the keywords DSPATR(CS), DSPATR(HI), and DSPATR(BL) produce the following colors on a color display station (the specified display attributes CS, HI, and BL are suppressed): _______________________ ________________ ________________ _______________ | Color Produced on the | Display | Display | Display | | Color Display Station | Attribute | Attribute | Attribute | | when No COLOR Keyword | Selected: | Selected: | Selected: | | is Specified | DSPATR(CS) | DSPATR(HI) | DSPATR(BL) | |_______________________|________________|________________|_____________ __| | Green (normal) | | | | |_______________________|________________|________________|_____________ __| | Turquoise | X | | | |_______________________|________________|________________|_____________ __| | White | | X | | |_______________________|________________|________________|_____________ __| | Red, no blinking | | | X | |_______________________|________________|________________|_____________ __| | Red, blinking | | X | X | |_______________________|________________|________________|_____________ __| | Yellow | X | X | | |_______________________|________________|________________|_____________ __| | Pink | X | | X | |_______________________|________________|________________|_____________ __| | Blue | X | X | X | |_______________________|________________|________________|_____________ __| Regards, Jim Langston Programmer/Analyst Cels Enterprises, Inc. -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Jose Vega Sent: Tuesday, September 04, 2001 10:47 AM To: rpg400-l@midrange.com Subject: Newby subfile question Hi All, How do I get the text to Blink on a display file as in an "alert" that a certain condition exists. I looked up and used the blink keyword "DSPATR(BL)" but I believe that may just apply to the cursor. Any help will be greatly appreciated. Jose _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.