Re: [Harbour] GT without Text Bufer : Feature Request

2008-11-17 Thread Pritpal Bedi

Hi Przemek

Please ignore this request. I have discovered how to.

Regards
Pritpal Bedi

-- 
View this message in context: 
http://www.nabble.com/GT-without-Text-Bufer-%3A-Feature-Request-tp20526548p20534771.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] 2008-11-16 23:22 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED])

2008-11-17 Thread Pritpal Bedi

2008-11-16 23:22 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED])
  * harbour/contrib/gtwvg/gtwvg.c
! Resizing: some recent changes reverted back.
; TODO: reversal in GTWVT also. It breaks some pre-initialization
issues.

  * harbour/contrib/gtwvg/wvgax.prg
! Better detection if COM object fails to be created.

  + harbour/contrib/gtwvg/wvggui.c
  + harbour/contrib/gtwvg/wvggui.h
+ Initial commit of pure GUI GT based on GTWVG named WGU.
  ; Subject to heavy changes onwards.
WGU will become the basis of WvgDialog() plus inherited 
sub-classes.

  * harbour/contrib/gtwvg/makefile
  * harbour/contrib/gtwvg/common.mak
+ Added new files.

  * harbour/contrib/gtwvg/tests/demowvg.prg
+ Now  is working properly. 
  It now opens in new thread if it is odd and as usual if even.
+ 
  ! Just to have experiments on WGU GT.

Regards
Pritpal Bedi
-- 
View this message in context: 
http://www.nabble.com/2008-11-16-23%3A22-UTC-0800-Pritpal-Bedi-%28pritpal%40vouchcac.com%29-tp20535315p20535315.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


RE: [Harbour] GT without Text Bufer : Feature Request

2008-11-17 Thread Massimo Belgrano
Hi Pritpal 

Can you show few lines of code how I can inherit from GTWVG with only
one method overloaded in new GT ( say 'WGU' )?
Will be usefull for other people that search reply to same question

Regards
Belgrano Massimo

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pritpal Bedi
Sent: Monday, November 17, 2008 8:19 AM
To: harbour@harbour-project.org
Subject: Re: [Harbour] GT without Text Bufer : Feature Request


Hi Przemek

Please ignore this request. I have discovered how to.

Regards
Pritpal Bedi

-- 
View this message in context:
http://www.nabble.com/GT-without-Text-Bufer-%3A-Feature-Request-tp205265
48p20534771.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


RE: [Harbour] 2008-11-16 23:22 UTC-0800 Pritpal Bedi([EMAIL PROTECTED])

2008-11-17 Thread Massimo Belgrano
A little suggestion for harbour/contrib/gtwvg/tests/demowvg.prg
 
Have problem after resize more big mail screen (why resize main screen
conditions child screen)
In Two browsing you can use mouse wheel to scroll record  and not click
for select record as usual in gui

Regards
Pritpal Bedi
-- 
View this message in context:
http://www.nabble.com/2008-11-16-23%3A22-UTC-0800-Pritpal-Bedi-%28pritpa
l%40vouchcac.com%29-tp20535315p20535315.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] FW: [Harbour-users] Mac OS 10.5.5 "dyld: Library not loaded:libharbour.1.dylib"

2008-11-17 Thread Massimo Belgrano
Will one of mac OS user give a reply on user list?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, November 14, 2008 2:08 PM
To: [EMAIL PROTECTED]
Subject: [Harbour-users] Mac OS 10.5.5 "dyld: Library not
loaded:libharbour.1.dylib"

Hello,

I have just downloaded the Mac OS binary 1.0.1.

After I copied the files to /usr/ and /private, I tried running a  
sample program:

jan$ hbrun helloworld.prg

and got the following error:
dyld: Library not loaded: libharbour.1.dylib
   Referenced from: /usr/local/bin/hbrun
   Reason: image not found
Trace/BPT trap

Is there anything else I have to do to load the library?

Thanks a lot for your help

Jan
___
Harbour-users mailing list
[EMAIL PROTECTED]
http://lists.harbour-project.org/mailman/listinfo/harbour-users
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


RE: [Harbour] 2008-11-16 23:22 UTC-0800 PritpalBedi([EMAIL PROTECTED])

2008-11-17 Thread Massimo Belgrano
Another suggestion
Att to demowvg http:address where download component active x

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Massimo
Belgrano
Sent: Monday, November 17, 2008 12:09 PM
To: Harbour Project Main Developer List.
Subject: RE: [Harbour] 2008-11-16 23:22 UTC-0800
PritpalBedi([EMAIL PROTECTED])

A little suggestion for harbour/contrib/gtwvg/tests/demowvg.prg
 
Have problem after resize more big mail screen (why resize main screen
conditions child screen)
In Two browsing you can use mouse wheel to scroll record  and not click
for select record as usual in gui


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] Are this information applicable also to harbour?

2008-11-17 Thread Massimo Belgrano
Are this information applicable also to harbour?
ftp://ftp.alaska-software.com/documents/oop-6-rules.pdf

„Class“ is an abstract term. The Xbase++ runtime knows class object and instance
objects. Class objects are created at the first time the class
function is executed, subsequent class function execution returns the same class
object.
To „free“ a class object the function ClassDestroy() can be used. The Xbase++
runtime has a process-global hashtable used to associate class objects with
class names.
ClassDestroy() simply removes the name<->class object
association. However the class object is not freed until the last
instance object of this class is destroyed.
:New() is the default constructor to create instance objects. Instance objects
are always created by class objects.
Therefore class objects are sometimes called „Object
Factories“. You can have an unlimited amount instance objects
of the same class. In the following the term object is used to
describe instance objects.

Note: Class objects which reference code or data of a DLL lead to sideeffects
such as that the DLL is not unloadable until all objects of the class are
destroyed and the class object itself has been destroyed. Until this
precondition is met the DLL can not be unloaded.

All class are dynamyc
There is no difference between a class object created from a class function A()
generated by the
compiler and a class object created with
CreateClass() by a Function A().
Runtime-classes can replace compile-time classes
and vice versa. Any class can be replaced by
another class with the same name. That‘s why
classes are dynamic.
The FREEZE attribute at CLASS declaration
prohibits the implicit replacement of this class.
FREEZE can be used to protect class
implementations from being replaced implicitly.
The FINAL attribute prohibits subclassing of this
class. The behaviour of FINAL classes can therefore be no longer changed -It is
FINAL

Consider the code on the right side:
Executing the method :Bark() on
objects of Class A executes method
:Print() at Class A. Executing the
method :Bark() on objects of Class B
executes the method :Print()
implemented at Class B.
This behaviour is called virtual override
because each method implementation
in a subclass does override a possible
implementation of its superclasses
- Overriding of METHOD is always a replacement
method replacement totally overwrites the
method of its base classes during execution. That is the code in the base class
is never executed when instances of subclasses are manipulated. The
Class B and the method :Print() is an example of
method replacement.
Refinement can be achieved as outlined in Class C. To do that, we must be able
to execute the
superclass implementation. The SUPER statement
is used to refer to the direct superclass
implementation. The SUPER statement executes the superclass implementation of
the current
method and passes all parameters passed to this
method. SUPER:Print() can be used as an
alternative to control method name and
parameters passed.
Note: You can write SELF:A:

Consider the code on the right side:
Executing the method :PrintA() on
objects of Class B prints „Value from A“,
while executing the method :PrintB()
shows „Value from B“.
This behaviour is called hiding in OO
terms. It simple means that redefining
a variable in a subclass hides the
variable of its superclass. It therefore
introduces the variable.

CLASS A
EXPORTED:
VAR Lastname
INLINE METHOD Init()
::LastName:= „ValuefromA“
RETURN
INLINE METHOD PrintA()
? ::LastName
RETURN
ENDCLASS
CLASS B FROM A
EXPORTED:
VAR Lastname
INLINE METHOD Init()
::A:Init()
::LastName:= „ValuefromB“
RETURN
INLINE METHOD PrintB()
? ::LastName
RETURN
ENDCLASS


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] OSX (and Linux) and dyn libs

2008-11-17 Thread Szakáts Viktor

To the OSX problem (which doesn't appeared on my mailbox,
only the web archive):

just copy the missing file from /lib to next to the executable,
and always use -static when using hbmk script.

BTW, I think we should rename the dynamic builds of our
supplied binaries to hbrun-dyn and hbtest-dyn, similarly
to Windows, and leave hbrun and hbtest to run standalone.
I mean this for both Linux and OS X, as the benefits of
these being built with dynamic libs is rather small, but
it can be a major PITA when someone is trying to run them
without installing Harbour (say they want to play with it
only, and/or they have multiple versions installed). For
OS X I'd also change the hbmk default to '-static'.

Anyone is welcome with more opinions on above.

Brgds,
Viktor

