searching for :

Char2Hash()
ComEvalCollection()
GetApplication()
GetPointerPos()
GraBackground()
GraEdge()
GraGradient()
GraSegLoad()
GraSegSave()
IsUnicode()
RandomInt()
RandomKey()
Str2Unicode()
TranslateSysColor()
UIThreadId()
Unicode2Str()
UuidCreate()
UuidFromChar()
UuidToChar()

greetings by OHR
Jimmy

Are they in the tools help??

Jim

AUGE_OHR wrote:
> searching for :
> 
> Char2Hash()
> ComEvalCollection()
> GetApplication()
> GetPointerPos()
> GraBackground()
> GraEdge()
> GraGradient()
> GraSegLoad()
> GraSegSave()
> IsUnicode()
> RandomInt()
> RandomKey()
> Str2Unicode()
> TranslateSysColor()
> UIThreadId()
> Unicode2Str()
> UuidCreate()
> UuidFromChar()
> UuidToChar()
> 
> greetings by OHR
> Jimmy
> 
>

hi,

> Are they in the tools help??

no, this are no tools Function.

this IS v1.9.355 SL1, but how to use a Function
if i can find it in SL1 v1.9.355 Help File ?

greetings by OHR
Jimmy

Jimmy,

> searching for :
> 
> Char2Hash()
> ComEvalCollection()
> GetApplication()
> GetPointerPos()
> GraBackground()
> GraEdge()
> GraGradient()
> GraSegLoad()
> GraSegSave()
> IsUnicode()
> RandomInt()
> RandomKey()
> Str2Unicode()
> TranslateSysColor()
> UIThreadId()
> Unicode2Str()
> UuidCreate()
> UuidFromChar()
> UuidToChar()

What exactly are you looking for.
These functions are described in the manual.

Peter

hi,

> What exactly are you looking for.
> These functions are described in the manual.

hm ... my is 4,59 MB (4.814.314 Bytes)
create       3. Juni 2009, 04:18:31
change ?  4. Mai 2006, 12:08:52

im using SL1 v1.9.355 "without" Visual Style

greetings by OHR
Jimmy

Jimmy,

>i´m using SL1 v1.9.355 "without" Visual Style

What you mean is that you are using the SL-1 version that (supposedly) 
only contains PDR fixes and no new features, like all the functions you 
have listed. So, why do you expect the help file to include those new
features, when they (supposedly) shouldn't be available in that version?

Of course, this isn't really the case, as those functions still exist in
the runtime DLLs, but you aren't supposed to use them with that version.
The only difference between those two SL-1 versions (besides the old help 
and source files from 1.90.331) is the old "SOM.DLL" (also from 1.90.331)!

Personally, I find it ridiculous to pretend to have two separate versions 
of SL-1 -- which not only have the exact same version and build numbers, 
but are binary identical (with the above mentioned exception) -- and 
which basically only differ in the fact that only users with active 
subscriptions are allowed to use some of their (new) features.

As you (obviously) have an active subscription, just use the "full" SL-1
version of 1.90.355, but keep the old "SOM.DLL" from version 1.90.331,
so you don't have to use the new "Visual Style" -- and you will have all
the documentation (and other features) that come with SL-1.

And, as the "SOM.DLL" is part of the runtime, which can be redistributed
freely, it looks like there really isn't any way for Alaska to prevent 
any of their registered 1.90 customers form using any and all those new 
features, anyway. 

Actually, the only thing making this a little more difficult for those 
(second class) users is, in fact, the missing documentation update!

-- 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
---                                                                      ---

Hi,

a realy confusing thing ... 

but don't you need a LIB file for every DLL at link time ?

Hubert,

>but don't you need a LIB file for every DLL at link time ?

Only for the ones you want to statically link to your project, not for 
the ones that are statically linked to those DLLs or the ones that are
dynamically loaded at runtime. For example, there is no LIB file for 
the "SOM.DLL", "XppNat.DLL", "XppRT0.DLL", or "XppUI1.DLL" or any of
the DBEs.

Anyway, all the LIB and DLL files are updated in either case, and only
the help and (most of) the source files are left unchanged with the 
"update" version of 1.90.355.

-- 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
---                                                                      ---

hi,

>>im using SL1 v1.9.355 "without" Visual Style
>
> What you mean is that you are using the SL-1 version that (supposedly)
> only contains PDR fixes and no new features, like all the functions you
> have listed. So, why do you expect the help file to include those new
> features, when they (supposedly) shouldn't be available in that version?

sorry this is not true. both Version are the same !!!

> Of course, this isn't really the case, as those functions still exist in
> the runtime DLLs, but you aren't supposed to use them with that version.

why not ? the Function are the same and do work like ComEvalCollection()

... and ... did you try to Subclass one of these "non visual Style" XbParts
and look into there Property ?

IMHO the only Differenze is that "visual Style" is "default" OFF and
"without" Version is about 10-15% "faster" (while must not "paint"
GraBackgound etc) depending how much XbParts you use.

> Personally, I find it ridiculous to pretend to have two separate versions
> of SL-1 -- which not only have the exact same version and build numbers,
> but are binary identical (with the above mentioned exception) -- and
> which basically only differ in the fact that only users with active
> subscriptions are allowed to use some of their (new) features.

please try it yourself, both Version are realy the same !!!
you do not need any active Subscription to get v1.9.355 which is
a "bugfix" Version of v1.9.331

i realy wonder why someone want to use "XP" visual Style...
they are not available on VISTA or WIN7 as MsComCrt v6.x does
NOT support visual Style ...

