Hallo,

aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich aber 
hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage 
ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte 
"continous delivery" hat kaum etwas gebracht.

Wahrscheinlich ist es günstiger, das in nächste Update dann einfach 
wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...


Markus

Hallo Markus,

ich habe heute meinen "ich lese mal quer" Tag ...
So bin ich über diese Frage gestolpert.

Ich gestehe, dass mich diese Frage und auch die Ausführungen hier 
ärgern. Ich will nicht über die Sinnhaftigkeit von einer 
Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.

Aber
 > Auch das mit 2.0 eingeführte
 > "continous delivery" hat kaum etwas gebracht.
ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19 
Updates veröffentlicht. Und das ist "kaum etwas gebracht"?

In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.

 > Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
 > wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend ist 
mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem Windows 
Aniversary Update "nur" in einem Update ohne Versionssprung 
veröffentlicht. Andere Firmen machen daraus neue Versionen.

Wie dem auch sei, ich habe mir erlaubt deine Registrierungen anzuschauen 
und das hast bisher versäumt: siehe unten.

Das hast du alles verpasst.

Gruß, Frank


Build 2.00.779 (closed workitems)
New features Add function DbDestroy() to the data-definition-language 
(DDL) to delete an ISAM emulating table programmatically by the 
underlying DatabaseEngine. (xpprt1.dll) (W16CWL)

Fixes/Changes Correct the calculation of the the column widths of the 
grids displayed in the debugger's auxilliary views. These may become 
smaller as the views get refreshed in a debugging session. 
(xppworkbench.exe) (W16CTU) (PDR6868)

  Correct debugger issue where debugging codeblocks and inspecting 
variable values crashes the client application and/or the debugger. 
(xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)

  Correct the Xbase++ debugger kernel so that breakpoints set in a 
calling context halt the debuggee after the STEP BACK (step out) command 
is used. (xppdbgk.dll) (W16CWG) (PDR6865)

  Resolve issue where a replace operation may force a runtime error 
right after an append in exclusive mode of the PostgreSQL ISAM 
emulation. (pgdbe.dll) (W16CWJ) (PDR6840)

  Ensure that DllExecuteCall() allows NIL to signal NULL for all 
reference parameter types. If passed by value, only character, object 
and codeblock must support NIL to signal no input value. (xpprt1.dll) 
(W16CWQ) (PDR6864)

  Correct the STEP BACK (step out) command of the Xbase++ debugger so 
that execution halts in the current context if the context was called 
recursively. Currently, the debuggee is halted only after the recursion 
has completed. (xppdbgk.dll) (W16CWR) (PDR6866)

  Correct the debugger kernel so that a "step into" command stops the 
debuggee in the calling function or method if the current line contains 
a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)

  Correct the callstack view in the Workbench debugger so that the 
current context (callstack level) is indicated correctly, even when 
debugging a function that is calling itself recursively. 
(xppworkbench.exe) (W17CW1) (PDR6869)

  Correct the "step over" debugger command so that execution indeed 
stops after the current line when the cursor is on a line calling the 
current procedure recursively. Currently, the "step over" command 
behaves as if "step into" was executed, and execution stops in the first 
line of the current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)

  Fix race condition due to statement leak which leads the PostgreSQL 
server to hang. (pgdbe.dll) (W17CX1) (PDR6625)

  Resolve issues where a filter condition may lead to a runtime error 
when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll) 
(W17CX2) (PDR6622)

  Correct the XbpTreeView class so that tree view items can be 
manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)

  Add a class method :setBehavior() to the XbpBrowse class to allow 
configuring the navigational behavior of all browse objects. 
(xppdui.dll) (W17CXH) (PDR6873)

  Resolve IDSC or stall with 1-digit port in connection string of 
PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ) (PDR6861)

  Resolve issue with runtime error on PACK using PostgreSQL ISAM 
emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)

  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit 
test. (pgdbe.dll) (W17CXL) (PDR6848)

  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll) 
(W17CXN) (PDR6847)

  Resolve issue with empty resultsets and invalid EOF() and Found() 
states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)

  Fix issue with default precision handling for aggregate results. Add 
unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ) 
(PDR6824)

  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL 
ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)

  Resolve issue with wrong record number in empty workarea if all 
records get filtered out by the FOR expression of the current order. 
Extend unit test. (pgdbe.dll) (W17CXS) (PDR6818)

  Resolve issues where OrdListRebuild() may run into an internal error 
with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)

  Fix the issue where creating an index with same name as an open index 
yields error while the PGDBE is trying to update the seek procedure. 
Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)

  Correct the PostgreSQL documentation regarding the numeric precision 
and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)

  Resolve the issues where adding an index tag to an existing bag leads 
to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX) (PDR6801)

  Resolve issues where SELECT Max(<charfield>) yields incorrect results 
with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)

  Ensure the debugger tool tips are displayed correctly when using the 
"Adjust the size of text and other display items" system option under 
Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)

  Investigate and fix the issue in the Xbase++ Workbench which sometimes 
causes an error message to appear ("canvas drawing error") when building 
or debugging an application. (xppworkbench.exe) (W16CTK)

  Correct the example code in the "Using northwind programmatically" 
programming guide chapter in the PGDBE documentation: the session object 
used with an SQL SELECT must be specified in parentheses. (*.chm) (W16CTR)

  Output a warning when attempting to load executables containing name 
tokens such as "install" or "setup" into the debugger. This is required 
as Windows handles executables with these names differently and may not 
allow debugging. (xppworkbench.exe) (W16CUR)

  Correct product sample readme files to conform to the specifications 
regarding content and format. (samples) (W16CWP)

  Reduce flicker in the context windows of the debugger when stepping 
through the code. The callstack window, for example, flickers 
excessively when the callstack is large. (xppworkbench.exe) (W17CWW)

  Ensure xppdui.dll is exported to the \runtime folder by the local 
makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from 
the runtime folder of the installed product. (*.msi) (W17CWY)






Build 2.00.769 (closed workitems)
New features Maintain asac.log in the users documents\xbase++\.logs 
folder. (xppworkbench.exe) (W16CTQ)

  Ensure that all datatypes from types.ch are properly supported by the 
USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)

  Add readme to the styled combo box example for the XbpHTMLStyle class 
to describe the rationale behind the sample. (samples) (W16CU7)

  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to 
ensure that called code is not affecting FPU status of the Xbase++ 
application. (xpprt1.dll) (W16CUB)

Fixes/Changes Investigate and resolve issue why halting a running 
debuggee (CTRL+S) takes such a long time to complete under Windows 10 
Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)

  Correct runtime FPU control word management so that calls to 
misbehaving API or printer driver code does not affect rounding 
behavior. (xpprt1.dll) (W16CT1) (PDR6678)

  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be 
operated with the finger, even after tapping the data area of the 
browse. (xppdui.dll) (W16CT3) (PDR6822)

  Correct the XbpQuickBrowse class so that it works correctly with a 
top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)

  Correct the XbpToolBar class so that no runtime error occurs when the 
first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)

  Add code to the XbpPrinter for ensuring that the current FPU settings 
are reset after communicating with a printer driver. (xppui1.dll) 
(W16CTX) (PDR6854)

  Correct the XbpHTMLStyle class so that the output is positioned 
correctly when used in conjunction with the XbpComboBox class. 
(xppwui.dll) (W16CU2) (PDR6860)

  Correct the issue in the Workbench debugger which may cause runtime 
errors in the IDE after resuming the client application after stopping 
at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)

  Correct the Workbench debugger so that executables can be debugged 
which reside in a path containing Umlaut characters (xppworkbench.exe) 
(W16CUH) (PDR6639)

  Fix SQLite type affinity related PDR 6855. Extend the existing test 
suite to ensure correct behaviour according to SQLite spec./doc. 
(asrdbc10.dll) (W16CUJ) (PDR6855)

  Resolve issue where SQL SELECT operations against local tables may 
cause a runtime error (internal datastructures corrupted) (adac20b.dll) 
(W16CUK) (PDR6762)

  The header files in the auto-dependency section must be normalized 
relative to the target. (pbuild.exe) (W16CUL) (PDR6851)

  Resolve DACSqlStatement: No instances allowed for this class error and 
extend the test suite to cover USQL with ADSDBE also. (adsutil.dll) 
(W16CUQ) (PDR6815)

  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY) 
(PDR6757)

  Ensure strings used with HTML/CSS-based Xbase Parts such as 
XbpCommandButton are converted to ANSI when the application uses an OEM 
charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U) (PDR6712)

  Remove the commandline switch /rc from the resource compiler 
executable and documentation. (arc.exe) (W16CT2)

  Validate for the correct interface when a XmlMapper is passed as 
second parameter to Var2Xml() (xpprt2.dll) (W16CTW)

  Correct the source code sample in the chapter "Programmatic reference 
- dbfupsize.dll" (pg20.chm) (W16CUA)

  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional 
array for fieldcount 1 - N and an empty array for an empty result set. 
Review related unit-tests. (asrdbc10.dll) (W16CUS)

  Review USQL unit tests with respect to the revised type system and 
ensure that the core types are properly validated. (adac20b.dll) (W16CUX)





Build 2.00.762 (closed workitems)
New features Add alternative interfaces for loading images used in the 
HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be 
Base64-encoded and defined via a :data URI scheme. (xppwui.dll) (W16CJT)

  Ensure the project manager restores the collapse/expand state. 
(xppworkbench.exe) (W16CND)

  Extend Workbench pre-defined macros to support all directories from 
the "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)

  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types. 
Extend the unit-test to cover the entire range of possible values as 
parameter, reference parameter and return value. (xpprt1.dll) (W16CNR)

  Add a function BinaryName() to identify the execution context. The 
function returns the name of the binary (exe or dll) executing the 
function. (xpprt1.dll) (W16CNX)

  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the 
unit-test to cover the entire range of possible values as parameter, 
reference parameter and return value. (xpprt1.dll) (W16CPK)

  Add a control for indicating busy state to the Xbase++ Workbench. 
(xppworkbench.exe) (W16CQB)

  The workbench must maintain logfiles in the user's documents folder 
under Xbase++\.logs. The folder Xbase++\logs becomes obsolete. 
(xppworkbench.exe) (W16CRW)

  Add optional feature "Asset Repository" to the installation package. 
The feature is a child of "Xbase++ 2.0 for windows". Installation is 
done to the users documents folder "Xbase++\.assets". (xpp*.msi) (W16CH3)

Fixes/Changes Add a resource setting to configure round() behavior 
according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)

  Ensure that mails containing a line starting with a dot are send 
completly instead of as a fragment by the SmtpClient class. See PDR 
6823. (asinet10.dll) (W16CNT) (PDR6823)

  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN 
presentation parameter when computing the position of the header and 
footer elements. (xppdui.dll) (W16CPJ) (PDR6828)

  Fix handle leak in PGDBE when performing SELECT queries and extend the 
unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1) 
(PDR6834)

  Highlight new content in the documentation using the color dark red. 
(xppref.css) (W16CJR)

  Ensure the XbpImageListBox control conforms to our coding style. 
(asset) (W16CL2)

  Ensure that asget writes error messages to stdout. This enables the 
workbench to display the error message. (asget.exe) (W16CL7)

  Extend exisiting Workbench template mechanism in such a way that new 
templates can be easily added by the user (xppworkbench.exe) (W16CL9)

  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and 
associated files conform to our coding style. (asset) (W16CLC)

  Ensure XbpHTMLStatic class and associated code conform to our coding 
style. (asset) (W16CLH)

  Ensure the XbpCommandButton class and related files conform to our 
coding style. (asset) (W16CLJ)

  Ensure the XbpCheckedListBox class and related files conform to our 
coding style. (asset) (W16CN1)

  Ensure the dialog for managing target-specific assets remembers its 
current size and position, as well as splitbar position. 
(xppworkbench.exe) (W16CN2)

  Ensure the "New Items" dialog remembers its current size and position 
(xppworkbench.exe) (W16CN3)

  Create and add import definition for VFP modernizer to Workbench 
(xppworkbench.exe) (W16CNC)

  Change "New items" dialog so that the view style (large icons etc.) is 
restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)

  Modify the event management sample in the CXP sample collection so 
that it uses the POST verb for transferring data, eg. when saving 
events. (alaska-software.webui.js) (W16CP1)

  Add a static/non-collapsible panel class to the XbpPanelContainer 
control. (asset) (W16CP4)

  Extend the styled list box example for the XbpHTMLStyle class so that 
it better illustrates the usage of the WebUI for customizing an existing 
Xbase Part. (samples) (W16CP7)

  Ensure the XbpToggleButton class and related files conform to our 
coding style. (asset) (W16CPA)

  Correct the htmlhelp.exe example so that it displays context-sensitive 
help when pressing the F1 key. (htmlhelp.exe) (W16CPC)

  Ensure the new project manager target nodes are expanded by default. 
(xwbassochlp20.dll) (W16CPD)

  Reorganize the closed workitems list in such a way that new features 
and changes are shown first followed by the list of fixes/corrections 
(changes20.chm) (W16CPL)

  Ensure that ALINK is able to handle long import library names 
identical in the first 16 chars. (alink.exe) (W16CPQ)

  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that, 
the XbpColumn class init state needs to be independent from module init 
state. (xppdui.dll) (W16CPY)

  Use global busy indicator when build is in progress. 
(xppworkbench.exe) (W16CQ1)

  Update "conventions" section in the reference documentation: changes 
are highlighted in red. (convent20.chm) (W16CRQ)





On 30.09.2015 08:19, Markus Ratzesberger wrote:
> Hallo,
>
> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich aber
> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
> "continous delivery" hat kaum etwas gebracht.
>
> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>
>
> Markus

Hallo Frank,

verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner 
hat das im September 2015(!) geschrieben. Damals war überhaupt noch 
nicht absehbar, wie sich das mit der Continuous Delivery entwickeln 
würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich 
den Kommentar von Markus durchaus verstehen.

