[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Wed Oct 13 04:17:50 + 2010 --- jbu: I am curious . . . did the dump I posted on Sep. 21 give you what you were looking for? If not, I'll gladly redo it however you say. I would like to help in whatever way I can in the fixing of this issue, but know very little about what all is involved beyond the primitive little patch I got working on my personal machine, as discussed in this thread. So any feedback, or suggestions will be greatly appreciated. Thanks, Nick On Sun, 2010-09-19 at 19:31 +, j...@openoffice.org wrote: Can you provide a complete native thread dump ? Should work as follows gdb /path/to/soffice.bin pid then type thread apply all bt - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Tue Sep 21 02:14:06 + 2010 --- I would be glad to, but as I am very new to this kind of work, please confirm that I understand exactly what you are asking for: 1) Start running an un-patched version OpenOffice process 2) Get it to hang by attempting to write to python attribute from basic 3) Run the dgb commands you suggest on the pid of the hung process My current installation has the patch discussed above (which so far has been working like a charm), but I can easily switch over to using the original libpyuno.so and post the backtrace you suggest of all threads in a hung process, assuming that is in fact what you are looking for. On Sun, 2010-09-19 at 19:31 +, j...@openoffice.org wrote: Can you provide a complete native thread dump ? Should work as follows gdb /path/to/soffice.bin pid then type thread apply all bt - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Tue Sep 21 05:11:11 + 2010 --- Anyway, using a hung soffice process (from the posted sample code), here's the screen output of the gdb commands jbu mentioned: nick-deb:/sortwork/nativethreaddump# gdb /usr/lib/openoffice/program/soffice.bin 4923 GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... (no debugging symbols found) Attaching to program: /usr/lib/openoffice/program/soffice.bin, process 4923 Reading symbols from /usr/lib/ure/lib/libuno_sal.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/ure-link/lib/libuno_sal.so.3 Reading symbols from /usr/lib/openoffice/basis3.2/program/libsofficeapp.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libsofficeapp.so Reading symbols from /usr/lib/libstlport_gcc.so.4.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstlport_gcc.so.4.6 Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/i686/cmov/libm.so.6... (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libm.so.6 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/i686/cmov/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/libpam.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpam.so.0 Reading symbols from /lib/i686/cmov/libcrypt.so.1... (no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libcrypt.so.1 Reading symbols from /lib/i686/cmov/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] [New Thread 0xb508f980 (LWP 4923)] [New Thread 0xa7ae1b90 (LWP 4940)] [New Thread 0xa7deab90 (LWP 4939)] [New Thread 0xa7eebb90 (LWP 4938)] [New Thread 0xa7f6cb90 (LWP 4937)] [New Thread 0xa806db90 (LWP 4936)] [New Thread 0xa816eb90 (LWP 4935)] [New Thread 0xa826fb90 (LWP 4934)] [New Thread 0xa82f0b90 (LWP 4933)] [New Thread 0xaf06ab90 (LWP 4930)] [New Thread 0xb06a1b90 (LWP 4927)] [New Thread 0xb2a8bb90 (LWP 4926)] [New Thread 0xb328cb90 (LWP 4925)] [New Thread 0xb4f24b90 (LWP 4924)] Loaded symbols for /lib/i686/cmov/libpthread.so.0 Reading symbols from /usr/lib/openoffice/basis3.2/program/libcomphelp4gcc3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libcomphelp4gcc3.so Reading symbols from /usr/lib/ure/lib/libuno_cppuhelpergcc3.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 Reading symbols from /usr/lib/ure/lib/libuno_cppu.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/../ure-link/lib/libuno_cppu.so.3 Reading symbols from /usr/lib/openoffice/basis3.2/program/libi18nisolang1gcc3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libi18nisolang1gcc3.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libsfxli.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libsfxli.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libsvlli.so... (no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libsvlli.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libsvtli.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libsvtli.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libtkli.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libtkli.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libtlli.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libtlli.so Reading symbols from /usr/lib/openoffice/basis3.2/program/libucbhelper4gcc3.so... (no debugging symbols found)...done. Loaded symbols for /usr/lib/openoffice/program/../basis-link/program/libucbhelper4gcc3.so Reading symbols from
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Wed Jul 21 17:06:23 + 2010 --- Indded, that fix to Adapter::setValue should be much more solid. Is there anything I can do to help getting a patch like this into a new release? I am totally new to this sort of stuff, but am capable of learning new tricks . . . - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 113302] pyuno: Apparent typo in u nhelper.py
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113302 --- Additional comments from gur...@openoffice.org Thu Jul 22 01:51:57 + 2010 --- The questionable code at that link is line 72/73 if PROP_ATTR_TRANSIENT mode: ret = ret + tranient which I still think should be if PROP_ATTR_TRANSIENT mode: ret = ret + transient - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111641
--- Additional comments from gur...@openoffice.org Tue Jul 20 06:06:28
+ 2010 ---
Great discovery hanya!
So here is my attempt - as a complete noob - at a fix that minimal testing seems
to indicate the problem is solved and revealing nothing else as seriously
broken.
Offending line commented out:
sal_Bool Adapter::hasProperty( const OUString aPropertyName )
throw ( RuntimeException )
{
bool bRet = false;
//PyThreadAttach guard( mInterpreter );
{
bRet = PyObject_HasAttrString(
mWrappedObject.get() , (char*) TO_ASCII( aPropertyName ));
}
return bRet;
}
Rebuilding OOo from source (debian package 1:3.2.0-4~bpo50+1) with that one
change did the trick! (I have also been able to put the new libpyuno.so into
another, otherwise un-hacked installation of the same debian version of OOo and
gotten the problem to go away there too.)
But someone who really knows what they are doing had better weigh in here before
this goes anywhere else, as I have never done anything like this before. The
required 7 hour complete build of OOo just to fix the python-uno package was an
extreme eyeopener into the workings of OOo (quite shocking at first!) but I am
thrilled to have now at least gotten a one-line code change to have apparently
solved a problem that has been causing me considerable headaches for a while
now!
Thanks again hanya for leading me this one step further into OOo programming
oblivion!!! I look forward to many more to come!
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org
For additional commands, e-mail: issues-h...@udk.openoffice.org
-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 113302] pyuno: Apparent typo in u nhelper.py
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113302 Issue #|113302 Summary|pyuno: Apparent typo in unhelper.py Component|udk Version|OOo 3.2 Platform|PC URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|jbu Reported by|gurfle --- Additional comments from gur...@openoffice.org Wed Jul 21 03:39:17 + 2010 --- Line 76/77 if PROP_ATTR_TRANSIENT mode: ret = ret + tranient I think should be if PROP_ATTR_TRANSIENT mode: ret = ret + transient Haven't seen any ill effects of this, but then I have not used transient properties, and not being even sure how to use them, I have no tests to report any such effects. I just ran accross this while browsing unohelper, trying to trace the cause of another issue (http://www.openoffice.org/issues/show_bug.cgi?id=111641) - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Wed Jun 2 05:10:28 + 2010 --- Created an attachment (id=69757) Package to easily compare faulty Python Inteface Attribute with working Java implementation - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 --- Additional comments from gur...@openoffice.org Wed Jun 2 05:15:34 + 2010 --- I have just attached a little package that hopefully should make some initial confirmation/testing/diagnosis of this issue much easier The purpose of the package is to compare the faulty behaviour of a python implementation of the component defined in UNO-IDL OOoComponents/TestOOComp/idl/names/nick/openoffice/TestOOComp.idl to a working Java implementation. All Binaries were built - and if necessary can be rebuilt using the script OOoComponents/MakeJavaComponent.sh To run a simple test: 1) Extract onto any system with OOo SDK, JDK and Python 2) Out of OOoComponents/TestOOComp add the folllowing three OOo Extensions: TestOOComptypes.rdb (as UNO RDB Type Library) TestOOCompImpl.jar (as UNO Java Component) TestOOCompImpl.py (as UNO Python Component) 3) Test Java implementation using Basic Macro code in OOoComponents/TestOOComp/TestOOCompImpl.bas 4) Test Python implementation using same code with service names.nick.openoffice.TestOOCompJavaImpl replaced by names.nick.openoffice.TestOOCompPythonImpl CAREFUL: BE PREPARED FOR OO TO FREEZE - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 User gurfle changed the following: What|Old value |New value URL| |http://user.services.openo | |ffice.org/en/forum/viewtop | |ic.php?f=45t=30543p=1392 | |31#p139231 Issue type|PATCH |DEFECT --- Additional comments from gur...@openoffice.org Fri May 21 01:52:04 + 2010 --- May 20th, 2010 edit: Original report submitted with issue type incorrectly marked as patch. I certainly do *not* have a patch, so am changing to issue type to defect. Also, adding URL pointing to prior attempt to start a discussion on OOo community forum. |\|. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111641
Issue #|111641
Summary|pyuno: Python-implemented Interface attribute is not w
|riteable
Component|udk
Version|OOo 3.2
Platform|PC
URL|
OS/Version|All
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|PATCH
Priority|P3
Subcomponent|code
Assigned to|jbu
Reported by|gurfle
--- Additional comments from gur...@openoffice.org Mon May 17 00:38:07
+ 2010 ---
Confirmed on Debian Linux 5.03 and Windows XP, sos supect it crosses all OS
platforms - URL is to a - so far inconclusive - OO Community Forum topic I
started on the issue that also lists the same code examples included below.
As illstrated in the OO Basic macro at the very bottom of this desciption,
assigning a value to a Python-implemeted readwrite attribute of a (UNOIDL)
user-defined Interface causes OO to freeze - soffice process must be killed
before any activity can be resumed.
This can be reproduced using the following example UNOIDL and python modules:
Contents of XTestOOPythonComp.idl (compiled .rdb file to be added as OO
Extension UNO RDB Type Library):
#ifndef __names_nick_openoffice_TestOOPythonComp_idl__
#define __names_nick_openoffice_TestOOPythonComp_idl__
module names { module nick { module openoffice { module TestOOPythonComp {
interface XTestOOPythonComp
{
[attribute] double TestOOPyDouble;
[attribute] long TestOOPyLong;
[attribute] string TestOOPyString;
double OOCompFunction( [in] double a, [in] double b );
// The following should not be necessary to properly implement the Interface
with the above attributes
/
double getTestOOPyDouble( );
void setTestOOPyDouble( [in] double newTestOOPyDouble );
long getTestOOPyLong( );
void setTestOOPyLong( [in] long newTestOOPyLong );
string getTestOOPyString( );
void setTestOOPyString( [in] string newTestOOPyString );
/
};
service STestOOPythonComp: XTestOOPythonComp;
}; }; }; };
#endif
Contents of TestOOPythonComp.py (to be added as OO Extension UNO Python
Component):
import uno
import unohelper
from com.sun.star.lang import XServiceName
from com.sun.star.lang import XServiceInfo
from names.nick.openoffice.TestOOPythonComp import XTestOOPythonComp
class TestOOPythonComp(unohelper.Base, XServiceName, XServiceInfo,
XTestOOPythonComp):
TestOOPyDouble=47.3
TestOOPyLong=6
TestOOPyString=MyStr
ServiceName=STestOOPythonComp
ImplementationName=OTestOOPythonComp
def __init__(self,newctx=None):
self.ctx=newctx
def OOCompFunction(self,a,b):
return a+b
# The following should not be necessary to properly implement the Interface
with the above attributes
def getTestOOPyDouble(self):
return self.TestOOPyDouble
def setTestOOPyDouble(self,newTestOOPyDouble):
self.TestOOPyDouble=newTestOOPyDouble
def getTestOOPyLong(self):
return self.TestOOPyLong
def setTestOOPyLong(self,newTestOOPyLong):
self.TestOOPyLong=newTestOOPyLong
def getTestOOPyString(self):
return self.TestOOPyString
def setTestOOPyString(self,newTestOOPyString):
self.TestOOPyString=newTestOOPyString
def getServiceName(self):
return self.ServiceName
def getImplementationName(self):
return self.ImplementationName
def getSupportedServiceNames(self):
return (self.ServiceName,)
g_ImplementationHelper = unohelper.ImplementationHelper()
g_ImplementationHelper.addImplementation(TestOOPythonComp,names.nick.openoffice.TestOOPythonCompImpl,(com.sun.star.task.Job,),)
OO Basic Macro to test the issue (CAUTION: As written, it WILL freeze soffice)
Option Explicit
Sub TestOOPythonComp
Dim x as Object
Dim y as Double
x = createUnoService( names.nick.openoffice.TestOOPythonCompImpl )
print x.TestOOPyDouble ' Displays value (47.3) without a problem
y=23.7
setTestOOPythonDouble(y) ' This works, as does print
getTestOOpythonDouble()
x.TestOOPyDouble=y ' CAUTION: This causes OO to freeze: Only killing the
soffice process frees OO up again
End Sub
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org
For additional commands, e-mail: issues-h...@udk.openoffice.org
[udk-issues] [Issue 111642] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111642
Issue #|111642
Summary|pyuno: Python-implemented Interface attribute is not w
|riteable
Component|udk
Version|OOo 3.2
Platform|PC
URL|http://user.services.openoffice.org/en/forum/viewtopic
|.php?f=45t=30543p=139231#p139231
OS/Version|All
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|PATCH
Priority|P3
Subcomponent|code
Assigned to|jbu
Reported by|gurfle
--- Additional comments from gur...@openoffice.org Mon May 17 00:42:30
+ 2010 ---
Confirmed on Debian Linux 5.03 and Windows XP, so suspect it crosses all OS
platforms - URL is to a - so far inconclusive - OO Community Forum topic I
started on the issue that also lists the same code examples included below.
As illstrated in the OO Basic macro at the very bottom of this desciption,
assigning a value to a Python-implemeted readwrite attribute of a (UNOIDL)
user-defined Interface causes OO to freeze - soffice process must be killed
before any activity can be resumed.
This can be reproduced using the following example UNOIDL and python modules:
Contents of XTestOOPythonComp.idl (compiled .rdb file to be added as OO
Extension UNO RDB Type Library):
#ifndef __names_nick_openoffice_TestOOPythonComp_idl__
#define __names_nick_openoffice_TestOOPythonComp_idl__
module names { module nick { module openoffice { module TestOOPythonComp {
interface XTestOOPythonComp
{
[attribute] double TestOOPyDouble;
[attribute] long TestOOPyLong;
[attribute] string TestOOPyString;
double OOCompFunction( [in] double a, [in] double b );
// The following should not be necessary to properly implement the Interface
with the above attributes
/
double getTestOOPyDouble( );
void setTestOOPyDouble( [in] double newTestOOPyDouble );
long getTestOOPyLong( );
void setTestOOPyLong( [in] long newTestOOPyLong );
string getTestOOPyString( );
void setTestOOPyString( [in] string newTestOOPyString );
/
};
service STestOOPythonComp: XTestOOPythonComp;
}; }; }; };
#endif
Contents of TestOOPythonComp.py (to be added as OO Extension UNO Python
Component):
import uno
import unohelper
from com.sun.star.lang import XServiceName
from com.sun.star.lang import XServiceInfo
from names.nick.openoffice.TestOOPythonComp import XTestOOPythonComp
class TestOOPythonComp(unohelper.Base, XServiceName, XServiceInfo,
XTestOOPythonComp):
TestOOPyDouble=47.3
TestOOPyLong=6
TestOOPyString=MyStr
ServiceName=STestOOPythonComp
ImplementationName=OTestOOPythonComp
def __init__(self,newctx=None):
self.ctx=newctx
def OOCompFunction(self,a,b):
return a+b
# The following should not be necessary to properly implement the Interface
with the above attributes
def getTestOOPyDouble(self):
return self.TestOOPyDouble
def setTestOOPyDouble(self,newTestOOPyDouble):
self.TestOOPyDouble=newTestOOPyDouble
def getTestOOPyLong(self):
return self.TestOOPyLong
def setTestOOPyLong(self,newTestOOPyLong):
self.TestOOPyLong=newTestOOPyLong
def getTestOOPyString(self):
return self.TestOOPyString
def setTestOOPyString(self,newTestOOPyString):
self.TestOOPyString=newTestOOPyString
def getServiceName(self):
return self.ServiceName
def getImplementationName(self):
return self.ImplementationName
def getSupportedServiceNames(self):
return (self.ServiceName,)
g_ImplementationHelper = unohelper.ImplementationHelper()
g_ImplementationHelper.addImplementation(TestOOPythonComp,names.nick.openoffice.TestOOPythonCompImpl,(com.sun.star.task.Job,),)
OO Basic Macro to test the issue (CAUTION: As written, it WILL freeze soffice)
Option Explicit
Sub TestOOPythonComp
Dim x as Object
Dim y as Double
x = createUnoService( names.nick.openoffice.TestOOPythonCompImpl )
print x.TestOOPyDouble ' Displays value (47.3) without a problem
y=23.7
setTestOOPythonDouble(y) ' This works, as does print
getTestOOpythonDouble()
x.TestOOPyDouble=y ' CAUTION: This causes OO to freeze: Only killing the
soffice process frees OO up again
End Sub
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org
For additional commands, e
[udk-issues] [Issue 111641] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111641 User gurfle changed the following: What|Old value |New value IssuesThisDependsOn| |111642 - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111642] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111642 User gurfle changed the following: What|Old value |New value OtherIssuesDependingOnTh| |111641 is| | - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[udk-issues] [Issue 111642] pyuno: Python-implemented Interface attribute is not writeable
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=111642 User gurfle changed the following: What|Old value |New value Issue type|PATCH |DEFECT - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org For additional commands, e-mail: issues-h...@udk.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
