Difference between revisions of "Talk:Custom functions"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Should semicolon necessity be even more obvious?)
Line 6: Line 6:
  
 
: Sorry I missed it. A good explanation about where to write code is already in the article [[Extensions development basic]] page. Maybe ''Extensions development basic'' is not the best name. I think ''OpenOffice.org Basic'' might be a better name. The title ''Basic'' alone would just be too meaningless or else I would just suggest it instead. [[User:Jebix|Jebix]] 04:37, 6 July 2006 (CEST)
 
: Sorry I missed it. A good explanation about where to write code is already in the article [[Extensions development basic]] page. Maybe ''Extensions development basic'' is not the best name. I think ''OpenOffice.org Basic'' might be a better name. The title ''Basic'' alone would just be too meaningless or else I would just suggest it instead. [[User:Jebix|Jebix]] 04:37, 6 July 2006 (CEST)
 +
 +
== Should semicolon necessity be even more obvious? ==
 +
 +
I've added a note to the page about how you must use a semicolon instead of a comma to separate your arguments for custom functions, because I've just spent around 40 minutes looking for why my function wasn't working and it came down to that. Silly I know, but if I did it I'm sure other people have done it too.
 +
 +
However, do you think this is enough? Right now it's a note under the second example - should it be even more obvious, perhaps as a note under the first paragraph? <br/>-- [[User:Darloth|Darloth]]

Revision as of 09:59, 6 December 2007

Where to put code

It's great to see some explanation on creating custom functions. I have not seen the functions I write show up in the function wizard in the Function list box of the Functions tab. This made me believe at first that I was not putting my custom function code in the right place or that I needed to change a setting.

Could someone explain where exactly the code should be placed? Jebix 04:04, 6 July 2006 (CEST)

Sorry I missed it. A good explanation about where to write code is already in the article Extensions development basic page. Maybe Extensions development basic is not the best name. I think OpenOffice.org Basic might be a better name. The title Basic alone would just be too meaningless or else I would just suggest it instead. Jebix 04:37, 6 July 2006 (CEST)

Should semicolon necessity be even more obvious?

I've added a note to the page about how you must use a semicolon instead of a comma to separate your arguments for custom functions, because I've just spent around 40 minutes looking for why my function wasn't working and it came down to that. Silly I know, but if I did it I'm sure other people have done it too.

However, do you think this is enough? Right now it's a note under the second example - should it be even more obvious, perhaps as a note under the first paragraph?
-- Darloth

Personal tools