Joe, Thanks for things well explained. I fully understand where layers come in handy now.
for the moment, I'm pleased with my two designs, one for printing pre-printed cards, the other one for printing all QSO details + shades, ines, etc ... But I will look into the multiple layer use for the 1,2 or 3 qso's, this is a neath approach. Thanks and 73 Phil ON4VP ----- Original Message ----- From: "Joe Glockner" <[EMAIL PROTECTED]> To: "Phil ON4VP" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Monday, December 30, 2002 4:49 PM Subject: Re: [DXBase] label designer - LAYERS > Phil, > > On the subject of LAYERS, I think that the best way for me > to explain what layers do for the user, is to describe what > I went through when I made the QSL CARD file that is on > the DXbase2003 CDROM (and therefore should be in your Labels > subdirectory on your harddrive). > > > The QSL Card file is called by the filename: > > MULT_QSL_Card-3q_auto_select.crd > > > > Some background on why I made this file as I did - and therefore > describes a bit of how LAYERS can help.. > > I wanted to make a QSL CARD file that could "automatically" > print a 1-QSO, or a 2-QSO, or even a 3-QSO card -- AND, have > the spacing on the card be EVEN (smooth looking) no matter how > many QSO's are to be printed. > > Since I wanted the "even spacing", I made "3 LAYERS" -- with > Layer #1 being the 1-QSO layer ; Layer #2 being the 2-QSO layer; > and, Layer #3 being the 3-QSO layer.. The beauty of the LAYERS > is that YOU "can decide" which LAYER is to be used at which time. > > For instance, in the example QSL Card file (named above), the > "Defintion" for Layer #1 is: > > Len(MODE)>0 and Len(MODE2)=0 and Len(MODE3)=0 > > ((Note: this coding for the Layer #1 defintion will ONLY give me > a TRUE output when there is something in the FIRST QSO > data line - but "nothing" in the 2nd or 3rd data line. > Indicating that there is ONLY 1-QSO to be printed by > this layer.)) > > > > The "Definition" for Layer #2 is: > > Len(MODE)>0 and Len(MODE2)>0 and Len(MODE3)=0 > > ((Note: this coding for Layer #2 defintion will ONLY give me a > TRUE output when we have 2 LINES of DATA to be printed)). > > > The "Definition" for Layer #3 is: > > Len(MODE3)>0 > > ((Note: this coding for Layer #3 defintion will only give me a > TRUE output when we have a full 3 lines of DATA to be > printed)). > > > By using the 3 separate LAYERS, my goal of a smooth looking QSL > Card, no matter how many QSO's per card (up to 3) are to be > printed. > > > When you open up (in the Label Designer Module) the above > mentioned example QSL Card file, all 3 layers will be on top > of each other initially.. To LOOK at each layer individually, > find the "LAYERS" small "window" - it will probably have a > GREEN Checkmark next to each LAYER.. DOUBLE-CLICK on the 2nd > and 3rd LAYERS' GREEN Checkmark and it will turn to a RED > "X" ... at this time, the 1-QSO Layer is visible all by itself. > You can look at each layer separately by "toggling" the GREEN > Checkmark on the two layers you DO NOT want to see right now. > > To LOOK at the LAYERs' Definitions, you will once again still > be in the LAYERS small "window" -- RIGHT-CLICK anywhere in the > "white area" of that window and then select the words: > > Layer Defintions ... > > > That is a "rough" narrative describing layers.. LAYERS is a > "Decision Making" tool that you can use in just about any > scenario. > > > 73 de Joe wa6axe > > > > > > > > Phil ON4VP wrote: > > > > Joe, many thanks !! > > > > The problem was indeed the appearance condition set to max 6 caracters. > > I now have placed two fields called "call" on top of eachother. > > > > one set for max 6 caracters with font size 16 > > one set for more than 6 caracters with font size 12 > > > > All my cards are printed fine !! > > Thanks a lot. > > > > Phil ON4VP > > (now trying to understand 'layers') > > > > ----- Original Message ----- > > From: "Joe Glockner" <[EMAIL PROTECTED]> > > To: "ON4VP" <[EMAIL PROTECTED]> > > Sent: Monday, December 30, 2002 12:27 PM > > Subject: Re: [DXBase] label designer, call won't print > > > > > Good morning Phil! > > > > > > Well, it doesn't matter at all which one is on top or on the > > > bottom.. The reason for this is that the APPEARANCE CONDITION > > > code that you put in "for each CALL field textbox" will decide > > > "which one is to be used - and when". > > > > > > The Appearance Condition for the CALL textbox that is for > > > a callsign with "more than 6 characters" is: > > > > > > Len(CALL)>6 > > > > > > > > > and > > > > > > > > > The Appearance Condition for the CALL Textbox that is for > > > a callsign with "less than 7 characters" is: > > > > > > Len(CALL)<7 > > > > > > > > > > > > Phil, I am sitting here at the computer and am on-line - so if you > > > want to pick my brain - go ahead and ask me! > > > > > > 73 de Joe WA6AXE > > > > > > > > > > > > ON4VP wrote: > > > > > > > > Yes Joe, > > > > > > > > I think you solved my problem. > > > > I copied a field to a new design and the appearance condition was set to > > max > > > > 6 caracter due to the font size being big (like 16). > > > > > > > > Thanks for pointing this out. > > > > I'm in the running now and will follow your lead. > > > > > > > > I will make two 'call' fields on top of eachother, one with small > > printing > > > > (for long callsigns) and one for regular 6 caracter callsigns with > > bigger > > > > text size. > > > > > > > > 1) which one has to sit on top of the other ? > > > > 2) can you send me the exact syntax for both fields to put into > > conditions > > > > variable > > > > > > > > Joe, many thanks and happy newyear > > > > > > > > Phil ON4VP > > > > > > > > ----- Original Message ----- > > > > From: "Joe Glockner" <[EMAIL PROTECTED]> > > > > To: "Phil ON4VP" <[EMAIL PROTECTED]> > > > > Cc: <[email protected]> > > > > Sent: Monday, December 30, 2002 12:37 AM > > > > Subject: Re: [DXBase] label designer, call won't print > > > > > > > > > Phil, > > > > > > > > > > If, by chance, you "copied" one of the files that uses > > > > > "Appearance Conditions" - that would answer the problem.. > > > > > > > > > > I myself have made many labels/QSL cards that use "TWO" CALL > > > > > fields (on top of each other) .. The one CALL field is used > > > > > for Callsigns that are "LESS than 7 characters" and uses the > > > > > FONT size of 12 .. the other CALL field is for Callsigns that > > > > > are "GREATER than 6 characters" and uses a FONT size of 10.. > > > > > > > > > > This way I could let the program make the decision as to which > > > > > CALL FIELD to USE ... The "conditional coding" for these two > > > > > CALL fields can be found by: > > > > > > > > > > (1) Left-click on the one CALL field and then Right-click on > > > > > that CALL field -- when the menu comes up - choose > > > > > > > > > > Appearance Condition > > > > > > > > > > > > > > > In that you will see something like: > > > > > > > > > > Len(CALL)>6 > > > > > > > > > > > > > > > ..... NOW ... > > > > > > > > > > If you DO NOT want the selection of TWO Different CALL text boxes, > > > > > just DELETE one of them and then REMOVE the "Appearance Condition" > > > > > from that remaining CALL Text Box.. > > > > > > > > > > > > > > > I hope that his helps Phil! > > > > > > > > > > 73 de Joe wa6axe > > > > > > > > > > Phil ON4VP wrote: > > > > > > > > > > > > Jack, > > > > > > > > > > > > I've tested more : when I even make the label field for the stations > > > > call > > > > > > VERY BIG and place the field very distant from any other fields, the > > > > call is > > > > > > not printed on the card from the moment it is more then 6 caracters. > > > > > > > > > > > > WA6DER is printed, WA6DER/P not ... > > > > > > > > > > > > Any ideas > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jack" <[EMAIL PROTECTED]> > > > > > > To: "Phil ON4VP" <[EMAIL PROTECTED]>; <[email protected]> > > > > > > Sent: Sunday, December 29, 2002 6:05 PM > > > > > > Subject: Re: [DXBase] label designer, call won't print > > > > > > > > > > > > > Phil, > > > > > > > > > > > > > > When placing QSO field variables on the card design, there were a > > > > couple > > > > > > > choices. One was to use the callsign from user options. This > > would > > > > > > result > > > > > > > in only one callsign ever showing up on the card for your > > callsign. > > > > The > > > > > > > other method is to use the OprCall variable. In this case, > > whatever > > > > > > > callsign was in the Operator callsign field for each QSO would be > > the > > > > one > > > > > > > that shows up on the card. > > > > > > > > > > > > > > Hope this helps, > > > > > > > Jack > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Phil ON4VP" <[EMAIL PROTECTED]> > > > > > > > To: <[email protected]> > > > > > > > Sent: Sunday, December 29, 2002 11:47 AM > > > > > > > Subject: [DXBase] label designer, call won't print > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I made some nice looking cards and all prints out qiet nice but > > with a > > > > > > > regular callsign in the 'call' field. > > > > > > > > > > > > > > but ... > > > > > > > > > > > > > > when I have a call with another prefix like PA/W4RT or KP4/N3EE or > > > > > > > when I have a special suffix like W5ER/M or KB2ERT/QRP or AA7YY/P > > > > > > > > > > > > > > the callsign is not printed on the cards. > > > > > > > > > > > > > > I've checked and I'm almost shure that the fields are wide enough > > to > > > > cover > > > > > > > all letters in the field. > > > > > > > What could be going wrong ? > > > > > > > > > > > > > > Phil ON4VP > > > > > > > > > > > > > > > > > > > > > --- StripMime Report -- processed MIME parts --- > > > > > > > multipart/alternative > > > > > > > text/plain (text body -- kept) > > > > > > > text/html > > > > > > > The reason this message is shown is because the post was in HTML > > > > > > > or had an attachment. Attachments are not allowed. > > > > > > > Please post in Plain-Text only.--- > > > > > > > _______________________________________________ > > > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > > > To UNSUBSCRIBE please visit: > > > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > > > To UNSUBSCRIBE please visit: > > > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > > > > > - - - - - - - - - - - - - - - - - - - - - - - > > > > > > To UNSUBSCRIBE please visit: > > > > > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > > > > > > > > > > > _______________________________________________ > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > - - - - - - - - - - - - - - - - - - - - - - - > > To UNSUBSCRIBE please visit: > > http://mailman.qth.net/mailman/listinfo/dxbase > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase >
