Ermm... yes Visual Studio did mess the order of
parameters in .ODL file again ...:-(
Will fix it manually and post update.
Best regards, Tomasz Janeczko amibroker.com
----- Original Message -----
Sent: Thursday, June 30, 2005 10:44
PM
Subject: RE: [amibroker] AmiBroker 4.71.0
BETA released
TJ,
I'm getting
when
running AQ via an automation script that was already
working.
I've
got AQ vsn 1.71
and
AB vsn 4.71 beta
d
Hello,
Thanks! Next round of improvements will be
released in about 3 weeks.
Best regards, Tomasz
Janeczko amibroker.com ----- Original Message ----- From: "Joseph
Landry" <jelandry@xxxxxxxxxxxxx> To:
<amibroker@xxxxxxxxxxxxxxx> Sent: Thursday, June 30, 2005 10:17
PM Subject: Re: [amibroker] AmiBroker 4.71.0 BETA
released
> In American slang - "You da man!" Thanks
Tomasz, from > a quick screen of the change log it looks like
there > are many new items that will improve AB. Some improved >
usability in a small thing, like the toolbar wrap ( I > didn't know it
was a bug I thought it was a feature > (;> and I learned to live
with it.)..and Export Image > from OLE is a needed addition >
Best regards > JOE > --- Tomasz Janeczko
<amibroker@xxxxxx> wrote: > >>
Hello, >> >> A new beta version (4.71.0) of AmiBroker has
just >> been released. >> >> >> It is
available for registered users only from the >> members area
at: >> http://www.amibroker.com/members/bin/ab4710beta.exe >>
>> (File size: 758 574bytes, 758 KB) >> >> If
you forgot your user name / password to the >> members
area >> you can use automatic reminder service at: >> http://www.amibroker.com/login.html >>
>> The instructions are available below and in the >>
"ReadMe" file >> ( Help->Read Me menu from AmiBroker
) >> >> Best regards, >> Tomasz
Janeczko >> amibroker.com >> >> AmiBroker 4.71.0
Beta Read Me >> June 30, 2005 21:11 >> >> THIS
IS A BETA VERSION OF THE SOFTWARE. EXPECT BUGS >> !!! >>
>> Backup your data files and entire AmiBroker folder >>
first! >> IMPORTANT NOTE: This version uses new system
to >> store indicators (in separate files), so old >>
versions will not automatically "see" indicators >> created with
new version. >> >> INSTALLATION INSTRUCTIONS >>
>> IMPORTANT: This archive is update-only. You have to >>
install full version 4.70 first. >> >> Just run the
installer and follow the instructions. >> >> Then run
AmiBroker. You should see "AmiBroker 4.71.0 >> beta" written in the
About box. >> >> Many thanks to all providing detailed
descriptions >> how to reproduce given bug. >>
>> >> See CHANGE LOG below for detailed list of
changes. >> >> CHANGE LOG >> >>
CHANGES FOR VERSION 4.71.0 (as compared to 4.70.5) >>
>> a.. AFL: added GetCursorXPosition() and >>
GetCursorYPosition() functions >> >>
Functions return current mouse cursor position. >>
Values returned are equal to those visible in the >> status bar,
and these functions require status bar >> to be visible. Returned
values represent cursor >> position at the formula execution time
(or few >> milliseconds before it) and accurracy is subject
to >> pixel resolution of the screen (first cursor >>
position is read in screen pixels (integer) and then >> converted
to actual value therefore for example when >> screen resolution is
1024x768 maximum obtainable >> resolution in X direction is 0.1%
and in Y direction >> 0.13%), also X values are snap to datetime
of >> nearest data bar. >> >> It
only makes sense to use these functions in >>
indicator/interpretation code. >> >> Using
them in AA window may yield random >> values.GetCursorXPosition()
function returns X >> position in DateTime format (the same as used
by >> DateTime() function).You can convert it to string >>
using DateTimeToStr() function.GetCursorYPosition() >> returns Y
position (as displayed in Y axis of the >> chart). >>
>> Example: >> >>
>>
ToolTip="X="+DateTimeToStr(GetCursorXPosition()) >>
+"\nY="+GetCursorYPosition(); >> >>
>> >> b.. AFL: added DateTimeToStr() and
StrToDateTime() >> functions >> >>
These functions allow to convert string to >> datetime format and
vice versa. >> >> >>
Example: >> >>
ToolTip="X="+DateTimeToStr(GetCursorXPosition()) >>
+"\nY="+GetCursorYPosition();] >> >> c..
Added ability to store charts as .GIF (in >> addition to
PNG) >> >> >>
>> d.. ASCII importer maximum supported line
length >> is increased to 2048 characters >>
>> >> >> e..
Fixed: .aflsafe files didn't get deleted >>
automatically >> >> >>
>> f.. Added N-volume bars charts and
timeframe >> support. >> >> Custom
N-volume bar intervals are definable (as >> usual) in
Tools->Preferences->Intraday. >> >>
TimeFrame functions were also extended to support >> N-volume bars
using new TimeFrameMode() function >> calling >>
>> TimeFrameMode( 0 ); >>
>> - switches time frame functions to
time-based >> operation (the default) >>
>> TimeFrameMode( 1 ); >>
>> - switches time frame functions to
N-tick >> operation (positive values passed to
TimeFrameSet >> are treated now as N-tick) >>
>> TimeFrameMode( 2 ); >>
>> - switches time frame functions to N-volume
bar >> operation (positive values passed to
TimeFrameSet >> are treated nowas N-volme bars) >>
>> Example: >> >>
TimeFrameMode( 2 ); >> TimeFrameSet( 50000 ); // 50'000
share bars.. >> ...do something
... >> TimeFrameRestore(); >> >>
>> Note: N-volume bars are somewhat weird >>
(compression of data to N-volume bar may actually >> deliver MORE
output bars - for example if one tick >> is 1000 shares and you
have specified 100V bars then >> single tick will be expanded to
TEN 100V bars - ten >> times original size) >>
TimeFrame functions are protected against array >> overrun and will
not decompress beyond original >> array size (you will get an
"Error 47. N-volume bar >> compressed data longer than base time
frame"). >> Also switching main time frame to some
weird >> N-volume bar value will result in limiting the >>
output to maximum twice original data size(without >> error
message). >> You should keep that in mind and avoid
using too >> small N-volume bar intervals that could lead to
such >> condition. >> Also due to the nature
of N-volume bars the only >> TimeFrameSet() function will yield
correct N-volume >> bar values, TimeFrameGetPrice() may give
slightly >> distorted results. >> It is also
possible to use n-volume bars in >> TimeFrame functions without
calling TimeFrameMode() >> - it is then necessary to specify
n-volume bars as >> negative number offset by -1000000 (minus
one >> million): >> >> TimeFrameSet(
-1000000 - 2000 ); >> >> // gives 2000V
barsSimilarly formatted negative >> numbers will be reported by
Interval() function when >> n-volume bars are selected. >>
>> >> >> >> g.. OLE:
Save As PNG / GIF callable from >> automation >>
>> Example script: >>
>> AB = new
ActiveXObject("Broker.Application"); >>
AB.ActiveWindow.ExportImage("Test.png"); >>
>> h.. Plugin is not called when GetExtraData is
used >> for > === message truncated === > >
> > Please note that this group is for discussion between
users only. > > To get support from AmiBroker please send an
e-mail directly to > SUPPORT {at} amibroker.com > > For
other support material please check also: > http://www.amibroker.com/support.html >
> > Yahoo! Groups Links > > > >
> > >
Please note that this group
is for discussion between users only.
To get support from AmiBroker
please send an e-mail directly to SUPPORT {at} amibroker.com
For
other support material please check also: http://www.amibroker.com/support.html
---- LSpots keywords ?>---- HM ADS ?>
Please
note that this group is for discussion between users only.
To get
support from AmiBroker please send an e-mail directly to SUPPORT {at}
amibroker.com
For other support material please check also: http://www.amibroker.com/support.html
---- LSpots keywords ?>---- HM ADS ?>
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For other support material please check also:
http://www.amibroker.com/support.html
---- LSpots keywords ?>
---- HM ADS ?>
YAHOO! GROUPS LINKS
|