Here's a good indication of what is to come 
Anyone who is testing VX can try this:

oColorDialog:=xbpcolordialog():new(SetAppWindow(),SetAppWindow())
oColorDialog:defaultColor:=GraMakeRGBColor({255,255,255})
oColorDialog:displayall:=.T.
oColorDialog:title:="My Colour Dialog"
oColorDialog:center:=.T.
oColorDialog:create()
oColorDialog:display()

just a teaser! This means that some of the functionality of Xbase 1.9 is
included in Visual Xbase - it must've edited our 1.82 files!!!
Now, can anyone work out how to get the colour the user has picked out of
the class?

Methods for XbpColorDialog appear to be: (This is a direct list from
ClassDescribe())
setPos()
setOwnerThread()
currentSize()
classDescribe()
new()
hide()
display()
addchild()
isVisible()
init()
isEnabled()
helpRequest()
ChildList()
Disable()
Quit()
ClassName()
ReplyEvent()
Status()
Show()
ChildFromName()
setName()
InitClass()
Configure()
Visible()
SetOwner()
Enable()
DelChild()
HandleEvent()
isDerivedFrom()
ClassObject()
Create()
Move()
SetEvent()
SetParent()
Destroy()
CurrentPos()

And Member Vars:

Quit
DisplayAll
Mode
Parent
Container
Center
Move
NoDither
UserColors
DefaultColor
Cargo
Owner
ShowHelp
Title
HelpRequest
Name

My guess is that :diplay() should return it. ie like XbpFile.

Jim


Simon Burford, Uluru Support wrote:

> Here's a good indication of what is to come 
> Anyone who is testing VX can try this:
> 
> oColorDialog:=xbpcolordialog():new(SetAppWindow(),SetAppWindow())
> oColorDialog:defaultColor:=GraMakeRGBColor({255,255,255})
> oColorDialog:displayall:=.T.
> oColorDialog:title:="My Colour Dialog"
> oColorDialog:center:=.T.
> oColorDialog:create()
> oColorDialog:display()
> 
> just a teaser! This means that some of the functionality of Xbase 1.9 is
> included in Visual Xbase - it must've edited our 1.82 files!!!
> Now, can anyone work out how to get the colour the user has picked out of
> the class?
> 
> Methods for XbpColorDialog appear to be: (This is a direct list from
> ClassDescribe())
> setPos()
> setOwnerThread()
> currentSize()
> classDescribe()
> new()
> hide()
> display()
> addchild()
> isVisible()
> init()
> isEnabled()
> helpRequest()
> ChildList()
> Disable()
> Quit()
> ClassName()
> ReplyEvent()
> Status()
> Show()
> ChildFromName()
> setName()
> InitClass()
> Configure()
> Visible()
> SetOwner()
> Enable()
> DelChild()
> HandleEvent()
> isDerivedFrom()
> ClassObject()
> Create()
> Move()
> SetEvent()
> SetParent()
> Destroy()
> CurrentPos()
> 
> And Member Vars:
> 
> Quit
> DisplayAll
> Mode
> Parent
> Container
> Center
> Move
> NoDither
> UserColors
> DefaultColor
> Cargo
> Owner
> ShowHelp
> Title
> HelpRequest
> Name
> 
>

You are totally correct 

nResult:=oColorDialog:display()

returns the selected colour.
Great stuff. Wonder what else has been added?!?

Simon Burford
Uluru Database Support
http://www.UluruDatabase.com

Download the latest version of Uluru Professional, Pro
Database Manager for xBase++ from http://www.UluruDatabase.com