Jan

Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
> Hallo Markus,
>
> ich habe heute meinen "ich lese mal quer" Tag ...
> So bin ich über diese Frage gestolpert.
>
> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>
> Aber
>> Auch das mit 2.0 eingeführte
>> "continous delivery" hat kaum etwas gebracht.
> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>
> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>
>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend ist
> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem Windowsn
> Aniversary Update "nur" in einem Update ohne Versionssprung
> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>
> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen anzuschauen
> und das hast bisher versäumt: siehe unten.
>
> Das hast du alles verpasst.
>
> Gruß, Frank
>
>
> Build 2.00.779 (closed workitems)
> New features Add function DbDestroy() to the data-definition-language
> (DDL) to delete an ISAM emulating table programmatically by the
> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>
> Fixes/Changes Correct the calculation of the the column widths of the
> grids displayed in the debugger's auxilliary views. These may become
> smaller as the views get refreshed in a debugging session.
> (xppworkbench.exe) (W16CTU) (PDR6868)
>
>  Correct debugger issue where debugging codeblocks and inspecting
> variable values crashes the client application and/or the debugger.
> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>
>  Correct the Xbase++ debugger kernel so that breakpoints set in a
> calling context halt the debuggee after the STEP BACK (step out) command
> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>
>  Resolve issue where a replace operation may force a runtime error right
> after an append in exclusive mode of the PostgreSQL ISAM emulation.
> (pgdbe.dll) (W16CWJ) (PDR6840)
>
>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
> reference parameter types. If passed by value, only character, object
> and codeblock must support NIL to signal no input value. (xpprt1.dll)
> (W16CWQ) (PDR6864)
>
>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
> that execution halts in the current context if the context was called
> recursively. Currently, the debuggee is halted only after the recursion
> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>
>  Correct the debugger kernel so that a "step into" command stops the
> debuggee in the calling function or method if the current line contains
> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>
>  Correct the callstack view in the Workbench debugger so that the
> current context (callstack level) is indicated correctly, even when
> debugging a function that is calling itself recursively.
> (xppworkbench.exe) (W17CW1) (PDR6869)
>
>  Correct the "step over" debugger command so that execution indeed stops
> after the current line when the cursor is on a line calling the current
> procedure recursively. Currently, the "step over" command behaves as if
> "step into" was executed, and execution stops in the first line of the
> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>
>  Fix race condition due to statement leak which leads the PostgreSQL
> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>
>  Resolve issues where a filter condition may lead to a runtime error
> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
> (W17CX2) (PDR6622)
>
>  Correct the XbpTreeView class so that tree view items can be
> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>
>  Add a class method :setBehavior() to the XbpBrowse class to allow
> configuring the navigational behavior of all browse objects.
> (xppdui.dll) (W17CXH) (PDR6873)
>
>  Resolve IDSC or stall with 1-digit port in connection string of
> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ) (PDR6861)
>
>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>
>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
> test. (pgdbe.dll) (W17CXL) (PDR6848)
>
>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
> (W17CXN) (PDR6847)
>
>  Resolve issue with empty resultsets and invalid EOF() and Found()
> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>
>  Fix issue with default precision handling for aggregate results. Add
> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
> (PDR6824)
>
>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>
>  Resolve issue with wrong record number in empty workarea if all records
> get filtered out by the FOR expression of the current order. Extend unit
> test. (pgdbe.dll) (W17CXS) (PDR6818)
>
>  Resolve issues where OrdListRebuild() may run into an internal error
> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>
>  Fix the issue where creating an index with same name as an open index
> yields error while the PGDBE is trying to update the seek procedure.
> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>
>  Correct the PostgreSQL documentation regarding the numeric precision
> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>
>  Resolve the issues where adding an index tag to an existing bag leads
> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX) (PDR6801)
>
>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>
>  Ensure the debugger tool tips are displayed correctly when using the
> "Adjust the size of text and other display items" system option under
> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>
>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
> causes an error message to appear ("canvas drawing error") when building
> or debugging an application. (xppworkbench.exe) (W16CTK)
>
>  Correct the example code in the "Using northwind programmatically"
> programming guide chapter in the PGDBE documentation: the session object
> used with an SQL SELECT must be specified in parentheses. (*.chm) (W16CTR)
>
>  Output a warning when attempting to load executables containing name
> tokens such as "install" or "setup" into the debugger. This is required
> as Windows handles executables with these names differently and may not
> allow debugging. (xppworkbench.exe) (W16CUR)
>
>  Correct product sample readme files to conform to the specifications
> regarding content and format. (samples) (W16CWP)
>
>  Reduce flicker in the context windows of the debugger when stepping
> through the code. The callstack window, for example, flickers
> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>
>  Ensure xppdui.dll is exported to the \runtime folder by the local
> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
> the runtime folder of the installed product. (*.msi) (W17CWY)
>
>
>
>
>
>
> Build 2.00.769 (closed workitems)
> New features Maintain asac.log in the users documents\xbase++\.logs
> folder. (xppworkbench.exe) (W16CTQ)
>
>  Ensure that all datatypes from types.ch are properly supported by the
> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>
>  Add readme to the styled combo box example for the XbpHTMLStyle class
> to describe the rationale behind the sample. (samples) (W16CU7)
>
>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
> ensure that called code is not affecting FPU status of the Xbase++
> application. (xpprt1.dll) (W16CUB)
>
> Fixes/Changes Investigate and resolve issue why halting a running
> debuggee (CTRL+S) takes such a long time to complete under Windows 10
> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>
>  Correct runtime FPU control word management so that calls to
> misbehaving API or printer driver code does not affect rounding
> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>
>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
> operated with the finger, even after tapping the data area of the
> browse. (xppdui.dll) (W16CT3) (PDR6822)
>
>  Correct the XbpQuickBrowse class so that it works correctly with a
> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>
>  Correct the XbpToolBar class so that no runtime error occurs when the
> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>
>  Add code to the XbpPrinter for ensuring that the current FPU settings
> are reset after communicating with a printer driver. (xppui1.dll)
> (W16CTX) (PDR6854)
>
>  Correct the XbpHTMLStyle class so that the output is positioned
> correctly when used in conjunction with the XbpComboBox class.
> (xppwui.dll) (W16CU2) (PDR6860)
>
>  Correct the issue in the Workbench debugger which may cause runtime
> errors in the IDE after resuming the client application after stopping
> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>
>  Correct the Workbench debugger so that executables can be debugged
> which reside in a path containing Umlaut characters (xppworkbench.exe)
> (W16CUH) (PDR6639)
>
>  Fix SQLite type affinity related PDR 6855. Extend the existing test
> suite to ensure correct behaviour according to SQLite spec./doc.
> (asrdbc10.dll) (W16CUJ) (PDR6855)
>
>  Resolve issue where SQL SELECT operations against local tables may
> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
> (W16CUK) (PDR6762)
>
>  The header files in the auto-dependency section must be normalized
> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>
>  Resolve DACSqlStatement: No instances allowed for this class error and
> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
> (W16CUQ) (PDR6815)
>
>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
> (PDR6757)
>
>  Ensure strings used with HTML/CSS-based Xbase Parts such as
> XbpCommandButton are converted to ANSI when the application uses an OEM
> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U) (PDR6712)
>
>  Remove the commandline switch /rc from the resource compiler executable
> and documentation. (arc.exe) (W16CT2)
>
>  Validate for the correct interface when a XmlMapper is passed as second
> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>
>  Correct the source code sample in the chapter "Programmatic reference -
> dbfupsize.dll" (pg20.chm) (W16CUA)
>
>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
> array for fieldcount 1 - N and an empty array for an empty result set.
> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>
>  Review USQL unit tests with respect to the revised type system and
> ensure that the core types are properly validated. (adac20b.dll) (W16CUX)
>
>
>
>
>
> Build 2.00.762 (closed workitems)
> New features Add alternative interfaces for loading images used in the
> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
> Base64-encoded and defined via a :data URI scheme. (xppwui.dll) (W16CJT)
>
>  Ensure the project manager restores the collapse/expand state.
> (xppworkbench.exe) (W16CND)
>
>  Extend Workbench pre-defined macros to support all directories from the
> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>
>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types. Extend
> the unit-test to cover the entire range of possible values as parameter,
> reference parameter and return value. (xpprt1.dll) (W16CNR)
>
>  Add a function BinaryName() to identify the execution context. The
> function returns the name of the binary (exe or dll) executing the
> function. (xpprt1.dll) (W16CNX)
>
>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
> unit-test to cover the entire range of possible values as parameter,
> reference parameter and return value. (xpprt1.dll) (W16CPK)
>
>  Add a control for indicating busy state to the Xbase++ Workbench.
> (xppworkbench.exe) (W16CQB)
>
>  The workbench must maintain logfiles in the user's documents folder
> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
> (xppworkbench.exe) (W16CRW)
>
>  Add optional feature "Asset Repository" to the installation package.
> The feature is a child of "Xbase++ 2.0 for windows". Installation is
> done to the users documents folder "Xbase++\.assets". (xpp*.msi) (W16CH3)
>
> Fixes/Changes Add a resource setting to configure round() behavior
> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>
>  Ensure that mails containing a line starting with a dot are send
> completly instead of as a fragment by the SmtpClient class. See PDR
> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>
>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
> presentation parameter when computing the position of the header and
> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>
>  Fix handle leak in PGDBE when performing SELECT queries and extend the
> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
> (PDR6834)
>
>  Highlight new content in the documentation using the color dark red.
> (xppref.css) (W16CJR)
>
>  Ensure the XbpImageListBox control conforms to our coding style.
> (asset) (W16CL2)
>
>  Ensure that asget writes error messages to stdout. This enables the
> workbench to display the error message. (asget.exe) (W16CL7)
>
>  Extend exisiting Workbench template mechanism in such a way that new
> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>
>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and associated
> files conform to our coding style. (asset) (W16CLC)
>
>  Ensure XbpHTMLStatic class and associated code conform to our coding
> style. (asset) (W16CLH)
>
>  Ensure the XbpCommandButton class and related files conform to our
> coding style. (asset) (W16CLJ)
>
>  Ensure the XbpCheckedListBox class and related files conform to our
> coding style. (asset) (W16CN1)
>
>  Ensure the dialog for managing target-specific assets remembers its
> current size and position, as well as splitbar position.
> (xppworkbench.exe) (W16CN2)
>
>  Ensure the "New Items" dialog remembers its current size and position
> (xppworkbench.exe) (W16CN3)
>
>  Create and add import definition for VFP modernizer to Workbench
> (xppworkbench.exe) (W16CNC)
>
>  Change "New items" dialog so that the view style (large icons etc.) is
> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>
>  Modify the event management sample in the CXP sample collection so that
> it uses the POST verb for transferring data, eg. when saving events.
> (alaska-software.webui.js) (W16CP1)
>
>  Add a static/non-collapsible panel class to the XbpPanelContainer
> control. (asset) (W16CP4)
>
>  Extend the styled list box example for the XbpHTMLStyle class so that
> it better illustrates the usage of the WebUI for customizing an existing
> Xbase Part. (samples) (W16CP7)
>
>  Ensure the XbpToggleButton class and related files conform to our
> coding style. (asset) (W16CPA)
>
>  Correct the htmlhelp.exe example so that it displays context-sensitive
> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>
>  Ensure the new project manager target nodes are expanded by default.
> (xwbassochlp20.dll) (W16CPD)
>
>  Reorganize the closed workitems list in such a way that new features
> and changes are shown first followed by the list of fixes/corrections
> (changes20.chm) (W16CPL)
>
>  Ensure that ALINK is able to handle long import library names identical
> in the first 16 chars. (alink.exe) (W16CPQ)
>
>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
> the XbpColumn class init state needs to be independent from module init
> state. (xppdui.dll) (W16CPY)
>
>  Use global busy indicator when build is in progress. (xppworkbench.exe)
> (W16CQ1)
>
>  Update "conventions" section in the reference documentation: changes
> are highlighted in red. (convent20.chm) (W16CRQ)
>
>
>
>
>
> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>> Hallo,
>>
>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich aber
>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>> "continous delivery" hat kaum etwas gebracht.
>>
>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>
>>
>> Markus
>

Hey Jan,

ja, das kam spät von mir.
Aber ich konnte das nicht so stehen lassen.
Und ich hatte mir extra das Kundenkonto vorher angeschaut.

Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht 
definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre 
etwas passiert. CDI macht es anders. Es geht hier auch nicht um die 
Frequenz. Sondern vorher haben wir immer gewartet und gewartet und 
gewartet und noch dieses Feature dran gemacht und noch das Schleifchen. 
Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben 
Feature-Grades ("Reifezustand" eines Features), ...

Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.

Anyhow, CDI war ein wichtiger Schritt.
Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen 
noch weiter helfen. Und und und ...

Bis bald,

Frank


On 31.03.2017 22:24, Jan Escholt wrote:
> Hallo Frank,
>
> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
> den Kommentar von Markus durchaus verstehen.
>
> Jan
>
> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>> Hallo Markus,
>>
>> ich habe heute meinen "ich lese mal quer" Tag ...
>> So bin ich über diese Frage gestolpert.
>>
>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>
>> Aber
>>> Auch das mit 2.0 eingeführte
>>> "continous delivery" hat kaum etwas gebracht.
>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>
>> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>>
>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend ist
>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem Windowsn
>> Aniversary Update "nur" in einem Update ohne Versionssprung
>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>
>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen anzuschauen
>> und das hast bisher versäumt: siehe unten.
>>
>> Das hast du alles verpasst.
>>
>> Gruß, Frank
>>
>>
>> Build 2.00.779 (closed workitems)
>> New features Add function DbDestroy() to the data-definition-language
>> (DDL) to delete an ISAM emulating table programmatically by the
>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>
>> Fixes/Changes Correct the calculation of the the column widths of the
>> grids displayed in the debugger's auxilliary views. These may become
>> smaller as the views get refreshed in a debugging session.
>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>
>>  Correct debugger issue where debugging codeblocks and inspecting
>> variable values crashes the client application and/or the debugger.
>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>
>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>> calling context halt the debuggee after the STEP BACK (step out) command
>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>
>>  Resolve issue where a replace operation may force a runtime error right
>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>
>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>> reference parameter types. If passed by value, only character, object
>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>> (W16CWQ) (PDR6864)
>>
>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>> that execution halts in the current context if the context was called
>> recursively. Currently, the debuggee is halted only after the recursion
>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>
>>  Correct the debugger kernel so that a "step into" command stops the
>> debuggee in the calling function or method if the current line contains
>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>
>>  Correct the callstack view in the Workbench debugger so that the
>> current context (callstack level) is indicated correctly, even when
>> debugging a function that is calling itself recursively.
>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>
>>  Correct the "step over" debugger command so that execution indeed stops
>> after the current line when the cursor is on a line calling the current
>> procedure recursively. Currently, the "step over" command behaves as if
>> "step into" was executed, and execution stops in the first line of the
>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>
>>  Fix race condition due to statement leak which leads the PostgreSQL
>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>
>>  Resolve issues where a filter condition may lead to a runtime error
>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>> (W17CX2) (PDR6622)
>>
>>  Correct the XbpTreeView class so that tree view items can be
>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>
>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>> configuring the navigational behavior of all browse objects.
>> (xppdui.dll) (W17CXH) (PDR6873)
>>
>>  Resolve IDSC or stall with 1-digit port in connection string of
>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ) (PDR6861)
>>
>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>
>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>
>>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
>> (W17CXN) (PDR6847)
>>
>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>
>>  Fix issue with default precision handling for aggregate results. Add
>> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
>> (PDR6824)
>>
>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>
>>  Resolve issue with wrong record number in empty workarea if all records
>> get filtered out by the FOR expression of the current order. Extend unit
>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>
>>  Resolve issues where OrdListRebuild() may run into an internal error
>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>
>>  Fix the issue where creating an index with same name as an open index
>> yields error while the PGDBE is trying to update the seek procedure.
>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>
>>  Correct the PostgreSQL documentation regarding the numeric precision
>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>
>>  Resolve the issues where adding an index tag to an existing bag leads
>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>> (PDR6801)
>>
>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>
>>  Ensure the debugger tool tips are displayed correctly when using the
>> "Adjust the size of text and other display items" system option under
>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>
>>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
>> causes an error message to appear ("canvas drawing error") when building
>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>
>>  Correct the example code in the "Using northwind programmatically"
>> programming guide chapter in the PGDBE documentation: the session object
>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>> (W16CTR)
>>
>>  Output a warning when attempting to load executables containing name
>> tokens such as "install" or "setup" into the debugger. This is required
>> as Windows handles executables with these names differently and may not
>> allow debugging. (xppworkbench.exe) (W16CUR)
>>
>>  Correct product sample readme files to conform to the specifications
>> regarding content and format. (samples) (W16CWP)
>>
>>  Reduce flicker in the context windows of the debugger when stepping
>> through the code. The callstack window, for example, flickers
>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>
>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>
>>
>>
>>
>>
>>
>> Build 2.00.769 (closed workitems)
>> New features Maintain asac.log in the users documents\xbase++\.logs
>> folder. (xppworkbench.exe) (W16CTQ)
>>
>>  Ensure that all datatypes from types.ch are properly supported by the
>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>
>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>> to describe the rationale behind the sample. (samples) (W16CU7)
>>
>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>> ensure that called code is not affecting FPU status of the Xbase++
>> application. (xpprt1.dll) (W16CUB)
>>
>> Fixes/Changes Investigate and resolve issue why halting a running
>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>
>>  Correct runtime FPU control word management so that calls to
>> misbehaving API or printer driver code does not affect rounding
>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>
>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>> operated with the finger, even after tapping the data area of the
>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>
>>  Correct the XbpQuickBrowse class so that it works correctly with a
>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>
>>  Correct the XbpToolBar class so that no runtime error occurs when the
>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>
>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>> are reset after communicating with a printer driver. (xppui1.dll)
>> (W16CTX) (PDR6854)
>>
>>  Correct the XbpHTMLStyle class so that the output is positioned
>> correctly when used in conjunction with the XbpComboBox class.
>> (xppwui.dll) (W16CU2) (PDR6860)
>>
>>  Correct the issue in the Workbench debugger which may cause runtime
>> errors in the IDE after resuming the client application after stopping
>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>
>>  Correct the Workbench debugger so that executables can be debugged
>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>> (W16CUH) (PDR6639)
>>
>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>> suite to ensure correct behaviour according to SQLite spec./doc.
>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>
>>  Resolve issue where SQL SELECT operations against local tables may
>> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
>> (W16CUK) (PDR6762)
>>
>>  The header files in the auto-dependency section must be normalized
>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>
>>  Resolve DACSqlStatement: No instances allowed for this class error and
>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>> (W16CUQ) (PDR6815)
>>
>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>> (PDR6757)
>>
>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>> XbpCommandButton are converted to ANSI when the application uses an OEM
>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U) (PDR6712)
>>
>>  Remove the commandline switch /rc from the resource compiler executable
>> and documentation. (arc.exe) (W16CT2)
>>
>>  Validate for the correct interface when a XmlMapper is passed as second
>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>
>>  Correct the source code sample in the chapter "Programmatic reference -
>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>
>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>> array for fieldcount 1 - N and an empty array for an empty result set.
>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>
>>  Review USQL unit tests with respect to the revised type system and
>> ensure that the core types are properly validated. (adac20b.dll) (W16CUX)
>>
>>
>>
>>
>>
>> Build 2.00.762 (closed workitems)
>> New features Add alternative interfaces for loading images used in the
>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll) (W16CJT)
>>
>>  Ensure the project manager restores the collapse/expand state.
>> (xppworkbench.exe) (W16CND)
>>
>>  Extend Workbench pre-defined macros to support all directories from the
>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>
>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types. Extend
>> the unit-test to cover the entire range of possible values as parameter,
>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>
>>  Add a function BinaryName() to identify the execution context. The
>> function returns the name of the binary (exe or dll) executing the
>> function. (xpprt1.dll) (W16CNX)
>>
>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
>> unit-test to cover the entire range of possible values as parameter,
>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>
>>  Add a control for indicating busy state to the Xbase++ Workbench.
>> (xppworkbench.exe) (W16CQB)
>>
>>  The workbench must maintain logfiles in the user's documents folder
>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>> (xppworkbench.exe) (W16CRW)
>>
>>  Add optional feature "Asset Repository" to the installation package.
>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>> done to the users documents folder "Xbase++\.assets". (xpp*.msi) (W16CH3)
>>
>> Fixes/Changes Add a resource setting to configure round() behavior
>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>
>>  Ensure that mails containing a line starting with a dot are send
>> completly instead of as a fragment by the SmtpClient class. See PDR
>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>
>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>> presentation parameter when computing the position of the header and
>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>
>>  Fix handle leak in PGDBE when performing SELECT queries and extend the
>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>> (PDR6834)
>>
>>  Highlight new content in the documentation using the color dark red.
>> (xppref.css) (W16CJR)
>>
>>  Ensure the XbpImageListBox control conforms to our coding style.
>> (asset) (W16CL2)
>>
>>  Ensure that asget writes error messages to stdout. This enables the
>> workbench to display the error message. (asget.exe) (W16CL7)
>>
>>  Extend exisiting Workbench template mechanism in such a way that new
>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>
>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and associated
>> files conform to our coding style. (asset) (W16CLC)
>>
>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>> style. (asset) (W16CLH)
>>
>>  Ensure the XbpCommandButton class and related files conform to our
>> coding style. (asset) (W16CLJ)
>>
>>  Ensure the XbpCheckedListBox class and related files conform to our
>> coding style. (asset) (W16CN1)
>>
>>  Ensure the dialog for managing target-specific assets remembers its
>> current size and position, as well as splitbar position.
>> (xppworkbench.exe) (W16CN2)
>>
>>  Ensure the "New Items" dialog remembers its current size and position
>> (xppworkbench.exe) (W16CN3)
>>
>>  Create and add import definition for VFP modernizer to Workbench
>> (xppworkbench.exe) (W16CNC)
>>
>>  Change "New items" dialog so that the view style (large icons etc.) is
>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>
>>  Modify the event management sample in the CXP sample collection so that
>> it uses the POST verb for transferring data, eg. when saving events.
>> (alaska-software.webui.js) (W16CP1)
>>
>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>> control. (asset) (W16CP4)
>>
>>  Extend the styled list box example for the XbpHTMLStyle class so that
>> it better illustrates the usage of the WebUI for customizing an existing
>> Xbase Part. (samples) (W16CP7)
>>
>>  Ensure the XbpToggleButton class and related files conform to our
>> coding style. (asset) (W16CPA)
>>
>>  Correct the htmlhelp.exe example so that it displays context-sensitive
>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>
>>  Ensure the new project manager target nodes are expanded by default.
>> (xwbassochlp20.dll) (W16CPD)
>>
>>  Reorganize the closed workitems list in such a way that new features
>> and changes are shown first followed by the list of fixes/corrections
>> (changes20.chm) (W16CPL)
>>
>>  Ensure that ALINK is able to handle long import library names identical
>> in the first 16 chars. (alink.exe) (W16CPQ)
>>
>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>> the XbpColumn class init state needs to be independent from module init
>> state. (xppdui.dll) (W16CPY)
>>
>>  Use global busy indicator when build is in progress. (xppworkbench.exe)
>> (W16CQ1)
>>
>>  Update "conventions" section in the reference documentation: changes
>> are highlighted in red. (convent20.chm) (W16CRQ)
>>
>>
>>
>>
>>
>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>> Hallo,
>>>
>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich aber
>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>> "continous delivery" hat kaum etwas gebracht.
>>>
>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>
>>>
>>> Markus
>>