On 2008.11.17., at 17:09, Massimo Belgrano wrote:


Another suggestion
Att to demowvg http:address where download component active x

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Massimo
Belgrano
Sent: Monday, November 17, 2008 12:09 PM
To: Harbour Project Main Developer List.
Subject: RE: [Harbour] 2008-11-16 23:22 UTC-0800
PritpalBedi([EMAIL PROTECTED])

A little suggestion for harbour/contrib/gtwvg/tests/demowvg.prg

Have problem after resize more big mail screen (why resize main screen
conditions child screen)
In Two browsing you can use mouse wheel to scroll record  and not  
click

for select record as usual in gui


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] FW: [Harbour-users] Filestats of xHarbour

2008-11-17 Thread Massimo Belgrano
Harbour have not ported filestat function ?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 6:18 PM
To: [EMAIL PROTECTED]
Subject: [Harbour-users] Filestats of xHarbour

Hi!
What is equivalent function ?

As subject.

TIA,
Itamar M. Lins Jr.

xHarbour Language Reference Guide (Version 1.1) - FileStats()FileStats()

Retrieves file information for a single file.
Syntax

FileStats( , ;
  [@]  , ;
  [@]  , ;
  [@], ;
  [@], ;
  [@], ;
  [@]  ) --> lSuccess

Arguments ** This is a character string holding the name of
the
file to query. It must include path and file extension. If the path is
omitted from **, the file is searched in the current
directory. @
** If specified, ** must be passed by reference.
It
receives the file attributes of the file as a character string. @*
* If specified, ** must be passed by reference. It
receives the file size of the file as a numeric value. @**
If
specified, ** must be passed by reference. It receives the
creation date of the file as a date value. @** If
specified, *
* must be passed by reference. It receives the creation
time of
the file as a numeric value. The unit is "seconds elapsed since
midnight".
Use function TString()  to convert this value to a
"hh:mm:ss" formatted time string. @** If specified, *
* must be passed by reference. It receives the last change
date
of the file as a date value. @** If specified,
**must be passed by reference. It receives the creation
time of the file as a
numeric value. The unit is "seconds elapsed since midnight". Return

The return value is .T. (true) when the information on the file
*
* could be retrieved, otherwise .F. (false) is returned.
Description

Function FileStats() retrieves statistical information about a single
file.
It is more efficient than the Directory()  function
which retrieves the same information for a group of files and stores
them in
an array. FileStats(), in contrast, allows for "picking" desired
information
about a single file by passing the according parameters by reference to
the
function.
Info

  See also: Directory() , FCreate()
,
HB_FSize()  Category: File
functions<../../Grp_file_functions.en.html>, Low
level file functions <../../Grp_low_level_file_functions.en.html> ,
xHarbour
extensions <../../Grp_xharbour_extensions.en.html> Source:
rtl\filestat.c
LIB: xhb.lib DLL: xhbdll.dll
Example

// The example shows how to retrieve statistical information about
// a single file, and how to convert the time values from Seconds
// to a hh:mm:ss time formatted string.

   PROCEDURE Main
  LOCAL cFileName := "FILESTATS.PRG"
  LOCAL cFileAttr  , nFileSize
  LOCAL dCreateDate, nCreateTime
  LOCAL dChangeDate, nChangeTime

  ? FileStats( cFileName, @cFileAttr  , @nFileSize  , ;
  @dCreateDate, @nCreateTime, ;
  @dChangeDate, @nChangeTime  )

  ? "File statistiscs"
  ? "File Name :", cFileName
  ? "Attributes:", cFileAttr
  ? "File Size :", nFileSize
  ? "Created   :", dCreateDate, TString( nCreateTime )
  ? "Changed   :", dChangeDate, TSTring( nChangeTime )
   RETURN
___
Harbour-users mailing list
[EMAIL PROTECTED]
http://lists.harbour-project.org/mailman/listinfo/harbour-users
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] OSX (and Linux) and dyn libs

2008-11-17 Thread Przemyslaw Czerpak
On Mon, 17 Nov 2008, Szak�ts Viktor wrote:

Hi Viktor,

> just copy the missing file from /lib to next to the executable,
> and always use -static when using hbmk script.

Why??? In all *nixes dynamic linking is a base and static
is sth seldom used for some specific reasons.

If there is sth wrong with default harbour shared library name
or location in harbour-*.tar.gz then of course it should be fixed.