"James Loughner" <jwrl@charter.net> wrote in message
news:khhqKli1DHA.2012@S15147418...
> My guess is that :diplay() should return it. ie like XbpFile.
>
> Jim
>
>
> Simon Burford, Uluru Support wrote:
>
> > Here's a good indication of what is to come :)
> > Anyone who is testing VX can try this:
> >
> > oColorDialog:=xbpcolordialog():new(SetAppWindow(),SetAppWindow())
> > oColorDialog:defaultColor:=GraMakeRGBColor({255,255,255})
> > oColorDialog:displayall:=.T.
> > oColorDialog:title:="My Colour Dialog"
> > oColorDialog:center:=.T.
> > oColorDialog:create()
> > oColorDialog:display()
> >
> > just a teaser! This means that some of the functionality of Xbase 1.9 is
> > included in Visual Xbase - it must've edited our 1.82 files!!!
> > Now, can anyone work out how to get the colour the user has picked out
of
> > the class?
> >
> > Methods for XbpColorDialog appear to be: (This is a direct list from
> > ClassDescribe())
> > setPos()
> > setOwnerThread()
> > currentSize()
> > classDescribe()
> > new()
> > hide()
> > display()
> > addchild()
> > isVisible()
> > init()
> > isEnabled()
> > helpRequest()
> > ChildList()
> > Disable()
> > Quit()
> > ClassName()
> > ReplyEvent()
> > Status()
> > Show()
> > ChildFromName()
> > setName()
> > InitClass()
> > Configure()
> > Visible()
> > SetOwner()
> > Enable()
> > DelChild()
> > HandleEvent()
> > isDerivedFrom()
> > ClassObject()
> > Create()
> > Move()
> > SetEvent()
> > SetParent()
> > Destroy()
> > CurrentPos()
> >
> > And Member Vars:
> >
> > Quit
> > DisplayAll
> > Mode
> > Parent
> > Container
> > Center
> > Move
> > NoDither
> > UserColors
> > DefaultColor
> > Cargo
> > Owner
> > ShowHelp
> > Title
> > HelpRequest
> > Name
> >
> >
>

A good guess then.

The Class is undocumented so be careful. Someone found a XbpEditBrowse 
class (I think it was Joe Carrick), but it was broken.

Jim


Simon Burford, Uluru Support wrote:

> You are totally correct 
> 
> nResult:=oColorDialog:display()
> 
> returns the selected colour.
> Great stuff. Wonder what else has been added?!?
>

> A good guess then.
>
> The Class is undocumented so be careful. Someone found a XbpEditBrowse
> class (I think it was Joe Carrick), but it was broken.
>
> Jim
>

XbpEditBrowse sounds a bit like another interface to the browse system.
XbpColorDialog is just a link to a simple API routine, and I've been playing
with it with no ill effects so far.
Obviously I wouldn't use it in my finished app until documented, but given
that I can always fall back on calling the API directly if it ever gets
withdrawn or doesn't make it into Xbase 1.9, I think I'll use it in the
alpha versions as it seems to work ok.

Out of interest, how did XbpEditBrowse get found? Did someone poke around in
the .dlls looking for new stuff? If so, how?!?
I simply guessed XbpColorDialog based on a logical guess of what was still
missing

Simon

HI Simon,

It wasn't XbpEditBrowse but XbpQuickEditBrowse and someone else actually
mentioned it but I investigated and tested until I determined it had severe
problems.  I would not be at all surprised to find that the XbpColorDialog
class was also an attempt by Astag that had problems and was therefore never
released formally.

I had posted the MxColor Dialog a couple of years ago, so it might be that
Astag decided to do a know off - their way.  Sometimes they undermine the
3PP's so most of us have almost given up trying to provide commercial
add-ons.

It seems that the only things that actually sell to any extent are
commercial apps.  Some small utilities sell to the dev community but it's
not enough to make a living from.

-Joe

"Simon Burford, Uluru Support" <support@ulurudatabase.com> wrote in message
news:Hml5Uzk1DHA.2012@S15147418...
> > A good guess then.
> >
> > The Class is undocumented so be careful. Someone found a XbpEditBrowse
> > class (I think it was Joe Carrick), but it was broken.
> >
> > Jim
> >
>
> XbpEditBrowse sounds a bit like another interface to the browse system.
> XbpColorDialog is just a link to a simple API routine, and I've been
playing
> with it with no ill effects so far.
> Obviously I wouldn't use it in my finished app until documented, but given
> that I can always fall back on calling the API directly if it ever gets
> withdrawn or doesn't make it into Xbase 1.9, I think I'll use it in the
> alpha versions as it seems to work ok.
>
> Out of interest, how did XbpEditBrowse get found? Did someone poke around
in
> the .dlls looking for new stuff? If so, how?!?
> I simply guessed XbpColorDialog based on a logical guess of what was still
> missing
>
> Simon
>
>

BTW, I am almost ready to release my MxEditBrowse class for sale.  I will be
posting an app as a sample that is basically DBU for Windows on steroids.
The actual underlying class allows extreme control of fields, positions,
edit permissions, etc.  This is a major set of code but it makes setting up
a browse for editing a snap.

-Joe