Hallo Frank,

versteh mich bitte nicht falsch. Ich bin durchaus sehr einverstanden mit 
Eurer CDI. Steffen hatte mir schon 2008 in Berlin vor versammelter 
Mannschaft zugesichert, das die Rhythmen der Fixes kürzer werden würden. 
Und wir wissen beide, was passiert ist. Es hat sich nämlich garnichts 
geändert danach. Jetzt mit CDI ist das vielleicht nicht so schnell wie 
gewünscht (die Ansprüche steigen halt), und viele Punkte sind überhaupt 
nichts für mich, aber ja, wenn das so weitergeht wie die letzten Monate, 
dann bin ich durchaus zufrieden damit.

Aber damals, als Markus das schrieb, war das noch in keinster Weise 
absehbar, was da kommen würde. Du hast zwar unten eine lange Latte von 
abgearbeiteten Punkten zitiert, und das will ich auch nicht klein reden. 
Aber auch die Abstände zwischen einzelnen Updates im CDI waren 
zwischendurch immer mal nicht von schlechten Eltern - und das meine ich 
nicht positiv. Es scheint sich jetzt ganz wesentlich zu bessern. Aber 
zum zum Zeitpunkt der Threaderöfffnung war das halt noch nicht absehbar, 
da war gerade nach 6monatiger Pause gerade ein Update erschienen. Was 
nicht den damals von Alaska kommunizierten Ansprüchen entsprach.

Jan

Am 04.04.2017 um 18:08 schrieb Frank Grossheinrich:
> Hey Jan,
>
> ja, das kam spät von mir.
> Aber ich konnte das nicht so stehen lassen.
> Und ich hatte mir extra das Kundenkonto vorher angeschaut.
>
> Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht
> definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
> Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre
> etwas passiert. CDI macht es anders. Es geht hier auch nicht um die
> Frequenz. Sondern vorher haben wir immer gewartet und gewartet und
> gewartet und noch dieses Feature dran gemacht und noch das Schleifchen.
> Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben
> Feature-Grades ("Reifezustand" eines Features), ...
>
> Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.
>
> Anyhow, CDI war ein wichtiger Schritt.
> Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen
> noch weiter helfen. Und und und ...
>
> Bis bald,
>
> Frank
>
>
> On 31.03.2017 22:24, Jan Escholt wrote:
>> Hallo Frank,
>>
>> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
>> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
>> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
>> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
>> den Kommentar von Markus durchaus verstehen.
>>
>> Jan
>>
>> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>>> Hallo Markus,
>>>
>>> ich habe heute meinen "ich lese mal quer" Tag ...
>>> So bin ich über diese Frage gestolpert.
>>>
>>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>>
>>> Aber
>>>> Auch das mit 2.0 eingeführte
>>>> "continous delivery" hat kaum etwas gebracht.
>>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>>
>>> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>>>
>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend ist
>>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem
>>> Windowsn
>>> Aniversary Update "nur" in einem Update ohne Versionssprung
>>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>>
>>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen anzuschauen
>>> und das hast bisher versäumt: siehe unten.
>>>
>>> Das hast du alles verpasst.
>>>
>>> Gruß, Frank
>>>
>>>
>>> Build 2.00.779 (closed workitems)
>>> New features Add function DbDestroy() to the data-definition-language
>>> (DDL) to delete an ISAM emulating table programmatically by the
>>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>>
>>> Fixes/Changes Correct the calculation of the the column widths of the
>>> grids displayed in the debugger's auxilliary views. These may become
>>> smaller as the views get refreshed in a debugging session.
>>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>>
>>>  Correct debugger issue where debugging codeblocks and inspecting
>>> variable values crashes the client application and/or the debugger.
>>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>>
>>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>>> calling context halt the debuggee after the STEP BACK (step out) command
>>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>>
>>>  Resolve issue where a replace operation may force a runtime error right
>>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>>
>>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>>> reference parameter types. If passed by value, only character, object
>>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>>> (W16CWQ) (PDR6864)
>>>
>>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>>> that execution halts in the current context if the context was called
>>> recursively. Currently, the debuggee is halted only after the recursion
>>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>>
>>>  Correct the debugger kernel so that a "step into" command stops the
>>> debuggee in the calling function or method if the current line contains
>>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>>
>>>  Correct the callstack view in the Workbench debugger so that the
>>> current context (callstack level) is indicated correctly, even when
>>> debugging a function that is calling itself recursively.
>>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>>
>>>  Correct the "step over" debugger command so that execution indeed stops
>>> after the current line when the cursor is on a line calling the current
>>> procedure recursively. Currently, the "step over" command behaves as if
>>> "step into" was executed, and execution stops in the first line of the
>>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>>
>>>  Fix race condition due to statement leak which leads the PostgreSQL
>>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>>
>>>  Resolve issues where a filter condition may lead to a runtime error
>>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>>> (W17CX2) (PDR6622)
>>>
>>>  Correct the XbpTreeView class so that tree view items can be
>>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>>
>>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>>> configuring the navigational behavior of all browse objects.
>>> (xppdui.dll) (W17CXH) (PDR6873)
>>>
>>>  Resolve IDSC or stall with 1-digit port in connection string of
>>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ) (PDR6861)
>>>
>>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>>
>>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>>
>>>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
>>> (W17CXN) (PDR6847)
>>>
>>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>>
>>>  Fix issue with default precision handling for aggregate results. Add
>>> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
>>> (PDR6824)
>>>
>>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>>
>>>  Resolve issue with wrong record number in empty workarea if all records
>>> get filtered out by the FOR expression of the current order. Extend unit
>>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>>
>>>  Resolve issues where OrdListRebuild() may run into an internal error
>>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>>
>>>  Fix the issue where creating an index with same name as an open index
>>> yields error while the PGDBE is trying to update the seek procedure.
>>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>>
>>>  Correct the PostgreSQL documentation regarding the numeric precision
>>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>>
>>>  Resolve the issues where adding an index tag to an existing bag leads
>>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>>> (PDR6801)
>>>
>>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>>
>>>  Ensure the debugger tool tips are displayed correctly when using the
>>> "Adjust the size of text and other display items" system option under
>>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>>
>>>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
>>> causes an error message to appear ("canvas drawing error") when building
>>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>>
>>>  Correct the example code in the "Using northwind programmatically"
>>> programming guide chapter in the PGDBE documentation: the session object
>>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>>> (W16CTR)
>>>
>>>  Output a warning when attempting to load executables containing name
>>> tokens such as "install" or "setup" into the debugger. This is required
>>> as Windows handles executables with these names differently and may not
>>> allow debugging. (xppworkbench.exe) (W16CUR)
>>>
>>>  Correct product sample readme files to conform to the specifications
>>> regarding content and format. (samples) (W16CWP)
>>>
>>>  Reduce flicker in the context windows of the debugger when stepping
>>> through the code. The callstack window, for example, flickers
>>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>>
>>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>>
>>>
>>>
>>>
>>>
>>>
>>> Build 2.00.769 (closed workitems)
>>> New features Maintain asac.log in the users documents\xbase++\.logs
>>> folder. (xppworkbench.exe) (W16CTQ)
>>>
>>>  Ensure that all datatypes from types.ch are properly supported by the
>>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>>
>>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>>> to describe the rationale behind the sample. (samples) (W16CU7)
>>>
>>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>>> ensure that called code is not affecting FPU status of the Xbase++
>>> application. (xpprt1.dll) (W16CUB)
>>>
>>> Fixes/Changes Investigate and resolve issue why halting a running
>>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>>
>>>  Correct runtime FPU control word management so that calls to
>>> misbehaving API or printer driver code does not affect rounding
>>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>>
>>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>>> operated with the finger, even after tapping the data area of the
>>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>>
>>>  Correct the XbpQuickBrowse class so that it works correctly with a
>>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>>
>>>  Correct the XbpToolBar class so that no runtime error occurs when the
>>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>>
>>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>>> are reset after communicating with a printer driver. (xppui1.dll)
>>> (W16CTX) (PDR6854)
>>>
>>>  Correct the XbpHTMLStyle class so that the output is positioned
>>> correctly when used in conjunction with the XbpComboBox class.
>>> (xppwui.dll) (W16CU2) (PDR6860)
>>>
>>>  Correct the issue in the Workbench debugger which may cause runtime
>>> errors in the IDE after resuming the client application after stopping
>>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>>
>>>  Correct the Workbench debugger so that executables can be debugged
>>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>>> (W16CUH) (PDR6639)
>>>
>>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>>> suite to ensure correct behaviour according to SQLite spec./doc.
>>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>>
>>>  Resolve issue where SQL SELECT operations against local tables may
>>> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
>>> (W16CUK) (PDR6762)
>>>
>>>  The header files in the auto-dependency section must be normalized
>>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>>
>>>  Resolve DACSqlStatement: No instances allowed for this class error and
>>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>>> (W16CUQ) (PDR6815)
>>>
>>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>>> (PDR6757)
>>>
>>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>>> XbpCommandButton are converted to ANSI when the application uses an OEM
>>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U) (PDR6712)
>>>
>>>  Remove the commandline switch /rc from the resource compiler executable
>>> and documentation. (arc.exe) (W16CT2)
>>>
>>>  Validate for the correct interface when a XmlMapper is passed as second
>>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>>
>>>  Correct the source code sample in the chapter "Programmatic reference -
>>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>>
>>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>>> array for fieldcount 1 - N and an empty array for an empty result set.
>>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>>
>>>  Review USQL unit tests with respect to the revised type system and
>>> ensure that the core types are properly validated. (adac20b.dll)
>>> (W16CUX)
>>>
>>>
>>>
>>>
>>>
>>> Build 2.00.762 (closed workitems)
>>> New features Add alternative interfaces for loading images used in the
>>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll) (W16CJT)
>>>
>>>  Ensure the project manager restores the collapse/expand state.
>>> (xppworkbench.exe) (W16CND)
>>>
>>>  Extend Workbench pre-defined macros to support all directories from the
>>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>>
>>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types. Extend
>>> the unit-test to cover the entire range of possible values as parameter,
>>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>>
>>>  Add a function BinaryName() to identify the execution context. The
>>> function returns the name of the binary (exe or dll) executing the
>>> function. (xpprt1.dll) (W16CNX)
>>>
>>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
>>> unit-test to cover the entire range of possible values as parameter,
>>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>>
>>>  Add a control for indicating busy state to the Xbase++ Workbench.
>>> (xppworkbench.exe) (W16CQB)
>>>
>>>  The workbench must maintain logfiles in the user's documents folder
>>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>>> (xppworkbench.exe) (W16CRW)
>>>
>>>  Add optional feature "Asset Repository" to the installation package.
>>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>>> done to the users documents folder "Xbase++\.assets". (xpp*.msi)
>>> (W16CH3)
>>>
>>> Fixes/Changes Add a resource setting to configure round() behavior
>>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>>
>>>  Ensure that mails containing a line starting with a dot are send
>>> completly instead of as a fragment by the SmtpClient class. See PDR
>>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>>
>>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>>> presentation parameter when computing the position of the header and
>>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>>
>>>  Fix handle leak in PGDBE when performing SELECT queries and extend the
>>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>>> (PDR6834)
>>>
>>>  Highlight new content in the documentation using the color dark red.
>>> (xppref.css) (W16CJR)
>>>
>>>  Ensure the XbpImageListBox control conforms to our coding style.
>>> (asset) (W16CL2)
>>>
>>>  Ensure that asget writes error messages to stdout. This enables the
>>> workbench to display the error message. (asget.exe) (W16CL7)
>>>
>>>  Extend exisiting Workbench template mechanism in such a way that new
>>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>>
>>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and associated
>>> files conform to our coding style. (asset) (W16CLC)
>>>
>>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>>> style. (asset) (W16CLH)
>>>
>>>  Ensure the XbpCommandButton class and related files conform to our
>>> coding style. (asset) (W16CLJ)
>>>
>>>  Ensure the XbpCheckedListBox class and related files conform to our
>>> coding style. (asset) (W16CN1)
>>>
>>>  Ensure the dialog for managing target-specific assets remembers its
>>> current size and position, as well as splitbar position.
>>> (xppworkbench.exe) (W16CN2)
>>>
>>>  Ensure the "New Items" dialog remembers its current size and position
>>> (xppworkbench.exe) (W16CN3)
>>>
>>>  Create and add import definition for VFP modernizer to Workbench
>>> (xppworkbench.exe) (W16CNC)
>>>
>>>  Change "New items" dialog so that the view style (large icons etc.) is
>>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>>
>>>  Modify the event management sample in the CXP sample collection so that
>>> it uses the POST verb for transferring data, eg. when saving events.
>>> (alaska-software.webui.js) (W16CP1)
>>>
>>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>>> control. (asset) (W16CP4)
>>>
>>>  Extend the styled list box example for the XbpHTMLStyle class so that
>>> it better illustrates the usage of the WebUI for customizing an existing
>>> Xbase Part. (samples) (W16CP7)
>>>
>>>  Ensure the XbpToggleButton class and related files conform to our
>>> coding style. (asset) (W16CPA)
>>>
>>>  Correct the htmlhelp.exe example so that it displays context-sensitive
>>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>>
>>>  Ensure the new project manager target nodes are expanded by default.
>>> (xwbassochlp20.dll) (W16CPD)
>>>
>>>  Reorganize the closed workitems list in such a way that new features
>>> and changes are shown first followed by the list of fixes/corrections
>>> (changes20.chm) (W16CPL)
>>>
>>>  Ensure that ALINK is able to handle long import library names identical
>>> in the first 16 chars. (alink.exe) (W16CPQ)
>>>
>>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>>> the XbpColumn class init state needs to be independent from module init
>>> state. (xppdui.dll) (W16CPY)
>>>
>>>  Use global busy indicator when build is in progress. (xppworkbench.exe)
>>> (W16CQ1)
>>>
>>>  Update "conventions" section in the reference documentation: changes
>>> are highlighted in red. (convent20.chm) (W16CRQ)
>>>
>>>
>>>
>>>
>>>
>>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>>> Hallo,
>>>>
>>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich aber
>>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>>> "continous delivery" hat kaum etwas gebracht.
>>>>
>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>
>>>>
>>>> Markus
>>>
>

