Author | Topic: fontsize unReadable := .T. on XbpTabPage | |
---|---|---|
Erik L. | fontsize unReadable := .T. on XbpTabPage on Wed, 15 Jul 2009 09:32:12 +0200 Hello, To access our software users have to identify themselves. On the screen there is a XbpSLE where :unReadable = TRUE so you only see black dots, in this case 10 of them. The administrator is able to add users. He also has to enter the identification code. This is the same XbpSLE as mentioned before. The only difference is the owner of the XbpSLE. In the first case this is XbpDialog in the second case it is XbpTabPage. On the XbpTabPage I only see 8 black dots, bigger than the 10 in the first case (I can still enter 10 characters). When I set unReadable to FALSE, the behaviour in both cases is the same, no difference in lettersize. Anyone noticed this behaviour ? What is a/the solution ? Regards, Erik | |
Andreas Gehrs-Pahl | Re: fontsize unReadable := .T. on XbpTabPage on Wed, 15 Jul 2009 06:14:43 -0400 Erik, Why did you post this to the BugReport NG rather than the GUI NG? This is obviously not a bug, but a question about SLEs and Fonts. >The only difference is the owner of the XbpSLE. In the first case this is >XbpDialog in the second case it is XbpTabPage. Don't you mean Parent, rather than Owner? And shouldn't it be either the XbpDialog's :DrawingArea or another XbpStatic, like a Group Box, which is the Parent of the XbpSLE in the first case? >On the XbpTabPage I only see 8 black dots, bigger than the 10 in the >first case (I can still enter 10 characters). The reason for the difference is that a different font is used in each of those cases. The reason for a different font being used is probably because you don't specify a desired font for the SLE, and the inherited (Parent's) font is different in those two cases. >What is a/the solution ? Simply assign the desired font, for example: oSLE:SetFontCompoundName('10.Arial') This would guarantee that always the same font is used, regardless of the parent's fonts. -- Andreas --- --- Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net 415 Gute Street or: Andreas@DDPSoftware.com Owosso, MI 48867-4410 or: Andreas_Gehrs-Pahl@CrimeCog.com Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net --- --- | |
Erik L. | Re: fontsize unReadable := .T. on XbpTabPage on Wed, 15 Jul 2009 13:37:35 +0200 Correct, parent in first case is xbpdialog:drawingarea. Your solution is my standard option, I always use setfontcompoundname() with every single xbpsle. I placed it in the bugreport NG because it gets messed up with the var unreadable. If I don't use :unreadable := .T. it al works fine, which indicates to me that the setfontcompoundname() is used correctly and your solution won't solve my problem. Andreas Gehrs-Pahl schreef: > Erik, > > Why did you post this to the BugReport NG rather than the GUI NG? This is > obviously not a bug, but a question about SLEs and Fonts. > >> The only difference is the owner of the XbpSLE. In the first case this is >> XbpDialog in the second case it is XbpTabPage. > > Don't you mean Parent, rather than Owner? And shouldn't it be either the > XbpDialog's :DrawingArea or another XbpStatic, like a Group Box, which is > the Parent of the XbpSLE in the first case? > >> On the XbpTabPage I only see 8 black dots, bigger than the 10 in the >> first case (I can still enter 10 characters). > > The reason for the difference is that a different font is used in each > of those cases. The reason for a different font being used is probably > because you don't specify a desired font for the SLE, and the inherited > (Parent's) font is different in those two cases. > >> What is a/the solution ? > > Simply assign the desired font, for example: > > oSLE:SetFontCompoundName('10.Arial') > > This would guarantee that always the same font is used, regardless of > the parent's fonts. > > -- Andreas > > --- --- > Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net > 415 Gute Street or: Andreas@DDPSoftware.com > Owosso, MI 48867-4410 or: Andreas_Gehrs-Pahl@CrimeCog.com > Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net > --- --- | |
Andreas Gehrs-Pahl | Re: fontsize unReadable := .T. on XbpTabPage on Wed, 15 Jul 2009 08:38:55 -0400 Erik, >Correct, parent in first case is xbpdialog:drawingarea. >Your solution is my standard option, I always use setfontcompoundname() >with every single xbpsle. Can you make a small example program that shows your problem? I don't see this kind of issue here, but I don't use unreadable SLEs on Tab Pages. >I placed it in the bugreport NG because it gets messed up with the var >unreadable. If I don't use :unreadable := .T. it al works fine, which >indicates to me that the setfontcompoundname() is used correctly and >your solution won't solve my problem. That depends on when you set :Unreadable to TRUE and when you set the Font Name and if you :Configure() or not. A demo program would be most helpful to determine the reason for your problem and to possibly find a workaround or even a fix for your issue. Also, don't forget to mention what OS and what version of Xbase++ you are using, as this could be important. -- Andreas --- --- Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net 415 Gute Street or: Andreas@DDPSoftware.com Owosso, MI 48867-4410 or: Andreas_Gehrs-Pahl@CrimeCog.com Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net --- --- | |
Erik L. | Re: fontsize unReadable := .T. on XbpTabPage on Thu, 16 Jul 2009 09:15:57 +0200 Andreas, Because our source code is full of our own creations regarding gets and stuff, I created a simple example program using basic xbase++ XbpSLe and XbpTabPage. I found that with basic xbase++ there is no difference between sle's on drawingarea or tabpage nor between readable or unreadable. I tried it on W2000 and WXP, with different fonts. Just to show you I'm not imagening things I added a word document with some screenshots I have to dig into our source code to find the cause of this behaviour. Wish me luck. Thanks for your response. Andreas Gehrs-Pahl schreef: > Erik, > >> Correct, parent in first case is xbpdialog:drawingarea. > >> Your solution is my standard option, I always use setfontcompoundname() >> with every single xbpsle. > > Can you make a small example program that shows your problem? I don't > see this kind of issue here, but I don't use unreadable SLEs on Tab Pages. > >> I placed it in the bugreport NG because it gets messed up with the var >> unreadable. If I don't use :unreadable := .T. it al works fine, which >> indicates to me that the setfontcompoundname() is used correctly and >> your solution won't solve my problem. > > That depends on when you set :Unreadable to TRUE and when you set the > Font Name and if you :Configure() or not. A demo program would be most > helpful to determine the reason for your problem and to possibly find a > workaround or even a fix for your issue. > > Also, don't forget to mention what OS and what version of Xbase++ you are > using, as this could be important. > > -- Andreas > > --- --- > Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net > 415 Gute Street or: Andreas@DDPSoftware.com > Owosso, MI 48867-4410 or: Andreas_Gehrs-Pahl@CrimeCog.com > Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net > --- --- testSLE.doc |