but Win7 does support DX9 in OS() ... when will Xbase++ support
DX Hardware Accellerator ???

***

the Reason why i use "without" Version :
Xbase++ can not work with on chinese OS() with XP Manifest !
as soon i use a Mainfest all chinese Sign in a XbpSLE or XbpBrowse are 
"lost"

IMHO there a 3 Windows Version : chinese, japanese and "all other"

i do not think that Xbase++ will every work with chinese or japanese
Sign correct as long we do not have full Unicode and DBCS Support.
( Str2Unicode() and Unicode2Str() work wrong on UFT-8 )

greetings by OHR
Jimmy

Jimmy,

>>>i´m using SL1 v1.9.355 "without" Visual Style

>>What you mean is that you are using the SL-1 version that (supposedly)
>>only contains PDR fixes and no new features, like all the functions you
>>have listed. So, why do you expect the help file to include those new
>>features, when they (supposedly) shouldn't be available in that version?

>sorry this is not true. both Version are the same !!!

That's what I'm saying! But according to Alaska, there are two separate
Xbase++ SL-1 or Xbase++ 1.90.355 versions. One is a complete download with
updated source and help files, while the other is a "partial" download,
which doesn't include those. The complete version is reserved for customers 
"with an active subscription" and the other is also available for "any 
registered Xbase++ 1.90 customer", which has 1.90.331 installed.

There is nowhere any mention of a version "without Visual Style", so I 
assumed you used the "updated" SL-1 version rather than the "new install"
SL-1 version. Correct me, if I'm wrong!

>>Of course, this isn't really the case, as those functions still exist in
>>the runtime DLLs, but you aren't supposed to use them with that version.

>why not ? the Function are the same and do work like ComEvalCollection()

Because only customers "with an active subscription" are allowed to use 
the new features. All others are only allowed to have the bug fixes. Of 
course that is practically impossible, because both versions are binary 
identical and contain all the new features. But by not releasing the help 
files, Alaska is trying to prevent non-subscription customers from using
or even knowing about those features. Otherwise, what advantage would it
be to pay for a (yearly) subscription, if you get the same features as
someone who didn't spent that money?

>IMHO the only Differenze is that "visual Style" is "default" OFF and
>"without" Version is about 10-15% "faster" (while must not "paint"
>GraBackgound etc) depending how much XbParts you use.

Can you explain what "Version" you are using, and how binary identical 
versions can have different default behaviors in the first place?

>please try it yourself, both Version are realy the same !!!

That's what I said! You said there is an "SL1 v1.9.355 "without" Visual 
Style", which you are using. If that isn't the "updated" version, then
what is it?

>you do not need any active Subscription to get v1.9.355 which is
>a "bugfix" Version of v1.9.331

Exactly! But you do need an active Subscription to be "entitled" to use 
the new "not-just bug-fix" features of 1.90.335, which includes those new 
functions, which is (apparently) the reason why the help files are not
updated in the "bug-fix-only" SL-1 version!

Anyway, if you do have an active subscription you should also have the 
new help files, so there shouldn't be any problem for you. The only thing
that I would like to know is: what version it is that you are using that 
you are calling "SL1 v1.9.355 "without" Visual Style", as I might want 
to use that feature myself -- especially if it is indeed so much faster!

-- 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
---                                                                      ---

hi,

> you are calling "SL1 v1.9.355 "without" Visual Style", as I might want

ok "without" = original v1.9.311 "patch" Version.

> to use that feature myself -- especially if it is indeed so much faster!

try 80x25 XbpPushbuttons "without" visual Style vs. "with" visual Style
or ownerdraw "without" visual Style vs ownerdraw "with" visual Style

"drawing" Grabackground and GraEdges and XBP_STATUS add up
to 10-15% using XP Manifest and IMHO it will grow using more
Xbparts with "visual Style".
on "older" PC you can "see" it more than on "newer" PC, so it also
your GFK / Driver how fast your 2D Engine is.


btw. i can use Codejock Skinframework to "style" my XbParts with
every Theme i like ... and it is fast, so why should i use "visual Style"
from Xbase++ which does not work with chinese OS() as i have report.

to Alaska Subscriptions Information Politics : no Comment

greetings by OHR
Jimmy

Hello:
good afternoon.
In ..\GraSys.prg they are used methods (ie: :drawFocusRect, :drawBackground) 
that I did not find in the XbpPresSpace() help.
May be that I am using an old help file? (my one is dated from 09.04.2009)

Beling
TIA


AUGE_OHR escreveu:
> hi,
> 
>> you are calling "SL1 v1.9.355 "without" Visual Style", as I might want
> 
> ok "without" = original v1.9.311 "patch" Version.
> 
>> to use that feature myself -- especially if it is indeed so much faster!
> 
> try 80x25 XbpPushbuttons "without" visual Style vs. "with" visual Style
> or ownerdraw "without" visual Style vs ownerdraw "with" visual Style
> 
> "drawing" Grabackground and GraEdges and XBP_STATUS add up
> to 10-15% using XP Manifest and IMHO it will grow using more
> Xbparts with "visual Style".
> on "older" PC you can "see" it more than on "newer" PC, so it also
> your GFK / Driver how fast your 2D Engine is.
> 
> 
> btw. i can use Codejock Skinframework to "style" my XbParts with
> every Theme i like ... and it is fast, so why should i use "visual Style"
> from Xbase++ which does not work with chinese OS() as i have report.
> 
> to Alaska Subscriptions Information Politics : no Comment
> 
> greetings by OHR
> Jimmy 
> 
>