> BTW, I think we should rename the dynamic builds of our
> supplied binaries to hbrun-dyn and hbtest-dyn, similarly
> to Windows, and leave hbrun and hbtest to run standalone.

Please do not make anything like that. If you want to unify
the names then I suggest to remove static binaries from Windows
builds or call them as *-static.exe.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] OSX (and Linux) and dyn libs

2008-11-17 Thread Szakáts Viktor

Hi Przemek,


just copy the missing file from /lib to next to the executable,
and always use -static when using hbmk script.


Why??? In all *nixes dynamic linking is a base and static
is sth seldom used for some specific reasons.


Because in OS X such experience is simply unprecedented
in the user world, and because it gives _no_ advantage
_at all_ on this platform, which is 99.99% aimed for desktop
users. At the same time it makes the binaries simply unusable,
and broken out of the box. So, I'm not exactly sure this is what
users expect on this platform, at least I haven't heard of
any such Mac users in the last 5 years. In fact 99% of them
doesn't want to or have to know that there is such thing
as a .dylib, and I'm pretty sure they won't want to learn just
to run a Harbour based app.

And I believe it's completely wrong to require installation,
sudo/admin rights and all that crap to just make it possible
to _try Harbour_, or run a simple "hello world", or god
forbid have 2 versions installed in parallel (which is not
something exceptional for a developer). Let alone work with
a _portable_ environment. No, we rather save 1.5MB on disk
(or we target server-side users? hard to tell.).

Pls tell some advantages this gives, so far you seemed
to have just ignored any points raised in this regard. It'd
be really nice to know the reasons why you insist on this
shared/dynamic/dll thing on all platforms.

Also, what if I'd like to just copy my Harbour devl env to
an USB drive and move it around to another machine? This isn't
possible with Linux either, thanks to the shared feature, and
install-time hard wired lib path tricks.


If there is sth wrong with default harbour shared library name
or location in harbour-*.tar.gz then of course it should be fixed.


There is something definitely wrong, since it doesn't work,
and it never did.


BTW, I think we should rename the dynamic builds of our
supplied binaries to hbrun-dyn and hbtest-dyn, similarly
to Windows, and leave hbrun and hbtest to run standalone.


Please do not make anything like that. If you want to unify
the names then I suggest to remove static binaries from Windows
builds or call them as *-static.exe.


Have you ever seen such thing on Windows? BTW, I haven't
seen too many programs on Windows in the form of *-dll.exe
either. On Windows - nowadays maybe except the Cygwin world
of horror -, apps are expected to just run with as few .dll
dependencies as possible. All of those are just a way to
make programs get screwed on some environments.

All in all OS X and Windows is not Linux, and there is no
point in forcing Linux standards onto them IMO.

Brgds,
Viktor

[ BTW and slightly off, both Linux and Windows could take long
lessons from OS X when it comes to _desktop software_ installation,
those other two simply cannot get it right. I had to fall back
and recommend XP over Linux on Asus EEE PC, because custom software
installation (= Google Earth and say a bittorrent client) is just
way too difficult - if possible - for an average user on Linux.
No wonder it still couldn't catch up. ]

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] 2008-11-18 01:36 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)

2008-11-17 Thread Przemyslaw Czerpak
2008-11-18 01:36 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
  * harbour/make_gcc.sh
  * harbour/make_gcc.mak
! fixed GCC builds broken by modifications in common.mak

best regards
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] OSX (and Linux) and dyn libs

2008-11-17 Thread Przemyslaw Czerpak
On Tue, 18 Nov 2008, Szak�ts Viktor wrote:

Hi Viktor,

> Because in OS X such experience is simply unprecedented
> in the user world, and because it gives _no_ advantage
> _at all_ on this platform, which is 99.99% aimed for desktop
> users. At the same time it makes the binaries simply unusable,
> and broken out of the box. So, I'm not exactly sure this is what
> users expect on this platform, at least I haven't heard of
> any such Mac users in the last 5 years. In fact 99% of them
> doesn't want to or have to know that there is such thing
> as a .dylib, and I'm pretty sure they won't want to learn just
> to run a Harbour based app.

I see only one problem. So far no one invest time to create
native MacOSX packages which will put Harbour binaries and
libraries in the OS friendly directories using OS packaging
system.
All of the above what you said is only results of such missing
functionality which you mixed with your personal preferences
from DOS/Windows.