Kannst du dir wirklich solche Jahreszahlen merken? 2008?
Wie dem auch sei, CDI hat uns locker 2 Jahre an Arbeit gekostet. Das ist 
ja nicht nur, dass wir Updates bereitstellen, sondern dahinter steckt ja 
eine komplette Infrastruktur. Das fängt vom Build-Prozessor an (also das 
Ding, das Xbase++ und all seine Komponenten zusammenbaut) bis hin zum 
Packaging und Deployment. Ganz ehrlich: wir machen da nix mehr von Hand. 
Das ist alles automatisiert (leider noch nicht das PDR Fixing ). Und 
das war eine gewaltige Aufgabe.

Und auch wir freuen uns, dass wir uns die Zeit dafür genommen haben, 
denn es macht Dinge einfacher und macht uns flexibler. Und hilft unseren 
Kunden.

"Als Markus das schrieb" waren auch schon einige Updates verfügbar. Ich 
habe gerade nachgeschaut: das waren seit Erscheinen der Version 2.0 5 
Updates bis zum Post. Also so schlecht hat das nicht ausgesehen. Auch 
wenn ich die Zweifel manchmal verstehe.

Gruß, ich


On 04.04.2017 20:45, Jan Escholt wrote:
> Hallo Frank,
>
> versteh mich bitte nicht falsch. Ich bin durchaus sehr einverstanden mit
> Eurer CDI. Steffen hatte mir schon 2008 in Berlin vor versammelter
> Mannschaft zugesichert, das die Rhythmen der Fixes kürzer werden würden.
> Und wir wissen beide, was passiert ist. Es hat sich nämlich garnichts
> geändert danach. Jetzt mit CDI ist das vielleicht nicht so schnell wie
> gewünscht (die Ansprüche steigen halt), und viele Punkte sind überhaupt
> nichts für mich, aber ja, wenn das so weitergeht wie die letzten Monate,
> dann bin ich durchaus zufrieden damit.
>
> Aber damals, als Markus das schrieb, war das noch in keinster Weise
> absehbar, was da kommen würde. Du hast zwar unten eine lange Latte von
> abgearbeiteten Punkten zitiert, und das will ich auch nicht klein reden.
> Aber auch die Abstände zwischen einzelnen Updates im CDI waren
> zwischendurch immer mal nicht von schlechten Eltern - und das meine ich
> nicht positiv. Es scheint sich jetzt ganz wesentlich zu bessern. Aber
> zum zum Zeitpunkt der Threaderöfffnung war das halt noch nicht absehbar,
> da war gerade nach 6monatiger Pause gerade ein Update erschienen. Was
> nicht den damals von Alaska kommunizierten Ansprüchen entsprach.
>
> Jan
>
> Am 04.04.2017 um 18:08 schrieb Frank Grossheinrich:
>> Hey Jan,
>>
>> ja, das kam spät von mir.
>> Aber ich konnte das nicht so stehen lassen.
>> Und ich hatte mir extra das Kundenkonto vorher angeschaut.
>>
>> Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht
>> definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
>> Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre
>> etwas passiert. CDI macht es anders. Es geht hier auch nicht um die
>> Frequenz. Sondern vorher haben wir immer gewartet und gewartet und
>> gewartet und noch dieses Feature dran gemacht und noch das Schleifchen.
>> Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben
>> Feature-Grades ("Reifezustand" eines Features), ...
>>
>> Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.
>>
>> Anyhow, CDI war ein wichtiger Schritt.
>> Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen
>> noch weiter helfen. Und und und ...
>>
>> Bis bald,
>>
>> Frank
>>
>>
>> On 31.03.2017 22:24, Jan Escholt wrote:
>>> Hallo Frank,
>>>
>>> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
>>> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
>>> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
>>> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
>>> den Kommentar von Markus durchaus verstehen.
>>>
>>> Jan
>>>
>>> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>>>> Hallo Markus,
>>>>
>>>> ich habe heute meinen "ich lese mal quer" Tag ...
>>>> So bin ich über diese Frage gestolpert.
>>>>
>>>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>>>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>>>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>>>
>>>> Aber
>>>>> Auch das mit 2.0 eingeführte
>>>>> "continous delivery" hat kaum etwas gebracht.
>>>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>>>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>>>
>>>> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>>>>
>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend
>>>> ist
>>>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem
>>>> Windowsn
>>>> Aniversary Update "nur" in einem Update ohne Versionssprung
>>>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>>>
>>>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen
>>>> anzuschauen
>>>> und das hast bisher versäumt: siehe unten.
>>>>
>>>> Das hast du alles verpasst.
>>>>
>>>> Gruß, Frank
>>>>
>>>>
>>>> Build 2.00.779 (closed workitems)
>>>> New features Add function DbDestroy() to the data-definition-language
>>>> (DDL) to delete an ISAM emulating table programmatically by the
>>>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>>>
>>>> Fixes/Changes Correct the calculation of the the column widths of the
>>>> grids displayed in the debugger's auxilliary views. These may become
>>>> smaller as the views get refreshed in a debugging session.
>>>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>>>
>>>>  Correct debugger issue where debugging codeblocks and inspecting
>>>> variable values crashes the client application and/or the debugger.
>>>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>>>
>>>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>>>> calling context halt the debuggee after the STEP BACK (step out)
>>>> command
>>>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>>>
>>>>  Resolve issue where a replace operation may force a runtime error
>>>> right
>>>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>>>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>>>
>>>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>>>> reference parameter types. If passed by value, only character, object
>>>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>>>> (W16CWQ) (PDR6864)
>>>>
>>>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>>>> that execution halts in the current context if the context was called
>>>> recursively. Currently, the debuggee is halted only after the recursion
>>>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>>>
>>>>  Correct the debugger kernel so that a "step into" command stops the
>>>> debuggee in the calling function or method if the current line contains
>>>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>>>
>>>>  Correct the callstack view in the Workbench debugger so that the
>>>> current context (callstack level) is indicated correctly, even when
>>>> debugging a function that is calling itself recursively.
>>>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>>>
>>>>  Correct the "step over" debugger command so that execution indeed
>>>> stops
>>>> after the current line when the cursor is on a line calling the current
>>>> procedure recursively. Currently, the "step over" command behaves as if
>>>> "step into" was executed, and execution stops in the first line of the
>>>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>>>
>>>>  Fix race condition due to statement leak which leads the PostgreSQL
>>>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>>>
>>>>  Resolve issues where a filter condition may lead to a runtime error
>>>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>>>> (W17CX2) (PDR6622)
>>>>
>>>>  Correct the XbpTreeView class so that tree view items can be
>>>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>>>
>>>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>>>> configuring the navigational behavior of all browse objects.
>>>> (xppdui.dll) (W17CXH) (PDR6873)
>>>>
>>>>  Resolve IDSC or stall with 1-digit port in connection string of
>>>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ)
>>>> (PDR6861)
>>>>
>>>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>>>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>>>
>>>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>>>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>>>
>>>>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
>>>> (W17CXN) (PDR6847)
>>>>
>>>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>>>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>>>
>>>>  Fix issue with default precision handling for aggregate results. Add
>>>> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
>>>> (PDR6824)
>>>>
>>>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>>>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>>>
>>>>  Resolve issue with wrong record number in empty workarea if all
>>>> records
>>>> get filtered out by the FOR expression of the current order. Extend
>>>> unit
>>>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>>>
>>>>  Resolve issues where OrdListRebuild() may run into an internal error
>>>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>>>
>>>>  Fix the issue where creating an index with same name as an open index
>>>> yields error while the PGDBE is trying to update the seek procedure.
>>>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>>>
>>>>  Correct the PostgreSQL documentation regarding the numeric precision
>>>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>>>
>>>>  Resolve the issues where adding an index tag to an existing bag leads
>>>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>>>> (PDR6801)
>>>>
>>>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>>>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>>>
>>>>  Ensure the debugger tool tips are displayed correctly when using the
>>>> "Adjust the size of text and other display items" system option under
>>>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>>>
>>>>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
>>>> causes an error message to appear ("canvas drawing error") when
>>>> building
>>>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>>>
>>>>  Correct the example code in the "Using northwind programmatically"
>>>> programming guide chapter in the PGDBE documentation: the session
>>>> object
>>>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>>>> (W16CTR)
>>>>
>>>>  Output a warning when attempting to load executables containing name
>>>> tokens such as "install" or "setup" into the debugger. This is required
>>>> as Windows handles executables with these names differently and may not
>>>> allow debugging. (xppworkbench.exe) (W16CUR)
>>>>
>>>>  Correct product sample readme files to conform to the specifications
>>>> regarding content and format. (samples) (W16CWP)
>>>>
>>>>  Reduce flicker in the context windows of the debugger when stepping
>>>> through the code. The callstack window, for example, flickers
>>>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>>>
>>>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>>>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>>>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Build 2.00.769 (closed workitems)
>>>> New features Maintain asac.log in the users documents\xbase++\.logs
>>>> folder. (xppworkbench.exe) (W16CTQ)
>>>>
>>>>  Ensure that all datatypes from types.ch are properly supported by the
>>>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>>>
>>>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>>>> to describe the rationale behind the sample. (samples) (W16CU7)
>>>>
>>>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>>>> ensure that called code is not affecting FPU status of the Xbase++
>>>> application. (xpprt1.dll) (W16CUB)
>>>>
>>>> Fixes/Changes Investigate and resolve issue why halting a running
>>>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>>>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>>>
>>>>  Correct runtime FPU control word management so that calls to
>>>> misbehaving API or printer driver code does not affect rounding
>>>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>>>
>>>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>>>> operated with the finger, even after tapping the data area of the
>>>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>>>
>>>>  Correct the XbpQuickBrowse class so that it works correctly with a
>>>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>>>
>>>>  Correct the XbpToolBar class so that no runtime error occurs when the
>>>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>>>
>>>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>>>> are reset after communicating with a printer driver. (xppui1.dll)
>>>> (W16CTX) (PDR6854)
>>>>
>>>>  Correct the XbpHTMLStyle class so that the output is positioned
>>>> correctly when used in conjunction with the XbpComboBox class.
>>>> (xppwui.dll) (W16CU2) (PDR6860)
>>>>
>>>>  Correct the issue in the Workbench debugger which may cause runtime
>>>> errors in the IDE after resuming the client application after stopping
>>>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>>>
>>>>  Correct the Workbench debugger so that executables can be debugged
>>>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>>>> (W16CUH) (PDR6639)
>>>>
>>>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>>>> suite to ensure correct behaviour according to SQLite spec./doc.
>>>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>>>
>>>>  Resolve issue where SQL SELECT operations against local tables may
>>>> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
>>>> (W16CUK) (PDR6762)
>>>>
>>>>  The header files in the auto-dependency section must be normalized
>>>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>>>
>>>>  Resolve DACSqlStatement: No instances allowed for this class error and
>>>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>>>> (W16CUQ) (PDR6815)
>>>>
>>>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>>>> (PDR6757)
>>>>
>>>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>>>> XbpCommandButton are converted to ANSI when the application uses an OEM
>>>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U)
>>>> (PDR6712)
>>>>
>>>>  Remove the commandline switch /rc from the resource compiler
>>>> executable
>>>> and documentation. (arc.exe) (W16CT2)
>>>>
>>>>  Validate for the correct interface when a XmlMapper is passed as
>>>> second
>>>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>>>
>>>>  Correct the source code sample in the chapter "Programmatic
>>>> reference -
>>>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>>>
>>>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>>>> array for fieldcount 1 - N and an empty array for an empty result set.
>>>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>>>
>>>>  Review USQL unit tests with respect to the revised type system and
>>>> ensure that the core types are properly validated. (adac20b.dll)
>>>> (W16CUX)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Build 2.00.762 (closed workitems)
>>>> New features Add alternative interfaces for loading images used in the
>>>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>>>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll)
>>>> (W16CJT)
>>>>
>>>>  Ensure the project manager restores the collapse/expand state.
>>>> (xppworkbench.exe) (W16CND)
>>>>
>>>>  Extend Workbench pre-defined macros to support all directories from
>>>> the
>>>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>>>
>>>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types.
>>>> Extend
>>>> the unit-test to cover the entire range of possible values as
>>>> parameter,
>>>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>>>
>>>>  Add a function BinaryName() to identify the execution context. The
>>>> function returns the name of the binary (exe or dll) executing the
>>>> function. (xpprt1.dll) (W16CNX)
>>>>
>>>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
>>>> unit-test to cover the entire range of possible values as parameter,
>>>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>>>
>>>>  Add a control for indicating busy state to the Xbase++ Workbench.
>>>> (xppworkbench.exe) (W16CQB)
>>>>
>>>>  The workbench must maintain logfiles in the user's documents folder
>>>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>>>> (xppworkbench.exe) (W16CRW)
>>>>
>>>>  Add optional feature "Asset Repository" to the installation package.
>>>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>>>> done to the users documents folder "Xbase++\.assets". (xpp*.msi)
>>>> (W16CH3)
>>>>
>>>> Fixes/Changes Add a resource setting to configure round() behavior
>>>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>>>
>>>>  Ensure that mails containing a line starting with a dot are send
>>>> completly instead of as a fragment by the SmtpClient class. See PDR
>>>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>>>
>>>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>>>> presentation parameter when computing the position of the header and
>>>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>>>
>>>>  Fix handle leak in PGDBE when performing SELECT queries and extend the
>>>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>>>> (PDR6834)
>>>>
>>>>  Highlight new content in the documentation using the color dark red.
>>>> (xppref.css) (W16CJR)
>>>>
>>>>  Ensure the XbpImageListBox control conforms to our coding style.
>>>> (asset) (W16CL2)
>>>>
>>>>  Ensure that asget writes error messages to stdout. This enables the
>>>> workbench to display the error message. (asget.exe) (W16CL7)
>>>>
>>>>  Extend exisiting Workbench template mechanism in such a way that new
>>>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>>>
>>>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and
>>>> associated
>>>> files conform to our coding style. (asset) (W16CLC)
>>>>
>>>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>>>> style. (asset) (W16CLH)
>>>>
>>>>  Ensure the XbpCommandButton class and related files conform to our
>>>> coding style. (asset) (W16CLJ)
>>>>
>>>>  Ensure the XbpCheckedListBox class and related files conform to our
>>>> coding style. (asset) (W16CN1)
>>>>
>>>>  Ensure the dialog for managing target-specific assets remembers its
>>>> current size and position, as well as splitbar position.
>>>> (xppworkbench.exe) (W16CN2)
>>>>
>>>>  Ensure the "New Items" dialog remembers its current size and position
>>>> (xppworkbench.exe) (W16CN3)
>>>>
>>>>  Create and add import definition for VFP modernizer to Workbench
>>>> (xppworkbench.exe) (W16CNC)
>>>>
>>>>  Change "New items" dialog so that the view style (large icons etc.) is
>>>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>>>
>>>>  Modify the event management sample in the CXP sample collection so
>>>> that
>>>> it uses the POST verb for transferring data, eg. when saving events.
>>>> (alaska-software.webui.js) (W16CP1)
>>>>
>>>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>>>> control. (asset) (W16CP4)
>>>>
>>>>  Extend the styled list box example for the XbpHTMLStyle class so that
>>>> it better illustrates the usage of the WebUI for customizing an
>>>> existing
>>>> Xbase Part. (samples) (W16CP7)
>>>>
>>>>  Ensure the XbpToggleButton class and related files conform to our
>>>> coding style. (asset) (W16CPA)
>>>>
>>>>  Correct the htmlhelp.exe example so that it displays context-sensitive
>>>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>>>
>>>>  Ensure the new project manager target nodes are expanded by default.
>>>> (xwbassochlp20.dll) (W16CPD)
>>>>
>>>>  Reorganize the closed workitems list in such a way that new features
>>>> and changes are shown first followed by the list of fixes/corrections
>>>> (changes20.chm) (W16CPL)
>>>>
>>>>  Ensure that ALINK is able to handle long import library names
>>>> identical
>>>> in the first 16 chars. (alink.exe) (W16CPQ)
>>>>
>>>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>>>> the XbpColumn class init state needs to be independent from module init
>>>> state. (xppdui.dll) (W16CPY)
>>>>
>>>>  Use global busy indicator when build is in progress.
>>>> (xppworkbench.exe)
>>>> (W16CQ1)
>>>>
>>>>  Update "conventions" section in the reference documentation: changes
>>>> are highlighted in red. (convent20.chm) (W16CRQ)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>>>> Hallo,
>>>>>
>>>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich
>>>>> aber
>>>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>>
>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>>
>>>>>
>>>>> Markus
>>>>
>>

