[api-dev] PyUNO and IDL files

Hi, all! I would like to know if it is possible to develop UNO components in Python (using the usual helpers) implementing interfaces in my own IDL files, as trivial in e.g. C++. I am using OOo version 1.1.4. I got to the point of compiling my rdb file, but just packing it together with the

[api-dev] TextTable: iterating over selected cells

Hi, all! Is there a way to iterate over the cells of a TextTable that have been selected by the user? I already know of invoking getSelection for the controller. However, it seems that the best that the thus obtained XTextTableCursor can provide is RangeName, which appears useless in the case

[api-dev] PyUNO: importing modules in package directory

Hi, all! It seems that the main python module of a UNO component cannot trivially load/import auxiliary modules shipped in the same package directory. Is that correct? How can I circumvent that? Thanks in advance. Cheers, Jorge.

[api-dev] uniform access to text across OOo apps

Hi, all! Is there a uniform way to access text (=sequences of adjacent TextContents) in selections or whole documents across OOo applications (Writer, Presentation, Spreadsheet, etc.). Developers of writing aids such as myself could definitely do with that! Cheers, Jorge.

[api-dev] text table selection: iterating through split cells

Hi, all! In a writer document, is there a awy to know the names the cells which are currently selected? I am having a real hard time trying to iterate through selected cells when some of them have been _split_. I know there must be a way, because Writer itself handles it properly, but it is

[api-dev] UNO package setting keybindings

Hi, all! Is it possible to have a UNO package assign to accelerator keys to some of its BASIC macros? I imagine this might go in the .xcu, but I haven't so far managed to discover exactly how. I am using OOo 1.1.4. Thanks in advance. Cheers, Jorge.

Re: [api-dev] UNO package setting keybindings

How? Does anyone have an example that sets accelerators? Thanks anyway, Carsten! Jorge. Selon Carsten Driesner [EMAIL PROTECTED]: [EMAIL PROTECTED] wrote: Hi, all! Is it possible to have a UNO package assign to accelerator keys to some of its BASIC macros? I imagine this might go in

[api-dev] SDK 2.0

Hi, all! I am new to OOo 2.0 and would like to know if there is a specific SDK for this version or we should keep using SDK 1.1. In any case, are there undocumented new features? Where one could learn about those? Thanks in advance. Cheers, Jorge.

[api-dev] crash and PyUNO

Hi, all! I am developing some python components to help iterating and updating text respecting its original format transparently. They abstract away where each piece of text comes from (TextTables, Footnotes, regular Paragraphs) its font properties (i.e., allow treating sequences of TextPortions

Re: [api-dev] crash and PyUNO

By the way, I do something in my python package that I am not very sure about. It works and just doing differently wouldn't be of much use because I don't know how to controlledly reproduce the crash. 1 - I provide a service that creates text iterators. The text iterators are not themselves

Re: [api-dev] xcs files: incompatibility between 1.5 and 2.0

Thank you very much, Stephan and Jüergen! Selon Stephan Bergmann [EMAIL PROTECTED]: Jürgen Schmidt wrote: Hi Jorge, first of all it isn't a good idea to attach zip files to mails on this mailing list. Your package depends on the install order, but the order is not guaranteed (at

[api-dev] aborting enums

Hi, all! Is there any problem leaving an enum object not completely exhausted (i.e. not having nextElement invoked as many times as possible)? Should I call a special cancel method? Thanks in advance. Cheers, Jorge. - To

[api-dev] text iteration in OOo 2.0.2: bugs?

Hi, all! I am trying to port a uno package to 2.0 that runs fine in 1.5. However, the behavior of text iteration primitives has changed a bit since (by the way, I am using version 2.0.2, US English, with SDK 2.0). I've noticed some enhancements but also what seems to be bugs. Please have a go at

[api-dev] PyUNO and 2.0: components stuck in 2nd ride

Hi, all! I am striving to make some python UNO components work for 2.0.2 on linux, while they worked fine for the previous stable version (on any system). I am still trying to isolate the problem so I can post an issue, but I guess I'll tell my story anyway to see if anybody has experienced

[api-dev] toolbar glue or adding to standard toolbar groups

Hi, all! It seems to be new behaviour in OOo 2.0 that when a new toolbar group is added (by means of a .xcu) it appears floating by default so the user is free and encouraged to place it wherever they see fit. I myself find this great, but I have a client that find it annoying... Well, so here

Re: [api-dev] toolbar glue or adding to standard toolbar groups

Selon Laurent Godard [EMAIL PROTECTED]: i think the question is - i define an addon containing a toolbar - when deploying the addon is floating - user has to drag it to dock it manually How to deploy an addon containing a toolbar so that it is docked automatically ? I couldn't put it