On Thu, 2013-11-21 at 17:06 +0100, Lionel Elie Mamane wrote:
> As a matter of example, here is how to detect the alluded to
> change. 't would be nice if someone posted it on some documentation /
> FAQ / code snippets website.
I added your nice fragment to the 4.1 release notes in the wik
On 11/26/2013 01:56 PM, Lionel Elie Mamane wrote:
On Thu, Nov 21, 2013 at 08:34:04PM +0100, Jan Holesovsky wrote:
Thomas Krumbein píše v Pá 15. 11. 2013 v 15:43 +0100:
Well, this change was a small technical thing - but with a very big
influence on typical market applications. Every custom ma
On 26/11/2013 17:42, Lionel Elie Mamane wrote:
On Tue, Nov 26, 2013 at 02:36:41PM +0100, Fernand Vanrie wrote:
On 26/11/2013 13:56, Lionel Elie Mamane wrote:
On Thu, Nov 21, 2013 at 08:34:04PM +0100, Jan Holesovsky wrote:
Thomas Krumbein píše v Pá 15. 11. 2013 v 15:43 +0100:
Well, this change
On 26/11/2013 13:56, Lionel Elie Mamane wrote:
On Thu, Nov 21, 2013 at 08:34:04PM +0100, Jan Holesovsky wrote:
Thomas Krumbein píše v Pá 15. 11. 2013 v 15:43 +0100:
Well, this change was a small technical thing - but with a very big
influence on typical market applications. Every custom macro a
On Thu, Nov 21, 2013 at 08:34:04PM +0100, Jan Holesovsky wrote:
> Thomas Krumbein píše v Pá 15. 11. 2013 v 15:43 +0100:
Well, this change was a small technical thing - but with a very big
influence on typical market applications. Every custom macro application
with dialogs or forms
Hi Thomas,
Thomas Krumbein píše v Pá 15. 11. 2013 v 15:43 +0100:
> >> Well, this change was a small technical thing - but with a very big
> >> influence on typical market applications. Every custom macro application
> >> with dialogs or forms for user interfaces is influenced if dialogs/forms
> >
On Mon, Nov 18, 2013 at 10:47:57PM +0100, Cor Nouws wrote:
> Thomas Krumbein wrote (14-11-13 09:21)
>> Because in LO 4.1 we have some API-changes, macros should now have a
>> version-switch.
>> There are different methods to get the internal version-number - that is
>> not a problem.
>> But: The
On 18/11/2013 18:32, Lionel Elie Mamane wrote:
On Mon, Nov 18, 2013 at 06:10:34PM +0100, Fernand Vanrie wrote:
On 18/11/2013 18:02, Lionel Elie Mamane wrote:
On Fri, Nov 15, 2013 at 03:43:10PM +0100, Thomas Krumbein wrote:
Am 15.11.2013 15:35, schrieb Jan Holesovsky:
Thomas Krumbein pÃÅ¡e v
On 18/11/2013 22:21, Lionel Elie Mamane wrote:
On Mon, Nov 18, 2013 at 09:10:34PM +0100, David Ostrovsky wrote:
Lionel Elie Mamane wrote on Mon Nov 18 09:32:57 PST 2013
On Mon, Nov 18, 2013 at 06:10:34PM +0100, Fernand Vanrie wrote:
yep conversions are not the problem, its the exiting code who
Hi Thomas, *,
Thomas Krumbein wrote (14-11-13 09:21)
Because in LO 4.1 we have some API-changes, macros should now have a
version-switch.
There are different methods to get the internal version-number - that is
not a problem.
But: The version number itself is not suffcient because AOO 4.1.0 wi
On Mon, Nov 18, 2013 at 09:10:34PM +0100, David Ostrovsky wrote:
> Lionel Elie Mamane wrote on Mon Nov 18 09:32:57 PST 2013
>>> On Mon, Nov 18, 2013 at 06:10:34PM +0100, Fernand Vanrie wrote:
>>> yep conversions are not the problem, its the exiting code who is
>>> broken in many places ?
>> What
Lionel Elie Mamane wrote on Mon Nov 18 09:32:57 PST 2013
>> On Mon, Nov 18, 2013 at 06:10:34PM +0100, Fernand Vanrie wrote:
>> yep conversions are not the problem, its the exiting code who is
>> broken in many places ?
>What exiting code?
This Basic-Macros excerpt:
oDlg.getControl("myDateField"
On Mon, Nov 18, 2013 at 06:10:34PM +0100, Fernand Vanrie wrote:
> On 18/11/2013 18:02, Lionel Elie Mamane wrote:
>>On Fri, Nov 15, 2013 at 03:43:10PM +0100, Thomas Krumbein wrote:
>>>Am 15.11.2013 15:35, schrieb Jan Holesovsky:
Thomas Krumbein píše v Pá 15. 11. 2013 v 13:43 +0100:
>Well, th
On 18/11/2013 18:02, Lionel Elie Mamane wrote:
On Fri, Nov 15, 2013 at 03:43:10PM +0100, Thomas Krumbein wrote:
Am 15.11.2013 15:35, schrieb Jan Holesovsky:
Thomas Krumbein píše v Pá 15. 11. 2013 v 13:43 +0100:
Well, this change was a small technical thing - but with a very big
influence on ty
On Fri, Nov 15, 2013 at 03:43:10PM +0100, Thomas Krumbein wrote:
> Am 15.11.2013 15:35, schrieb Jan Holesovsky:
>> Thomas Krumbein píše v Pá 15. 11. 2013 v 13:43 +0100:
>>> Well, this change was a small technical thing - but with a very big
>>> influence on typical market applications. Every cust
Andrew ,
the problem is :
"stardiv.Toolkit.UnoDateFieldControls" who has until 4.0 a "date"
property who is a ISO representation of the datevalue.
Since 4.1 this date property is a structure (day, month, year) who is
more handy but painfull for us with hundreds of code lines using the
isoval
Just to point you to some other options. The basic library Tools that
comes with LibreOffice contains a few interesting macros related to
this. You need to load the library first then you can use GetProductName.
BasicLibraries.LoadLibrary("Tools")
msgbox GetProductName
If you need more
Hi Miklos,
yes, thanks, that might be a practible way at this time.
Nevertheless - it is not a solution for the future.
I guess, there should be an implementation of the original product name,
version-number (major and minor) and actuall product name.
This should be easy accessible even for une
Hey Kendy,
Am 15.11.2013 15:35, schrieb Jan Holesovsky:
> Hi Thomas,
>
> Thomas Krumbein píše v Pá 15. 11. 2013 v 13:43 +0100:
>
>> Well, this change was a small technical thing - but with a very big
>> influence on typical market applications. Every custom macro application
>> with dialogs or f
Hi Thomas,
Thomas Krumbein píše v Pá 15. 11. 2013 v 13:43 +0100:
> Well, this change was a small technical thing - but with a very big
> influence on typical market applications. Every custom macro application
> with dialogs or forms for user interfaces is influenced if dialogs/forms
> using Date
On 11/15/2013 07:43 AM, Thomas Krumbein wrote:
Every custom macro application with dialogs or forms for user
interfaces is influenced if dialogs/forms using Date/time fields. And
typicly most of them (in my applications about 70%) used those fields.
So all applications will crash using LO 4.1.
Hi,
On Fri, Nov 15, 2013 at 01:43:38PM +0100, Thomas Krumbein
wrote:
> Thanks for this - I know the xcu files. But this is not an easy access
> for (Basic-) macros. The way to do is: Search for this file, parse this
> file and extract the vendor name... for basic marcos a very long way.
Why not
Hey Michael,
Am 15.11.2013 12:53, schrieb Michael Stahl:
> On 14/11/13 09:21, Thomas Krumbein wrote:
>> Hey all,
>>
>> I am looking for an easy way to find out, which product (LibO or AOO) is
>> installed and currently activ via Basic Macros.
>>
>> Because in LO 4.1 we have some API-changes, macro
On 14/11/13 09:21, Thomas Krumbein wrote:
> Hey all,
>
> I am looking for an easy way to find out, which product (LibO or AOO) is
> installed and currently activ via Basic Macros.
>
> Because in LO 4.1 we have some API-changes, macros should now have a
> version-switch.
i hope the API changes ar
24 matches
Mail list logo