Hallo Frank,

2007 war die Devcon in Berlin, und da war das auf der 
Abschlußveranstaltung. Deswegen weiß ich das halt noch. Hab mich nur 
vertippt ... 

Und ja, ich weiß das die ganze Geschichte bei Euch inzwischen 
automatisiert wurde. Irgendeiner der anderen Drei hat mir das mal 
erzählt vor zwei Jahren oder so. Ich fand das damals einfach nur genial.

Jan

Am 06.04.2017 um 19:03 schrieb Frank Grossheinrich:
> Kannst du dir wirklich solche Jahreszahlen merken? 2008?
> Wie dem auch sei, CDI hat uns locker 2 Jahre an Arbeit gekostet. Das ist 
> ja nicht nur, dass wir Updates bereitstellen, sondern dahinter steckt ja 
> eine komplette Infrastruktur. Das fängt vom Build-Prozessor an (also das 
> Ding, das Xbase++ und all seine Komponenten zusammenbaut) bis hin zum 
> Packaging und Deployment. Ganz ehrlich: wir machen da nix mehr von Hand. 
> Das ist alles automatisiert (leider noch nicht das PDR Fixing ). Und 
> das war eine gewaltige Aufgabe.
> 
> Und auch wir freuen uns, dass wir uns die Zeit dafür genommen haben, 
> denn es macht Dinge einfacher und macht uns flexibler. Und hilft unseren 
> Kunden.
> 
> "Als Markus das schrieb" waren auch schon einige Updates verfügbar. Ich 
> habe gerade nachgeschaut: das waren seit Erscheinen der Version 2.0 5 
> Updates bis zum Post. Also so schlecht hat das nicht ausgesehen. Auch 
> wenn ich die Zweifel manchmal verstehe.
> 
> Gruß, ich
> 
> 
> On 04.04.2017 20:45, Jan Escholt wrote:
>> Hallo Frank,
>>
>> versteh mich bitte nicht falsch. Ich bin durchaus sehr einverstanden mit
>> Eurer CDI. Steffen hatte mir schon 2008 in Berlin vor versammelter
>> Mannschaft zugesichert, das die Rhythmen der Fixes kürzer werden würden.
>> Und wir wissen beide, was passiert ist. Es hat sich nämlich garnichts
>> geändert danach. Jetzt mit CDI ist das vielleicht nicht so schnell wie
>> gewünscht (die Ansprüche steigen halt), und viele Punkte sind überhaupt
>> nichts für mich, aber ja, wenn das so weitergeht wie die letzten Monate,
>> dann bin ich durchaus zufrieden damit.
>>
>> Aber damals, als Markus das schrieb, war das noch in keinster Weise
>> absehbar, was da kommen würde. Du hast zwar unten eine lange Latte von
>> abgearbeiteten Punkten zitiert, und das will ich auch nicht klein reden.
>> Aber auch die Abstände zwischen einzelnen Updates im CDI waren
>> zwischendurch immer mal nicht von schlechten Eltern - und das meine ich
>> nicht positiv. Es scheint sich jetzt ganz wesentlich zu bessern. Aber
>> zum zum Zeitpunkt der Threaderöfffnung war das halt noch nicht absehbar,
>> da war gerade nach 6monatiger Pause gerade ein Update erschienen. Was
>> nicht den damals von Alaska kommunizierten Ansprüchen entsprach.
>>
>> Jan
>>
>> Am 04.04.2017 um 18:08 schrieb Frank Grossheinrich:
>>> Hey Jan,
>>>
>>> ja, das kam spät von mir.
>>> Aber ich konnte das nicht so stehen lassen.
>>> Und ich hatte mir extra das Kundenkonto vorher angeschaut.
>>>
>>> Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht
>>> definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
>>> Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre
>>> etwas passiert. CDI macht es anders. Es geht hier auch nicht um die
>>> Frequenz. Sondern vorher haben wir immer gewartet und gewartet und
>>> gewartet und noch dieses Feature dran gemacht und noch das Schleifchen.
>>> Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben
>>> Feature-Grades ("Reifezustand" eines Features), ...
>>>
>>> Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.
>>>
>>> Anyhow, CDI war ein wichtiger Schritt.
>>> Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen
>>> noch weiter helfen. Und und und ...
>>>
>>> Bis bald,
>>>
>>> Frank
>>>
>>>
>>> On 31.03.2017 22:24, Jan Escholt wrote:
>>>> Hallo Frank,
>>>>
>>>> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
>>>> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
>>>> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
>>>> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
>>>> den Kommentar von Markus durchaus verstehen.
>>>>
>>>> Jan
>>>>
>>>> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>>>>> Hallo Markus,
>>>>>
>>>>> ich habe heute meinen "ich lese mal quer" Tag ...
>>>>> So bin ich über diese Frage gestolpert.
>>>>>
>>>>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>>>>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>>>>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>>>>
>>>>> Aber
>>>>>> Auch das mit 2.0 eingeführte
>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>>>>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>>>>
>>>>> In jedem Update gab es Erweiterungen, Neuerungen und 
>>>>> Problembehebungen.
>>>>>
>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend
>>>>> ist
>>>>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem
>>>>> Windowsn
>>>>> Aniversary Update "nur" in einem Update ohne Versionssprung
>>>>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>>>>
>>>>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen
>>>>> anzuschauen
>>>>> und das hast bisher versäumt: siehe unten.
>>>>>
>>>>> Das hast du alles verpasst.
>>>>>
>>>>> Gruß, Frank
>>>>>
>>>>>
>>>>> Build 2.00.779 (closed workitems)
>>>>> New features Add function DbDestroy() to the data-definition-language
>>>>> (DDL) to delete an ISAM emulating table programmatically by the
>>>>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>>>>
>>>>> Fixes/Changes Correct the calculation of the the column widths of the
>>>>> grids displayed in the debugger's auxilliary views. These may become
>>>>> smaller as the views get refreshed in a debugging session.
>>>>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>>>>
>>>>>  Correct debugger issue where debugging codeblocks and inspecting
>>>>> variable values crashes the client application and/or the debugger.
>>>>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>>>>
>>>>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>>>>> calling context halt the debuggee after the STEP BACK (step out)
>>>>> command
>>>>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>>>>
>>>>>  Resolve issue where a replace operation may force a runtime error
>>>>> right
>>>>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>>>>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>>>>
>>>>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>>>>> reference parameter types. If passed by value, only character, object
>>>>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>>>>> (W16CWQ) (PDR6864)
>>>>>
>>>>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>>>>> that execution halts in the current context if the context was called
>>>>> recursively. Currently, the debuggee is halted only after the 
>>>>> recursion
>>>>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>>>>
>>>>>  Correct the debugger kernel so that a "step into" command stops the
>>>>> debuggee in the calling function or method if the current line 
>>>>> contains
>>>>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>>>>
>>>>>  Correct the callstack view in the Workbench debugger so that the
>>>>> current context (callstack level) is indicated correctly, even when
>>>>> debugging a function that is calling itself recursively.
>>>>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>>>>
>>>>>  Correct the "step over" debugger command so that execution indeed
>>>>> stops
>>>>> after the current line when the cursor is on a line calling the 
>>>>> current
>>>>> procedure recursively. Currently, the "step over" command behaves 
>>>>> as if
>>>>> "step into" was executed, and execution stops in the first line of the
>>>>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>>>>
>>>>>  Fix race condition due to statement leak which leads the PostgreSQL
>>>>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>>>>
>>>>>  Resolve issues where a filter condition may lead to a runtime error
>>>>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>>>>> (W17CX2) (PDR6622)
>>>>>
>>>>>  Correct the XbpTreeView class so that tree view items can be
>>>>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>>>>
>>>>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>>>>> configuring the navigational behavior of all browse objects.
>>>>> (xppdui.dll) (W17CXH) (PDR6873)
>>>>>
>>>>>  Resolve IDSC or stall with 1-digit port in connection string of
>>>>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ)
>>>>> (PDR6861)
>>>>>
>>>>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>>>>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>>>>
>>>>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>>>>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>>>>
>>>>>  Fix invalid return value of DacSession():executeQuery(). 
>>>>> (adac20b.dll)
>>>>> (W17CXN) (PDR6847)
>>>>>
>>>>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>>>>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>>>>
>>>>>  Fix issue with default precision handling for aggregate results. Add
>>>>> unit test to cover aggregate result type handling. (pgdbe.dll) 
>>>>> (W17CXQ)
>>>>> (PDR6824)
>>>>>
>>>>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>>>>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>>>>
>>>>>  Resolve issue with wrong record number in empty workarea if all
>>>>> records
>>>>> get filtered out by the FOR expression of the current order. Extend
>>>>> unit
>>>>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>>>>
>>>>>  Resolve issues where OrdListRebuild() may run into an internal error
>>>>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>>>>
>>>>>  Fix the issue where creating an index with same name as an open index
>>>>> yields error while the PGDBE is trying to update the seek procedure.
>>>>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>>>>
>>>>>  Correct the PostgreSQL documentation regarding the numeric precision
>>>>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>>>>
>>>>>  Resolve the issues where adding an index tag to an existing bag leads
>>>>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>>>>> (PDR6801)
>>>>>
>>>>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>>>>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>>>>
>>>>>  Ensure the debugger tool tips are displayed correctly when using the
>>>>> "Adjust the size of text and other display items" system option under
>>>>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>>>>
>>>>>  Investigate and fix the issue in the Xbase++ Workbench which 
>>>>> sometimes
>>>>> causes an error message to appear ("canvas drawing error") when
>>>>> building
>>>>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>>>>
>>>>>  Correct the example code in the "Using northwind programmatically"
>>>>> programming guide chapter in the PGDBE documentation: the session
>>>>> object
>>>>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>>>>> (W16CTR)
>>>>>
>>>>>  Output a warning when attempting to load executables containing name
>>>>> tokens such as "install" or "setup" into the debugger. This is 
>>>>> required
>>>>> as Windows handles executables with these names differently and may 
>>>>> not
>>>>> allow debugging. (xppworkbench.exe) (W16CUR)
>>>>>
>>>>>  Correct product sample readme files to conform to the specifications
>>>>> regarding content and format. (samples) (W16CWP)
>>>>>
>>>>>  Reduce flicker in the context windows of the debugger when stepping
>>>>> through the code. The callstack window, for example, flickers
>>>>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>>>>
>>>>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>>>>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>>>>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Build 2.00.769 (closed workitems)
>>>>> New features Maintain asac.log in the users documents\xbase++\.logs
>>>>> folder. (xppworkbench.exe) (W16CTQ)
>>>>>
>>>>>  Ensure that all datatypes from types.ch are properly supported by the
>>>>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>>>>
>>>>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>>>>> to describe the rationale behind the sample. (samples) (W16CU7)
>>>>>
>>>>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>>>>> ensure that called code is not affecting FPU status of the Xbase++
>>>>> application. (xpprt1.dll) (W16CUB)
>>>>>
>>>>> Fixes/Changes Investigate and resolve issue why halting a running
>>>>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>>>>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>>>>
>>>>>  Correct runtime FPU control word management so that calls to
>>>>> misbehaving API or printer driver code does not affect rounding
>>>>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>>>>
>>>>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>>>>> operated with the finger, even after tapping the data area of the
>>>>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>>>>
>>>>>  Correct the XbpQuickBrowse class so that it works correctly with a
>>>>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>>>>
>>>>>  Correct the XbpToolBar class so that no runtime error occurs when the
>>>>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>>>>
>>>>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>>>>> are reset after communicating with a printer driver. (xppui1.dll)
>>>>> (W16CTX) (PDR6854)
>>>>>
>>>>>  Correct the XbpHTMLStyle class so that the output is positioned
>>>>> correctly when used in conjunction with the XbpComboBox class.
>>>>> (xppwui.dll) (W16CU2) (PDR6860)
>>>>>
>>>>>  Correct the issue in the Workbench debugger which may cause runtime
>>>>> errors in the IDE after resuming the client application after stopping
>>>>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>>>>
>>>>>  Correct the Workbench debugger so that executables can be debugged
>>>>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>>>>> (W16CUH) (PDR6639)
>>>>>
>>>>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>>>>> suite to ensure correct behaviour according to SQLite spec./doc.
>>>>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>>>>
>>>>>  Resolve issue where SQL SELECT operations against local tables may
>>>>> cause a runtime error (internal datastructures corrupted) 
>>>>> (adac20b.dll)
>>>>> (W16CUK) (PDR6762)
>>>>>
>>>>>  The header files in the auto-dependency section must be normalized
>>>>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>>>>
>>>>>  Resolve DACSqlStatement: No instances allowed for this class error 
>>>>> and
>>>>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>>>>> (W16CUQ) (PDR6815)
>>>>>
>>>>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>>>>> (PDR6757)
>>>>>
>>>>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>>>>> XbpCommandButton are converted to ANSI when the application uses an 
>>>>> OEM
>>>>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U)
>>>>> (PDR6712)
>>>>>
>>>>>  Remove the commandline switch /rc from the resource compiler
>>>>> executable
>>>>> and documentation. (arc.exe) (W16CT2)
>>>>>
>>>>>  Validate for the correct interface when a XmlMapper is passed as
>>>>> second
>>>>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>>>>
>>>>>  Correct the source code sample in the chapter "Programmatic
>>>>> reference -
>>>>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>>>>
>>>>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>>>>> array for fieldcount 1 - N and an empty array for an empty result set.
>>>>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>>>>
>>>>>  Review USQL unit tests with respect to the revised type system and
>>>>> ensure that the core types are properly validated. (adac20b.dll)
>>>>> (W16CUX)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Build 2.00.762 (closed workitems)
>>>>> New features Add alternative interfaces for loading images used in the
>>>>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>>>>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll)
>>>>> (W16CJT)
>>>>>
>>>>>  Ensure the project manager restores the collapse/expand state.
>>>>> (xppworkbench.exe) (W16CND)
>>>>>
>>>>>  Extend Workbench pre-defined macros to support all directories from
>>>>> the
>>>>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>>>>
>>>>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types.
>>>>> Extend
>>>>> the unit-test to cover the entire range of possible values as
>>>>> parameter,
>>>>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>>>>
>>>>>  Add a function BinaryName() to identify the execution context. The
>>>>> function returns the name of the binary (exe or dll) executing the
>>>>> function. (xpprt1.dll) (W16CNX)
>>>>>
>>>>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend 
>>>>> the
>>>>> unit-test to cover the entire range of possible values as parameter,
>>>>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>>>>
>>>>>  Add a control for indicating busy state to the Xbase++ Workbench.
>>>>> (xppworkbench.exe) (W16CQB)
>>>>>
>>>>>  The workbench must maintain logfiles in the user's documents folder
>>>>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>>>>> (xppworkbench.exe) (W16CRW)
>>>>>
>>>>>  Add optional feature "Asset Repository" to the installation package.
>>>>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>>>>> done to the users documents folder "Xbase++\.assets". (xpp*.msi)
>>>>> (W16CH3)
>>>>>
>>>>> Fixes/Changes Add a resource setting to configure round() behavior
>>>>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>>>>
>>>>>  Ensure that mails containing a line starting with a dot are send
>>>>> completly instead of as a fragment by the SmtpClient class. See PDR
>>>>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>>>>
>>>>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>>>>> presentation parameter when computing the position of the header and
>>>>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>>>>
>>>>>  Fix handle leak in PGDBE when performing SELECT queries and extend 
>>>>> the
>>>>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>>>>> (PDR6834)
>>>>>
>>>>>  Highlight new content in the documentation using the color dark red.
>>>>> (xppref.css) (W16CJR)
>>>>>
>>>>>  Ensure the XbpImageListBox control conforms to our coding style.
>>>>> (asset) (W16CL2)
>>>>>
>>>>>  Ensure that asget writes error messages to stdout. This enables the
>>>>> workbench to display the error message. (asget.exe) (W16CL7)
>>>>>
>>>>>  Extend exisiting Workbench template mechanism in such a way that new
>>>>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>>>>
>>>>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and
>>>>> associated
>>>>> files conform to our coding style. (asset) (W16CLC)
>>>>>
>>>>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>>>>> style. (asset) (W16CLH)
>>>>>
>>>>>  Ensure the XbpCommandButton class and related files conform to our
>>>>> coding style. (asset) (W16CLJ)
>>>>>
>>>>>  Ensure the XbpCheckedListBox class and related files conform to our
>>>>> coding style. (asset) (W16CN1)
>>>>>
>>>>>  Ensure the dialog for managing target-specific assets remembers its
>>>>> current size and position, as well as splitbar position.
>>>>> (xppworkbench.exe) (W16CN2)
>>>>>
>>>>>  Ensure the "New Items" dialog remembers its current size and position
>>>>> (xppworkbench.exe) (W16CN3)
>>>>>
>>>>>  Create and add import definition for VFP modernizer to Workbench
>>>>> (xppworkbench.exe) (W16CNC)
>>>>>
>>>>>  Change "New items" dialog so that the view style (large icons 
>>>>> etc.) is
>>>>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>>>>
>>>>>  Modify the event management sample in the CXP sample collection so
>>>>> that
>>>>> it uses the POST verb for transferring data, eg. when saving events.
>>>>> (alaska-software.webui.js) (W16CP1)
>>>>>
>>>>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>>>>> control. (asset) (W16CP4)
>>>>>
>>>>>  Extend the styled list box example for the XbpHTMLStyle class so that
>>>>> it better illustrates the usage of the WebUI for customizing an
>>>>> existing
>>>>> Xbase Part. (samples) (W16CP7)
>>>>>
>>>>>  Ensure the XbpToggleButton class and related files conform to our
>>>>> coding style. (asset) (W16CPA)
>>>>>
>>>>>  Correct the htmlhelp.exe example so that it displays 
>>>>> context-sensitive
>>>>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>>>>
>>>>>  Ensure the new project manager target nodes are expanded by default.
>>>>> (xwbassochlp20.dll) (W16CPD)
>>>>>
>>>>>  Reorganize the closed workitems list in such a way that new features
>>>>> and changes are shown first followed by the list of fixes/corrections
>>>>> (changes20.chm) (W16CPL)
>>>>>
>>>>>  Ensure that ALINK is able to handle long import library names
>>>>> identical
>>>>> in the first 16 chars. (alink.exe) (W16CPQ)
>>>>>
>>>>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>>>>> the XbpColumn class init state needs to be independent from module 
>>>>> init
>>>>> state. (xppdui.dll) (W16CPY)
>>>>>
>>>>>  Use global busy indicator when build is in progress.
>>>>> (xppworkbench.exe)
>>>>> (W16CQ1)
>>>>>
>>>>>  Update "conventions" section in the reference documentation: changes
>>>>> are highlighted in red. (convent20.chm) (W16CRQ)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>>>>> Hallo,
>>>>>>
>>>>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich
>>>>>> aber
>>>>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>>>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>>>
>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>>>
>>>>>>
>>>>>> Markus
>>>>>
>>>
>