> And I believe it's completely wrong to require installation,
> sudo/admin rights and all that crap to just make it possible
> to _try Harbour_, or run a simple "hello world", or god
> forbid have 2 versions installed in parallel (which is not
> something exceptional for a developer). Let alone work with
> a _portable_ environment. No, we rather save 1.5MB on disk
> (or we target server-side users? hard to tell.).

I believe that any manual installation which does not use
OS support is wrong and farther workarounds only makes it
worse.

> Pls tell some advantages this gives, so far you seemed
> to have just ignored any points raised in this regard. It'd
> be really nice to know the reasons why you insist on this
> shared/dynamic/dll thing on all platforms.

Because shared linking it's a basic requirement in most of
open source OS distributions and without it Harbour will never
be accepted as default package in them. I do not want to create
Harbour binaries to the end of my days and I hope to see in the
future Harbour part of all most popular OS *nixes distribution.
In current days real static linking stop to be possible in
many systems and number of static libraries is systematically
reduced. I do not like it sometimes because still there are
situations when full static binaries are usable but I understand
the reasons. When bug is found in some library then it's enough
to upgrade this library instead of all binaries which may use
this static library.
Shared libraries for Harbour programmers may give yet another feature
when it's not possible to create fully static binaries for some
libraries, f.e. try to create sth like that for xWindow. When final
user application compiled by Harbour is linked with Harbour shared
library then it should be possible to install it with any
other libraries located with system if only Harbour is recompiled
for this OS. I plan to extend it because static linking begins
to be real show stopper in software distribution.
Without it I will have to recompile my applications for user
host. I do not like such improvement ;-)

> Also, what if I'd like to just copy my Harbour devl env to
> an USB drive and move it around to another machine? This isn't
> possible with Linux either, thanks to the shared feature, and
> install-time hard wired lib path tricks.

It's possible. It's enough to read one man page and resolve it
in few possible ways depending on your personal preferences.
And if we drop the ideas with making everything static it will
be much easier because Harbour may become part of default OS
distributions.
Now it's not a problem for users who used to install OS friendly
packages with Harbour binaries like RPM or DEB.

>> If there is sth wrong with default harbour shared library name
>> or location in harbour-*.tar.gz then of course it should be fixed.
> There is something definitely wrong, since it doesn't work,
> and it never did.

???
Viktor if you do not understand sth then its not a reason to
remove it from Harbour.

Lorenzo can you explain how you are able to use shared libraries
in MacOSX.
You and Viktor are using MacOSX. Can you try to create native MacOSX
Harbour packages which will put all libraries in all expected
places?

>> Please do not make anything like that. If you want to unify
>> the names then I suggest to remove static binaries from Windows
>> builds or call them as *-static.exe.
> Have you ever seen such thing on Windows? BTW, I haven't
> seen too many programs on Windows in the form of *-dll.exe
> either. On Windows - nowadays maybe except the Cygwin world
> of horror -, apps are expected to just run with as few .dll
> dependencies as possible. All of those are just a way to
> make programs get screwed on some environments.

I hoped that you will find it as heretic idea for windows world.
I'm finding your ideas in such way.
BTW AFAIR with MSVC is not possible to create static binaries
and they always depend on MSVC CRTL DLLs which has to be install
in compatible version in Windows or you should distr

[Harbour] 2008-11-18 02:53 UTC+0100 Viktor Szakats (harbour.01 syenar hu)

2008-11-17 Thread Szakáts Viktor
2008-11-18 02:53 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
  * source/rtl/gtwvt/gtwvt.c
! Fix to previous fix to maximize the window when the initial 
  size would be too big to fit on screen (stupid omission).
  Now the previously cited sizing problem is alright.

  * source/vm/fm.c
+ Replaced HB_NO_FM_STAT and HB_FM_STAT envvars 
  with HB_FM_STAT=yes|no (maybe 0|1 or on|off woud be 
  better or could be accepted as alternatives or 
  replacement). This is to avoid ambiguity when both 
  envvars were set or the app default is not known.
+ Added HB_FM_STATISTICS_DYN_OFF to turn off mem tracking 
  by default when stat module is linked in.

  * source/common/hbverdsp.c
* Minor cosmetic.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] 2008-11-18 03:04 UTC+0100 Viktor Szakats (harbour.01 syenar hu)

2008-11-17 Thread Szakáts Viktor
2008-11-18 03:04 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
  * ChangeLog
* Two recent TODOs in entries marked as [DONE] by this change:
  2008-11-18 01:36 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
  (It was "broken" due to enhancements, see the TODOs. Thanks anyway.)
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour