[Octave-bug-tracker] [bug #46235] [OF] windows package doesn't work anymore with newest Octave 4.1.0+

[Philip Nienhuis]

URL:
  <http://savannah.gnu.org/bugs/?46235>

                 Summary: [OF] windows package doesn't work anymore with
newest Octave 4.1.0+
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Sat 17 Oct 2015 02:05:47 PM CEST
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

The OF windows package has stopped working with recent Octave development
versions.

## Trying to invoke LibreOffice:
>> objServiceManager = actxserver ("com.sun.star.ServiceManager")
error: actxserver: unknown ActiveX server ` L↕j'
>>

## ...or with MS-Excel:
>> app = actxserver ("Excel.Application")
error: actxserver: unknown ActiveX server `░%‼j'
>>


where the following is expected:

## LibreOffice
>> objServiceManager = actxserver ("com.sun.star.ServiceManager")

objServiceManager =

<COM object Unknown (0x0xd6e3848)>

>>

## or for Excel:
>> app = actxserver ("Excel.Application")
app =

<COM object _Application (0x0xd8d38b8)>

>>


Experimenting with older Octave binary Windows installers I have lying around
shows that OF windows packages from the mxe-octave installers:
* work fine with Octave rev. f61c67865d9f (~7 Oct.)
* don't work anymore with Octave rev. 56333f6df823 (~10 Oct.)

(Those revisions and dates are of course just indicative - somewhere in
between them the windows package stopped working.  I merely include the
revision name when renaming the mxe-octave binary installers.)

The OF windows-1.2.1 package from the newest Octave binary I have (rev.
ab705b42cfd8, ~15 Oct) installs and runs fine in an Octave installation from 7
Oct.  
So something inside Octave itself has changed.  Could this be the error_state
changes?

Item Group => "Incorrect result" as I think core Octave changes affecting OF
packages aren't to be perceived as "regressions".





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46235>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/