Hallo Frank,

einen Wunsch htte ich fr die Updates des CDI.

Man mchte bitte ein Update auch als solches installieren und nicht jedes Mal
die alte Version deinstallieren, da wir hufig genutzte Libs und Includes
direkt in das passende Alaska-Verzeichnis legen, fehlen diese nach jedem
"Update". Und wenn man mal eine Sekunde nicht daran denkt, produziert der
Linker/Compiler gleich mal eine Palette an Fehlern. Zumindest knnte
nutzergenerierter Inhalt dort liegen bleiben.

Gru
Michael


On 06.04.2017 19:03:30,  wrote:
> Kannst du dir wirklich solche Jahreszahlen merken? 2008?
> Wie dem auch sei, CDI hat uns locker 2 Jahre an Arbeit gekostet. Das ist
> ja nicht nur, dass wir Updates bereitstellen, sondern dahinter steckt ja
> eine komplette Infrastruktur. Das fängt vom Build-Prozessor an (also das
> Ding, das Xbase++ und all seine Komponenten zusammenbaut) bis hin zum
> Packaging und Deployment. Ganz ehrlich: wir machen da nix mehr von Hand.
> Das ist alles automatisiert (leider noch nicht das PDR Fixing ). Und
> das war eine gewaltige Aufgabe.
> 
> Und auch wir freuen uns, dass wir uns die Zeit dafür genommen haben,
> denn es macht Dinge einfacher und macht uns flexibler. Und hilft unseren
> Kunden.
> 
> "Als Markus das schrieb" waren auch schon einige Updates verfügbar. Ich
> habe gerade nachgeschaut: das waren seit Erscheinen der Version 2.0 5
> Updates bis zum Post. Also so schlecht hat das nicht ausgesehen. Auch
> wenn ich die Zweifel manchmal verstehe.
> 
> Gruß, ich
> 
> 
> On 04.04.2017 20:45, Jan Escholt wrote:
>> Hallo Frank,
>>
>> versteh mich bitte nicht falsch. Ich bin durchaus sehr einverstanden mit
>> Eurer CDI. Steffen hatte mir schon 2008 in Berlin vor versammelter
>> Mannschaft zugesichert, das die Rhythmen der Fixes kürzer werden würden.
>> Und wir wissen beide, was passiert ist. Es hat sich nämlich garnichts
>> geändert danach. Jetzt mit CDI ist das vielleicht nicht so schnell wie
>> gewünscht (die Ansprüche steigen halt), und viele Punkte sind überhaupt
>> nichts für mich, aber ja, wenn das so weitergeht wie die letzten Monate,
>> dann bin ich durchaus zufrieden damit.
>>
>> Aber damals, als Markus das schrieb, war das noch in keinster Weise
>> absehbar, was da kommen würde. Du hast zwar unten eine lange Latte von
>> abgearbeiteten Punkten zitiert, und das will ich auch nicht klein reden.
>> Aber auch die Abstände zwischen einzelnen Updates im CDI waren
>> zwischendurch immer mal nicht von schlechten Eltern - und das meine ich
>> nicht positiv. Es scheint sich jetzt ganz wesentlich zu bessern. Aber
>> zum zum Zeitpunkt der Threaderöfffnung war das halt noch nicht absehbar,
>> da war gerade nach 6monatiger Pause gerade ein Update erschienen. Was
>> nicht den damals von Alaska kommunizierten Ansprüchen entsprach.
>>
>> Jan
>>
>> Am 04.04.2017 um 18:08 schrieb Frank Grossheinrich:
>>> Hey Jan,
>>>
>>> ja, das kam spät von mir.
>>> Aber ich konnte das nicht so stehen lassen.
>>> Und ich hatte mir extra das Kundenkonto vorher angeschaut.
>>>
>>> Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht
>>> definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
>>> Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre
>>> etwas passiert. CDI macht es anders. Es geht hier auch nicht um die
>>> Frequenz. Sondern vorher haben wir immer gewartet und gewartet und
>>> gewartet und noch dieses Feature dran gemacht und noch das Schleifchen.
>>> Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben
>>> Feature-Grades ("Reifezustand" eines Features), ...
>>>
>>> Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.
>>>
>>> Anyhow, CDI war ein wichtiger Schritt.
>>> Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen
>>> noch weiter helfen. Und und und ...
>>>
>>> Bis bald,
>>>
>>> Frank
>>>
>>>
>>> On 31.03.2017 22:24, Jan Escholt wrote:
>>>> Hallo Frank,
>>>>
>>>> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
>>>> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
>>>> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
>>>> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
>>>> den Kommentar von Markus durchaus verstehen.
>>>>
>>>> Jan
>>>>
>>>> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>>>>> Hallo Markus,
>>>>>
>>>>> ich habe heute meinen "ich lese mal quer" Tag ...
>>>>> So bin ich über diese Frage gestolpert.
>>>>>
>>>>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>>>>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>>>>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>>>>
>>>>> Aber
>>>>>> Auch das mit 2.0 eingeführte
>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>>>>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>>>>
>>>>> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>>>>>
>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend
>>>>> ist
>>>>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem
>>>>> Windowsn
>>>>> Aniversary Update "nur" in einem Update ohne Versionssprung
>>>>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>>>>
>>>>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen
>>>>> anzuschauen
>>>>> und das hast bisher versäumt: siehe unten.
>>>>>
>>>>> Das hast du alles verpasst.
>>>>>
>>>>> Gruß, Frank
>>>>>
>>>>>
>>>>> Build 2.00.779 (closed workitems)
>>>>> New features Add function DbDestroy() to the data-definition-language
>>>>> (DDL) to delete an ISAM emulating table programmatically by the
>>>>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>>>>
>>>>> Fixes/Changes Correct the calculation of the the column widths of the
>>>>> grids displayed in the debugger's auxilliary views. These may become
>>>>> smaller as the views get refreshed in a debugging session.
>>>>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>>>>
>>>>>  Correct debugger issue where debugging codeblocks and inspecting
>>>>> variable values crashes the client application and/or the debugger.
>>>>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>>>>
>>>>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>>>>> calling context halt the debuggee after the STEP BACK (step out)
>>>>> command
>>>>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>>>>
>>>>>  Resolve issue where a replace operation may force a runtime error
>>>>> right
>>>>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>>>>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>>>>
>>>>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>>>>> reference parameter types. If passed by value, only character, object
>>>>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>>>>> (W16CWQ) (PDR6864)
>>>>>
>>>>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>>>>> that execution halts in the current context if the context was called
>>>>> recursively. Currently, the debuggee is halted only after the recursion
>>>>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>>>>
>>>>>  Correct the debugger kernel so that a "step into" command stops the
>>>>> debuggee in the calling function or method if the current line contains
>>>>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>>>>
>>>>>  Correct the callstack view in the Workbench debugger so that the
>>>>> current context (callstack level) is indicated correctly, even when
>>>>> debugging a function that is calling itself recursively.
>>>>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>>>>
>>>>>  Correct the "step over" debugger command so that execution indeed
>>>>> stops
>>>>> after the current line when the cursor is on a line calling the current
>>>>> procedure recursively. Currently, the "step over" command behaves as if
>>>>> "step into" was executed, and execution stops in the first line of the
>>>>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>>>>
>>>>>  Fix race condition due to statement leak which leads the PostgreSQL
>>>>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>>>>
>>>>>  Resolve issues where a filter condition may lead to a runtime error
>>>>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>>>>> (W17CX2) (PDR6622)
>>>>>
>>>>>  Correct the XbpTreeView class so that tree view items can be
>>>>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>>>>
>>>>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>>>>> configuring the navigational behavior of all browse objects.
>>>>> (xppdui.dll) (W17CXH) (PDR6873)
>>>>>
>>>>>  Resolve IDSC or stall with 1-digit port in connection string of
>>>>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ)
>>>>> (PDR6861)
>>>>>
>>>>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>>>>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>>>>
>>>>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>>>>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>>>>
>>>>>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
>>>>> (W17CXN) (PDR6847)
>>>>>
>>>>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>>>>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>>>>
>>>>>  Fix issue with default precision handling for aggregate results. Add
>>>>> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
>>>>> (PDR6824)
>>>>>
>>>>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>>>>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>>>>
>>>>>  Resolve issue with wrong record number in empty workarea if all
>>>>> records
>>>>> get filtered out by the FOR expression of the current order. Extend
>>>>> unit
>>>>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>>>>
>>>>>  Resolve issues where OrdListRebuild() may run into an internal error
>>>>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>>>>
>>>>>  Fix the issue where creating an index with same name as an open index
>>>>> yields error while the PGDBE is trying to update the seek procedure.
>>>>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>>>>
>>>>>  Correct the PostgreSQL documentation regarding the numeric precision
>>>>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>>>>
>>>>>  Resolve the issues where adding an index tag to an existing bag leads
>>>>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>>>>> (PDR6801)
>>>>>
>>>>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>>>>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>>>>
>>>>>  Ensure the debugger tool tips are displayed correctly when using the
>>>>> "Adjust the size of text and other display items" system option under
>>>>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>>>>
>>>>>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
>>>>> causes an error message to appear ("canvas drawing error") when
>>>>> building
>>>>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>>>>
>>>>>  Correct the example code in the "Using northwind programmatically"
>>>>> programming guide chapter in the PGDBE documentation: the session
>>>>> object
>>>>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>>>>> (W16CTR)
>>>>>
>>>>>  Output a warning when attempting to load executables containing name
>>>>> tokens such as "install" or "setup" into the debugger. This is required
>>>>> as Windows handles executables with these names differently and may not
>>>>> allow debugging. (xppworkbench.exe) (W16CUR)
>>>>>
>>>>>  Correct product sample readme files to conform to the specifications
>>>>> regarding content and format. (samples) (W16CWP)
>>>>>
>>>>>  Reduce flicker in the context windows of the debugger when stepping
>>>>> through the code. The callstack window, for example, flickers
>>>>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>>>>
>>>>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>>>>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>>>>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Build 2.00.769 (closed workitems)
>>>>> New features Maintain asac.log in the users documents\xbase++\.logs
>>>>> folder. (xppworkbench.exe) (W16CTQ)
>>>>>
>>>>>  Ensure that all datatypes from types.ch are properly supported by the
>>>>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>>>>
>>>>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>>>>> to describe the rationale behind the sample. (samples) (W16CU7)
>>>>>
>>>>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>>>>> ensure that called code is not affecting FPU status of the Xbase++
>>>>> application. (xpprt1.dll) (W16CUB)
>>>>>
>>>>> Fixes/Changes Investigate and resolve issue why halting a running
>>>>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>>>>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>>>>
>>>>>  Correct runtime FPU control word management so that calls to
>>>>> misbehaving API or printer driver code does not affect rounding
>>>>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>>>>
>>>>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>>>>> operated with the finger, even after tapping the data area of the
>>>>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>>>>
>>>>>  Correct the XbpQuickBrowse class so that it works correctly with a
>>>>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>>>>
>>>>>  Correct the XbpToolBar class so that no runtime error occurs when the
>>>>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>>>>
>>>>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>>>>> are reset after communicating with a printer driver. (xppui1.dll)
>>>>> (W16CTX) (PDR6854)
>>>>>
>>>>>  Correct the XbpHTMLStyle class so that the output is positioned
>>>>> correctly when used in conjunction with the XbpComboBox class.
>>>>> (xppwui.dll) (W16CU2) (PDR6860)
>>>>>
>>>>>  Correct the issue in the Workbench debugger which may cause runtime
>>>>> errors in the IDE after resuming the client application after stopping
>>>>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>>>>
>>>>>  Correct the Workbench debugger so that executables can be debugged
>>>>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>>>>> (W16CUH) (PDR6639)
>>>>>
>>>>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>>>>> suite to ensure correct behaviour according to SQLite spec./doc.
>>>>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>>>>
>>>>>  Resolve issue where SQL SELECT operations against local tables may
>>>>> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
>>>>> (W16CUK) (PDR6762)
>>>>>
>>>>>  The header files in the auto-dependency section must be normalized
>>>>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>>>>
>>>>>  Resolve DACSqlStatement: No instances allowed for this class error and
>>>>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>>>>> (W16CUQ) (PDR6815)
>>>>>
>>>>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>>>>> (PDR6757)
>>>>>
>>>>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>>>>> XbpCommandButton are converted to ANSI when the application uses an OEM
>>>>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U)
>>>>> (PDR6712)
>>>>>
>>>>>  Remove the commandline switch /rc from the resource compiler
>>>>> executable
>>>>> and documentation. (arc.exe) (W16CT2)
>>>>>
>>>>>  Validate for the correct interface when a XmlMapper is passed as
>>>>> second
>>>>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>>>>
>>>>>  Correct the source code sample in the chapter "Programmatic
>>>>> reference -
>>>>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>>>>
>>>>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>>>>> array for fieldcount 1 - N and an empty array for an empty result set.
>>>>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>>>>
>>>>>  Review USQL unit tests with respect to the revised type system and
>>>>> ensure that the core types are properly validated. (adac20b.dll)
>>>>> (W16CUX)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Build 2.00.762 (closed workitems)
>>>>> New features Add alternative interfaces for loading images used in the
>>>>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>>>>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll)
>>>>> (W16CJT)
>>>>>
>>>>>  Ensure the project manager restores the collapse/expand state.
>>>>> (xppworkbench.exe) (W16CND)
>>>>>
>>>>>  Extend Workbench pre-defined macros to support all directories from
>>>>> the
>>>>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>>>>
>>>>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types.
>>>>> Extend
>>>>> the unit-test to cover the entire range of possible values as
>>>>> parameter,
>>>>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>>>>
>>>>>  Add a function BinaryName() to identify the execution context. The
>>>>> function returns the name of the binary (exe or dll) executing the
>>>>> function. (xpprt1.dll) (W16CNX)
>>>>>
>>>>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
>>>>> unit-test to cover the entire range of possible values as parameter,
>>>>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>>>>
>>>>>  Add a control for indicating busy state to the Xbase++ Workbench.
>>>>> (xppworkbench.exe) (W16CQB)
>>>>>
>>>>>  The workbench must maintain logfiles in the user's documents folder
>>>>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>>>>> (xppworkbench.exe) (W16CRW)
>>>>>
>>>>>  Add optional feature "Asset Repository" to the installation package.
>>>>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>>>>> done to the users documents folder "Xbase++\.assets". (xpp*.msi)
>>>>> (W16CH3)
>>>>>
>>>>> Fixes/Changes Add a resource setting to configure round() behavior
>>>>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>>>>
>>>>>  Ensure that mails containing a line starting with a dot are send
>>>>> completly instead of as a fragment by the SmtpClient class. See PDR
>>>>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>>>>
>>>>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>>>>> presentation parameter when computing the position of the header and
>>>>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>>>>
>>>>>  Fix handle leak in PGDBE when performing SELECT queries and extend the
>>>>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>>>>> (PDR6834)
>>>>>
>>>>>  Highlight new content in the documentation using the color dark red.
>>>>> (xppref.css) (W16CJR)
>>>>>
>>>>>  Ensure the XbpImageListBox control conforms to our coding style.
>>>>> (asset) (W16CL2)
>>>>>
>>>>>  Ensure that asget writes error messages to stdout. This enables the
>>>>> workbench to display the error message. (asget.exe) (W16CL7)
>>>>>
>>>>>  Extend exisiting Workbench template mechanism in such a way that new
>>>>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>>>>
>>>>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and
>>>>> associated
>>>>> files conform to our coding style. (asset) (W16CLC)
>>>>>
>>>>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>>>>> style. (asset) (W16CLH)
>>>>>
>>>>>  Ensure the XbpCommandButton class and related files conform to our
>>>>> coding style. (asset) (W16CLJ)
>>>>>
>>>>>  Ensure the XbpCheckedListBox class and related files conform to our
>>>>> coding style. (asset) (W16CN1)
>>>>>
>>>>>  Ensure the dialog for managing target-specific assets remembers its
>>>>> current size and position, as well as splitbar position.
>>>>> (xppworkbench.exe) (W16CN2)
>>>>>
>>>>>  Ensure the "New Items" dialog remembers its current size and position
>>>>> (xppworkbench.exe) (W16CN3)
>>>>>
>>>>>  Create and add import definition for VFP modernizer to Workbench
>>>>> (xppworkbench.exe) (W16CNC)
>>>>>
>>>>>  Change "New items" dialog so that the view style (large icons etc.) is
>>>>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>>>>
>>>>>  Modify the event management sample in the CXP sample collection so
>>>>> that
>>>>> it uses the POST verb for transferring data, eg. when saving events.
>>>>> (alaska-software.webui.js) (W16CP1)
>>>>>
>>>>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>>>>> control. (asset) (W16CP4)
>>>>>
>>>>>  Extend the styled list box example for the XbpHTMLStyle class so that
>>>>> it better illustrates the usage of the WebUI for customizing an
>>>>> existing
>>>>> Xbase Part. (samples) (W16CP7)
>>>>>
>>>>>  Ensure the XbpToggleButton class and related files conform to our
>>>>> coding style. (asset) (W16CPA)
>>>>>
>>>>>  Correct the htmlhelp.exe example so that it displays context-sensitive
>>>>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>>>>
>>>>>  Ensure the new project manager target nodes are expanded by default.
>>>>> (xwbassochlp20.dll) (W16CPD)
>>>>>
>>>>>  Reorganize the closed workitems list in such a way that new features
>>>>> and changes are shown first followed by the list of fixes/corrections
>>>>> (changes20.chm) (W16CPL)
>>>>>
>>>>>  Ensure that ALINK is able to handle long import library names
>>>>> identical
>>>>> in the first 16 chars. (alink.exe) (W16CPQ)
>>>>>
>>>>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>>>>> the XbpColumn class init state needs to be independent from module init
>>>>> state. (xppdui.dll) (W16CPY)
>>>>>
>>>>>  Use global busy indicator when build is in progress.
>>>>> (xppworkbench.exe)
>>>>> (W16CQ1)
>>>>>
>>>>>  Update "conventions" section in the reference documentation: changes
>>>>> are highlighted in red. (convent20.chm) (W16CRQ)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>>>>> Hallo,
>>>>>>
>>>>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich
>>>>>> aber
>>>>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>>>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>>>
>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>>>
>>>>>>
>>>>>> Markus
>>>>>
>>>
> 
>

Hi Michael,

Danke für den Hinweis.
Wir haben das auch schon mehrfach hier im Haus diskutiert.
Sind aber immer wieder zu dem Ergebnis gekommen, dass wir "Herrscher" 
über unsere Installation sein wollen und müssen. Sprich, da sollen keine 
"Fremdkörper" reinwandern.

Wir bitten also keine CH, LIB oder sonstige Dateien in die Xbase++ 
Installation zu kopieren. Diese bitte in einer eigenen Struktur halten. 
Man kann sich das Leben ja erleichtern, indem man sich die Pfade in der 
Workbench hinterlegt: Tools, Environment Options, Directories. Hier kann 
man ja mehrere Pfade hinterlegen. Dann musst du dich nach einem Update 
nicht mehr dran denken.

Grüße,

Frank

On 16.05.2017 10:38, Michael Papst wrote:
> Hallo Frank,
>
> einen Wunsch hätte ich für die Updates des CDI.
>
> Man möchte bitte ein Update auch als solches installieren und nicht jedes Mal
> die alte Version deinstallieren, da wir häufig genutzte Libs und Includes
> direkt in das passende Alaska-Verzeichnis legen, fehlen diese nach jedem
> "Update". Und wenn man mal eine Sekunde nicht daran denkt, produziert der
> Linker/Compiler gleich mal eine Palette an Fehlern. Zumindest könnte
> nutzergenerierter Inhalt dort liegen bleiben.
>
> Gruß
> Michael
>
>
> On 06.04.2017 19:03:30,  wrote:
>> Kannst du dir wirklich solche Jahreszahlen merken? 2008?
>> Wie dem auch sei, CDI hat uns locker 2 Jahre an Arbeit gekostet. Das ist
>> ja nicht nur, dass wir Updates bereitstellen, sondern dahinter steckt ja
>> eine komplette Infrastruktur. Das fängt vom Build-Prozessor an (also das
>> Ding, das Xbase++ und all seine Komponenten zusammenbaut) bis hin zum
>> Packaging und Deployment. Ganz ehrlich: wir machen da nix mehr von Hand.
>> Das ist alles automatisiert (leider noch nicht das PDR Fixing ). Und
>> das war eine gewaltige Aufgabe.
>>
>> Und auch wir freuen uns, dass wir uns die Zeit dafür genommen haben,
>> denn es macht Dinge einfacher und macht uns flexibler. Und hilft unseren
>> Kunden.
>>
>> "Als Markus das schrieb" waren auch schon einige Updates verfügbar. Ich
>> habe gerade nachgeschaut: das waren seit Erscheinen der Version 2.0 5
>> Updates bis zum Post. Also so schlecht hat das nicht ausgesehen. Auch
>> wenn ich die Zweifel manchmal verstehe.
>>
>> Gruß, ich
>>
>>
>> On 04.04.2017 20:45, Jan Escholt wrote:
>>> Hallo Frank,
>>>
>>> versteh mich bitte nicht falsch. Ich bin durchaus sehr einverstanden mit
>>> Eurer CDI. Steffen hatte mir schon 2008 in Berlin vor versammelter
>>> Mannschaft zugesichert, das die Rhythmen der Fixes kürzer werden würden.
>>> Und wir wissen beide, was passiert ist. Es hat sich nämlich garnichts
>>> geändert danach. Jetzt mit CDI ist das vielleicht nicht so schnell wie
>>> gewünscht (die Ansprüche steigen halt), und viele Punkte sind überhaupt
>>> nichts für mich, aber ja, wenn das so weitergeht wie die letzten Monate,
>>> dann bin ich durchaus zufrieden damit.
>>>
>>> Aber damals, als Markus das schrieb, war das noch in keinster Weise
>>> absehbar, was da kommen würde. Du hast zwar unten eine lange Latte von
>>> abgearbeiteten Punkten zitiert, und das will ich auch nicht klein reden.
>>> Aber auch die Abstände zwischen einzelnen Updates im CDI waren
>>> zwischendurch immer mal nicht von schlechten Eltern - und das meine ich
>>> nicht positiv. Es scheint sich jetzt ganz wesentlich zu bessern. Aber
>>> zum zum Zeitpunkt der Threaderöfffnung war das halt noch nicht absehbar,
>>> da war gerade nach 6monatiger Pause gerade ein Update erschienen. Was
>>> nicht den damals von Alaska kommunizierten Ansprüchen entsprach.
>>>
>>> Jan
>>>
>>> Am 04.04.2017 um 18:08 schrieb Frank Grossheinrich:
>>>> Hey Jan,
>>>>
>>>> ja, das kam spät von mir.
>>>> Aber ich konnte das nicht so stehen lassen.
>>>> Und ich hatte mir extra das Kundenkonto vorher angeschaut.
>>>>
>>>> Ich kann Kritik ertragen. Auch wenn sie manchmal weh tut. Alaska macht
>>>> definitiv nicht alles richtig. Aber wir versuchen auch Dinge zu ändern.
>>>> Diese CDI haben wir ja explizit gemacht, damit nicht nur alle 5 Jahre
>>>> etwas passiert. CDI macht es anders. Es geht hier auch nicht um die
>>>> Frequenz. Sondern vorher haben wir immer gewartet und gewartet und
>>>> gewartet und noch dieses Feature dran gemacht und noch das Schleifchen.
>>>> Nun trauen wir uns auch mal eine Doku zu vernachlässigen. Oder vergeben
>>>> Feature-Grades ("Reifezustand" eines Features), ...
>>>>
>>>> Damit sind wir näher an den Usern. Zumindest bilden wir uns das ein.
>>>>
>>>> Anyhow, CDI war ein wichtiger Schritt.
>>>> Videos - habe gerade die Preview des nächsten Videos angeschaut - sollen
>>>> noch weiter helfen. Und und und ...
>>>>
>>>> Bis bald,
>>>>
>>>> Frank
>>>>
>>>>
>>>> On 31.03.2017 22:24, Jan Escholt wrote:
>>>>> Hallo Frank,
>>>>>
>>>>> verzeih, aber ich denke Du hast da etwas übersehen. Der Threaderöffner
>>>>> hat das im September 2015(!) geschrieben. Damals war überhaupt noch
>>>>> nicht absehbar, wie sich das mit der Continuous Delivery entwickeln
>>>>> würde. Und nach den Erfahrungen mit vorigen Update-Abständen kann ich
>>>>> den Kommentar von Markus durchaus verstehen.
>>>>>
>>>>> Jan
>>>>>
>>>>> Am 31.03.2017 um 16:06 schrieb Frank Grossheinrich:
>>>>>> Hallo Markus,
>>>>>>
>>>>>> ich habe heute meinen "ich lese mal quer" Tag ...
>>>>>> So bin ich über diese Frage gestolpert.
>>>>>>
>>>>>> Ich gestehe, dass mich diese Frage und auch die Ausführungen hier
>>>>>> ärgern. Ich will nicht über die Sinnhaftigkeit von einer
>>>>>> Subskriptionverlängerung diskutieren. Das muss jeder selbst wissen.
>>>>>>
>>>>>> Aber
>>>>>>> Auch das mit 2.0 eingeführte
>>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>>> ist schon gemein. Wir haben seit Beginn von "Continous Delivery" 19
>>>>>> Updates veröffentlicht. Und das ist "kaum etwas gebracht"?
>>>>>>
>>>>>> In jedem Update gab es Erweiterungen, Neuerungen und Problembehebungen.
>>>>>>
>>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>>> Was wird wieder Jahre dauern? Nur weil die Alaska sehr zurückhaltend
>>>>>> ist
>>>>>> mit Versionssprüngen? Wir haben Anpassungen an Xbase++ wegen dem
>>>>>> Windowsn
>>>>>> Aniversary Update "nur" in einem Update ohne Versionssprung
>>>>>> veröffentlicht. Andere Firmen machen daraus neue Versionen.
>>>>>>
>>>>>> Wie dem auch sei, ich habe mir erlaubt deine Registrierungen
>>>>>> anzuschauen
>>>>>> und das hast bisher versäumt: siehe unten.
>>>>>>
>>>>>> Das hast du alles verpasst.
>>>>>>
>>>>>> Gruß, Frank
>>>>>>
>>>>>>
>>>>>> Build 2.00.779 (closed workitems)
>>>>>> New features Add function DbDestroy() to the data-definition-language
>>>>>> (DDL) to delete an ISAM emulating table programmatically by the
>>>>>> underlying DatabaseEngine. (xpprt1.dll) (W16CWL)
>>>>>>
>>>>>> Fixes/Changes Correct the calculation of the the column widths of the
>>>>>> grids displayed in the debugger's auxilliary views. These may become
>>>>>> smaller as the views get refreshed in a debugging session.
>>>>>> (xppworkbench.exe) (W16CTU) (PDR6868)
>>>>>>
>>>>>>  Correct debugger issue where debugging codeblocks and inspecting
>>>>>> variable values crashes the client application and/or the debugger.
>>>>>> (xppdbgk.dllxppdapi.dll) (W16CUC) (PDR6874)
>>>>>>
>>>>>>  Correct the Xbase++ debugger kernel so that breakpoints set in a
>>>>>> calling context halt the debuggee after the STEP BACK (step out)
>>>>>> command
>>>>>> is used. (xppdbgk.dll) (W16CWG) (PDR6865)
>>>>>>
>>>>>>  Resolve issue where a replace operation may force a runtime error
>>>>>> right
>>>>>> after an append in exclusive mode of the PostgreSQL ISAM emulation.
>>>>>> (pgdbe.dll) (W16CWJ) (PDR6840)
>>>>>>
>>>>>>  Ensure that DllExecuteCall() allows NIL to signal NULL for all
>>>>>> reference parameter types. If passed by value, only character, object
>>>>>> and codeblock must support NIL to signal no input value. (xpprt1.dll)
>>>>>> (W16CWQ) (PDR6864)
>>>>>>
>>>>>>  Correct the STEP BACK (step out) command of the Xbase++ debugger so
>>>>>> that execution halts in the current context if the context was called
>>>>>> recursively. Currently, the debuggee is halted only after the recursion
>>>>>> has completed. (xppdbgk.dll) (W16CWR) (PDR6866)
>>>>>>
>>>>>>  Correct the debugger kernel so that a "step into" command stops the
>>>>>> debuggee in the calling function or method if the current line contains
>>>>>> a RETURN statement. (xppdbgk.dll) (W16CWT) (PDR6867)
>>>>>>
>>>>>>  Correct the callstack view in the Workbench debugger so that the
>>>>>> current context (callstack level) is indicated correctly, even when
>>>>>> debugging a function that is calling itself recursively.
>>>>>> (xppworkbench.exe) (W17CW1) (PDR6869)
>>>>>>
>>>>>>  Correct the "step over" debugger command so that execution indeed
>>>>>> stops
>>>>>> after the current line when the cursor is on a line calling the current
>>>>>> procedure recursively. Currently, the "step over" command behaves as if
>>>>>> "step into" was executed, and execution stops in the first line of the
>>>>>> current procedure. (xppdbgk.dll) (W17CW3) (PDR4692)
>>>>>>
>>>>>>  Fix race condition due to statement leak which leads the PostgreSQL
>>>>>> server to hang. (pgdbe.dll) (W17CX1) (PDR6625)
>>>>>>
>>>>>>  Resolve issues where a filter condition may lead to a runtime error
>>>>>> when executing GO TOP with the PostgreSQL ISAM emulation. (pgdbe.dll)
>>>>>> (W17CX2) (PDR6622)
>>>>>>
>>>>>>  Correct the XbpTreeView class so that tree view items can be
>>>>>> manipulated with a stylus. (xppui1.dll) (W17CXB) (PDR6871)
>>>>>>
>>>>>>  Add a class method :setBehavior() to the XbpBrowse class to allow
>>>>>> configuring the navigational behavior of all browse objects.
>>>>>> (xppdui.dll) (W17CXH) (PDR6873)
>>>>>>
>>>>>>  Resolve IDSC or stall with 1-digit port in connection string of
>>>>>> PostgreSQL DatabaseEngine. Add unit test. (pgdbe.dll) (W17CXJ)
>>>>>> (PDR6861)
>>>>>>
>>>>>>  Resolve issue with runtime error on PACK using PostgreSQL ISAM
>>>>>> emulation. Add unit test. (pgdbe.dll) (W17CXK) (PDR6856)
>>>>>>
>>>>>>  Resolve IDSC when opening ISAM table w/ SQL result set open. Add unit
>>>>>> test. (pgdbe.dll) (W17CXL) (PDR6848)
>>>>>>
>>>>>>  Fix invalid return value of DacSession():executeQuery(). (adac20b.dll)
>>>>>> (W17CXN) (PDR6847)
>>>>>>
>>>>>>  Resolve issue with empty resultsets and invalid EOF() and Found()
>>>>>> states. Extend existing unit test. (pgdbe.dll) (W17CXP) (PDR6827)
>>>>>>
>>>>>>  Fix issue with default precision handling for aggregate results. Add
>>>>>> unit test to cover aggregate result type handling. (pgdbe.dll) (W17CXQ)
>>>>>> (PDR6824)
>>>>>>
>>>>>>  Fix invalid Recno() and Eof() state after ZAP/DbZap() with PostgreSQL
>>>>>> ISAM emulation (pgdbe.dll) (W17CXR) (PDR6819)
>>>>>>
>>>>>>  Resolve issue with wrong record number in empty workarea if all
>>>>>> records
>>>>>> get filtered out by the FOR expression of the current order. Extend
>>>>>> unit
>>>>>> test. (pgdbe.dll) (W17CXS) (PDR6818)
>>>>>>
>>>>>>  Resolve issues where OrdListRebuild() may run into an internal error
>>>>>> with the PostgreSQL ISAM emulation. (pgdbe.dll) (W17CXT) (PDR6808)
>>>>>>
>>>>>>  Fix the issue where creating an index with same name as an open index
>>>>>> yields error while the PGDBE is trying to update the seek procedure.
>>>>>> Extend unit test. (pgdbe.dll) (W17CXU) (PDR6806)
>>>>>>
>>>>>>  Correct the PostgreSQL documentation regarding the numeric precision
>>>>>> and scale calculation. (pgdbe.dll) (W17CXW) (PDR6804)
>>>>>>
>>>>>>  Resolve the issues where adding an index tag to an existing bag leads
>>>>>> to invalid sql plan. Extend unit test also. (pgdbe.dll) (W17CXX)
>>>>>> (PDR6801)
>>>>>>
>>>>>>  Resolve issues where SELECT Max(<charfield>) yields incorrect results
>>>>>> with the PostgreSQL DatabaseEngine. (pgdbe.dll) (W17CXY) (PDR6767)
>>>>>>
>>>>>>  Ensure the debugger tool tips are displayed correctly when using the
>>>>>> "Adjust the size of text and other display items" system option under
>>>>>> Windows 10. (xppworkbench.exe) (W15B7X) (PDR6722)
>>>>>>
>>>>>>  Investigate and fix the issue in the Xbase++ Workbench which sometimes
>>>>>> causes an error message to appear ("canvas drawing error") when
>>>>>> building
>>>>>> or debugging an application. (xppworkbench.exe) (W16CTK)
>>>>>>
>>>>>>  Correct the example code in the "Using northwind programmatically"
>>>>>> programming guide chapter in the PGDBE documentation: the session
>>>>>> object
>>>>>> used with an SQL SELECT must be specified in parentheses. (*.chm)
>>>>>> (W16CTR)
>>>>>>
>>>>>>  Output a warning when attempting to load executables containing name
>>>>>> tokens such as "install" or "setup" into the debugger. This is required
>>>>>> as Windows handles executables with these names differently and may not
>>>>>> allow debugging. (xppworkbench.exe) (W16CUR)
>>>>>>
>>>>>>  Correct product sample readme files to conform to the specifications
>>>>>> regarding content and format. (samples) (W16CWP)
>>>>>>
>>>>>>  Reduce flicker in the context windows of the debugger when stepping
>>>>>> through the code. The callstack window, for example, flickers
>>>>>> excessively when the callstack is large. (xppworkbench.exe) (W17CWW)
>>>>>>
>>>>>>  Ensure xppdui.dll is exported to the \runtime folder by the local
>>>>>> makefile. And remove xppprof.dll, eventspy.dll a and memwatch.dll from
>>>>>> the runtime folder of the installed product. (*.msi) (W17CWY)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Build 2.00.769 (closed workitems)
>>>>>> New features Maintain asac.log in the users documents\xbase++\.logs
>>>>>> folder. (xppworkbench.exe) (W16CTQ)
>>>>>>
>>>>>>  Ensure that all datatypes from types.ch are properly supported by the
>>>>>> USQL local engine (embedded SQLite). (asrdbc10.dll) (W16CU4)
>>>>>>
>>>>>>  Add readme to the styled combo box example for the XbpHTMLStyle class
>>>>>> to describe the rationale behind the sample. (samples) (W16CU7)
>>>>>>
>>>>>>  Extend DLLCall() with an optional DLL_CALLMODE_RESTOREFPU mode to
>>>>>> ensure that called code is not affecting FPU status of the Xbase++
>>>>>> application. (xpprt1.dll) (W16CUB)
>>>>>>
>>>>>> Fixes/Changes Investigate and resolve issue why halting a running
>>>>>> debuggee (CTRL+S) takes such a long time to complete under Windows 10
>>>>>> Anniversary Update. (xppdbgk.dll) (W16CNQ) (PDR6857)
>>>>>>
>>>>>>  Correct runtime FPU control word management so that calls to
>>>>>> misbehaving API or printer driver code does not affect rounding
>>>>>> behavior. (xpprt1.dll) (W16CT1) (PDR6678)
>>>>>>
>>>>>>  Ensure the scroll bars in XbpBrowse and XbpQuickBrowse objects can be
>>>>>> operated with the finger, even after tapping the data area of the
>>>>>> browse. (xppdui.dll) (W16CT3) (PDR6822)
>>>>>>
>>>>>>  Correct the XbpQuickBrowse class so that it works correctly with a
>>>>>> top/left origin setting. (xppdui.dll) (W16CT4) (PDR6852)
>>>>>>
>>>>>>  Correct the XbpToolBar class so that no runtime error occurs when the
>>>>>> first item has an icon image. (xppdui.dll) (W16CT7) (PDR6754)
>>>>>>
>>>>>>  Add code to the XbpPrinter for ensuring that the current FPU settings
>>>>>> are reset after communicating with a printer driver. (xppui1.dll)
>>>>>> (W16CTX) (PDR6854)
>>>>>>
>>>>>>  Correct the XbpHTMLStyle class so that the output is positioned
>>>>>> correctly when used in conjunction with the XbpComboBox class.
>>>>>> (xppwui.dll) (W16CU2) (PDR6860)
>>>>>>
>>>>>>  Correct the issue in the Workbench debugger which may cause runtime
>>>>>> errors in the IDE after resuming the client application after stopping
>>>>>> at a breakpoint. (xppdapi.dll) (W16CUG) (PDR6646)
>>>>>>
>>>>>>  Correct the Workbench debugger so that executables can be debugged
>>>>>> which reside in a path containing Umlaut characters (xppworkbench.exe)
>>>>>> (W16CUH) (PDR6639)
>>>>>>
>>>>>>  Fix SQLite type affinity related PDR 6855. Extend the existing test
>>>>>> suite to ensure correct behaviour according to SQLite spec./doc.
>>>>>> (asrdbc10.dll) (W16CUJ) (PDR6855)
>>>>>>
>>>>>>  Resolve issue where SQL SELECT operations against local tables may
>>>>>> cause a runtime error (internal datastructures corrupted) (adac20b.dll)
>>>>>> (W16CUK) (PDR6762)
>>>>>>
>>>>>>  The header files in the auto-dependency section must be normalized
>>>>>> relative to the target. (pbuild.exe) (W16CUL) (PDR6851)
>>>>>>
>>>>>>  Resolve DACSqlStatement: No instances allowed for this class error and
>>>>>> extend the test suite to cover USQL with ADSDBE also. (adsutil.dll)
>>>>>> (W16CUQ) (PDR6815)
>>>>>>
>>>>>>  Remove implicit type negotiation of USQL. (asrdbc10.dll) (W16CUY)
>>>>>> (PDR6757)
>>>>>>
>>>>>>  Ensure strings used with HTML/CSS-based Xbase Parts such as
>>>>>> XbpCommandButton are converted to ANSI when the application uses an OEM
>>>>>> charset (automatic OEM/ANSI conversion). (xppwui.dll) (W15B3U)
>>>>>> (PDR6712)
>>>>>>
>>>>>>  Remove the commandline switch /rc from the resource compiler
>>>>>> executable
>>>>>> and documentation. (arc.exe) (W16CT2)
>>>>>>
>>>>>>  Validate for the correct interface when a XmlMapper is passed as
>>>>>> second
>>>>>> parameter to Var2Xml() (xpprt2.dll) (W16CTW)
>>>>>>
>>>>>>  Correct the source code sample in the chapter "Programmatic
>>>>>> reference -
>>>>>> dbfupsize.dll" (pg20.chm) (W16CUA)
>>>>>>
>>>>>>  Ensure that SELECT ... INTO ARRAY aData returns a multi dimensional
>>>>>> array for fieldcount 1 - N and an empty array for an empty result set.
>>>>>> Review related unit-tests. (asrdbc10.dll) (W16CUS)
>>>>>>
>>>>>>  Review USQL unit tests with respect to the revised type system and
>>>>>> ensure that the core types are properly validated. (adac20b.dll)
>>>>>> (W16CUX)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Build 2.00.762 (closed workitems)
>>>>>> New features Add alternative interfaces for loading images used in the
>>>>>> HTML/CSS stream of an XbpHTMLStyle object. Currently, images must be
>>>>>> Base64-encoded and defined via a :data URI scheme. (xppwui.dll)
>>>>>> (W16CJT)
>>>>>>
>>>>>>  Ensure the project manager restores the collapse/expand state.
>>>>>> (xppworkbench.exe) (W16CND)
>>>>>>
>>>>>>  Extend Workbench pre-defined macros to support all directories from
>>>>>> the
>>>>>> "Environment options" directories dialog. (xppworkbench.exe) (W16CNF)
>>>>>>
>>>>>>  Extend the DLL_TYPES with unsigned 16 and unsigned 32 bit types.
>>>>>> Extend
>>>>>> the unit-test to cover the entire range of possible values as
>>>>>> parameter,
>>>>>> reference parameter and return value. (xpprt1.dll) (W16CNR)
>>>>>>
>>>>>>  Add a function BinaryName() to identify the execution context. The
>>>>>> function returns the name of the binary (exe or dll) executing the
>>>>>> function. (xpprt1.dll) (W16CNX)
>>>>>>
>>>>>>  Extend the DLL_TYPES with signed and unsigned 64 bit types. Extend the
>>>>>> unit-test to cover the entire range of possible values as parameter,
>>>>>> reference parameter and return value. (xpprt1.dll) (W16CPK)
>>>>>>
>>>>>>  Add a control for indicating busy state to the Xbase++ Workbench.
>>>>>> (xppworkbench.exe) (W16CQB)
>>>>>>
>>>>>>  The workbench must maintain logfiles in the user's documents folder
>>>>>> under Xbase++\.logs. The folder Xbase++\logs becomes obsolete.
>>>>>> (xppworkbench.exe) (W16CRW)
>>>>>>
>>>>>>  Add optional feature "Asset Repository" to the installation package.
>>>>>> The feature is a child of "Xbase++ 2.0 for windows". Installation is
>>>>>> done to the users documents folder "Xbase++\.assets". (xpp*.msi)
>>>>>> (W16CH3)
>>>>>>
>>>>>> Fixes/Changes Add a resource setting to configure round() behavior
>>>>>> according to PDR 6678. (xpprt1.dll) (W16CLL) (PDR6678)
>>>>>>
>>>>>>  Ensure that mails containing a line starting with a dot are send
>>>>>> completly instead of as a fragment by the SmtpClient class. See PDR
>>>>>> 6823. (asinet10.dll) (W16CNT) (PDR6823)
>>>>>>
>>>>>>  Ensure that the XbpColumn class correctly respects the XBP_PP_ORIGIN
>>>>>> presentation parameter when computing the position of the header and
>>>>>> footer elements. (xppdui.dll) (W16CPJ) (PDR6828)
>>>>>>
>>>>>>  Fix handle leak in PGDBE when performing SELECT queries and extend the
>>>>>> unit test to cover that scenario. See PDR 6834 (pgdbe.dll) (W16CR1)
>>>>>> (PDR6834)
>>>>>>
>>>>>>  Highlight new content in the documentation using the color dark red.
>>>>>> (xppref.css) (W16CJR)
>>>>>>
>>>>>>  Ensure the XbpImageListBox control conforms to our coding style.
>>>>>> (asset) (W16CL2)
>>>>>>
>>>>>>  Ensure that asget writes error messages to stdout. This enables the
>>>>>> workbench to display the error message. (asget.exe) (W16CL7)
>>>>>>
>>>>>>  Extend exisiting Workbench template mechanism in such a way that new
>>>>>> templates can be easily added by the user (xppworkbench.exe) (W16CL9)
>>>>>>
>>>>>>  Ensure XbpPanelContainer and XbpCollapsiblePanel classes and
>>>>>> associated
>>>>>> files conform to our coding style. (asset) (W16CLC)
>>>>>>
>>>>>>  Ensure XbpHTMLStatic class and associated code conform to our coding
>>>>>> style. (asset) (W16CLH)
>>>>>>
>>>>>>  Ensure the XbpCommandButton class and related files conform to our
>>>>>> coding style. (asset) (W16CLJ)
>>>>>>
>>>>>>  Ensure the XbpCheckedListBox class and related files conform to our
>>>>>> coding style. (asset) (W16CN1)
>>>>>>
>>>>>>  Ensure the dialog for managing target-specific assets remembers its
>>>>>> current size and position, as well as splitbar position.
>>>>>> (xppworkbench.exe) (W16CN2)
>>>>>>
>>>>>>  Ensure the "New Items" dialog remembers its current size and position
>>>>>> (xppworkbench.exe) (W16CN3)
>>>>>>
>>>>>>  Create and add import definition for VFP modernizer to Workbench
>>>>>> (xppworkbench.exe) (W16CNC)
>>>>>>
>>>>>>  Change "New items" dialog so that the view style (large icons etc.) is
>>>>>> restored when the dialog is reopened. (xppworkbench.exe) (W16CNW)
>>>>>>
>>>>>>  Modify the event management sample in the CXP sample collection so
>>>>>> that
>>>>>> it uses the POST verb for transferring data, eg. when saving events.
>>>>>> (alaska-software.webui.js) (W16CP1)
>>>>>>
>>>>>>  Add a static/non-collapsible panel class to the XbpPanelContainer
>>>>>> control. (asset) (W16CP4)
>>>>>>
>>>>>>  Extend the styled list box example for the XbpHTMLStyle class so that
>>>>>> it better illustrates the usage of the WebUI for customizing an
>>>>>> existing
>>>>>> Xbase Part. (samples) (W16CP7)
>>>>>>
>>>>>>  Ensure the XbpToggleButton class and related files conform to our
>>>>>> coding style. (asset) (W16CPA)
>>>>>>
>>>>>>  Correct the htmlhelp.exe example so that it displays context-sensitive
>>>>>> help when pressing the F1 key. (htmlhelp.exe) (W16CPC)
>>>>>>
>>>>>>  Ensure the new project manager target nodes are expanded by default.
>>>>>> (xwbassochlp20.dll) (W16CPD)
>>>>>>
>>>>>>  Reorganize the closed workitems list in such a way that new features
>>>>>> and changes are shown first followed by the list of fixes/corrections
>>>>>> (changes20.chm) (W16CPL)
>>>>>>
>>>>>>  Ensure that ALINK is able to handle long import library names
>>>>>> identical
>>>>>> in the first 16 chars. (alink.exe) (W16CPQ)
>>>>>>
>>>>>>  Ensure that DLLs using XbpColumn can be unloaded/reloaded. For that,
>>>>>> the XbpColumn class init state needs to be independent from module init
>>>>>> state. (xppdui.dll) (W16CPY)
>>>>>>
>>>>>>  Use global busy indicator when build is in progress.
>>>>>> (xppworkbench.exe)
>>>>>> (W16CQ1)
>>>>>>
>>>>>>  Update "conventions" section in the reference documentation: changes
>>>>>> are highlighted in red. (convent20.chm) (W16CRQ)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 30.09.2015 08:19, Markus Ratzesberger wrote:
>>>>>>> Hallo,
>>>>>>>
>>>>>>> aktuell stünde bei mir eine Subscription-Verlängerung an, wenn ich
>>>>>>> aber
>>>>>>> hier so mitlese was Alaska hier nicht schreibt oder beantwortet frage
>>>>>>> ich mich über die Sinnhaftigkeit. Auch das mit 2.0 eingeführte
>>>>>>> "continous delivery" hat kaum etwas gebracht.
>>>>>>>
>>>>>>> Wahrscheinlich ist es günstiger, das in nächste Update dann einfach
>>>>>>> wieder zu kaufen. Werden ja sicher wieder ein paar Jahre vergehen...
>>>>>>>
>>>>>>>
>>>>>>> Markus
>>>>>>
>>>>
>>
>>
>