[dev] BASIC Variants, VarType(), and arrays
Can I get a little help from someone who knows the code, to confirm my experimental observations? Then I can get the documentation updated, and fix the BASIC code. The VarType function can be used on a variant to return the type of data therein, as documented. However, when the variant contains an array, VarType apparently returns the value x'2000' (decimal 8192) plus the "simple" type of the array variables, which is not documented. What I'm seeing: If a variant is set with the Array function, VarType returns a 200C (8204) code, indicating type "variant", which is more or less useless. If the variant is set to an existing array: Dim ai(2) as Integer : ai(0) = 1 : v = ai() then the VarType returns 2002 (8194), where "2" is the type code for "integer". Similarly, explicit string arrays return 2008 (8200). Values like these occur in property sets. This affects the OLH and wiki documentation, and BASIC code on the wiki and in the released macro libraries. I'll update the wiki, and file issues for the rest, once I'm sure what to say. -- /tj/ T. J. Frazier Melbourne, FL (TJFrazier on OO.o) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: operator delete mismatch
Am Fri, 09 Apr 2010 15:12:00 -0400 schrieb Terrence Enger : > Is there anything that will capture a record of what I did to get into > an "interesting" situation? It has happened more than once that I > have been trying to reproduced an assertion--but writing down the > steps as I go along, so as to produce a good bug report--when I > fat-finger something (but I am not sure exactly what) which sends me > to a different assertion. This: > http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program could be of some help to figure out what you fat-fingered. ;) However, I fear it is still a bit to "high-level" to be useful in general. But it might give you a hint on what just happened in some situations. Best Regards, Bjoern - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Want to Contribute to open source project
Am Fri, 9 Apr 2010 13:33:31 -0400 schrieb Trevillian Highter : > I would like to contribute to openoffice.org, but not sure where to > start. > > I am a software engineering graduate familiar with an array of > programming languages, concepts and technologies, including C++, C, > Java, HTML, MS Visual Studio.NET, UNIX, Windows XP, MS Office, and > MySQL. Experience teaching/training others and writing documentation. > > Could you provide a starting point. I am really excited to get > started. > Hello Trevillian, great to have raised your interest! To get started with OpenOffice.org development see: > http://wiki.services.openoffice.org/wiki/Development If working directly on the product itself scares you, you will find that there is a lot to be achieved with Extensions. You can get started really quick using the NetBeans integration: > http://wiki.services.openoffice.org/wiki/OpenOffice_NetBeans_Integration Also note that there is the education project to help students to get involved in the project: > http://wiki.services.openoffice.org/wiki/Education_Project Also note that there are various ways to get in touch with the devs directly: > http://wiki.services.openoffice.org/wiki/Communication > http://wiki.services.openoffice.org/wiki/IRC_Communication IRC is a great way to get started. Sometimes you will find grumpy old veterans in our IRC channels -- dont let them scare you, they are just ... grumpy. ;) Best Regards, Bjoern P.S.: The wiki in general is very active is used heavily by many subprojects of OpenOffice.org. Its a good point to get started. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: operator delete mismatch
On Tue, 2010-03-30 at 15:11 +0200, Michael Stahl wrote: > On 30/03/2010 13:31, Terrence Enger wrote: > > ( I think, though, that I am giving up on trying to use a non-product > > build when I actually want to get work done . ) > > before resorting to such extreme measures as not using non-product builds, > try the debug dialog (Control-Shift-Alt-D). > it lets you change assertion reporting from a dialog box to output on > stderr (the option is called "shell"), or to a window. > you can also increase your level of annoyance by enabling "warnings" as > well :) Ah, yes that debug dialog. I tried a non-product build with the intention of learning about that dialog. But before getting there, I got caught up in the assertions, and I have yet to get out of the trap. Is there anything that will capture a record of what I did to get into an "interesting" situation? It has happened more than once that I have been trying to reproduced an assertion--but writing down the steps as I go along, so as to produce a good bug report--when I fat-finger something (but I am not sure exactly what) which sends me to a different assertion. Speaking of bug reports ... I have been attaching a backtrace captured while the Debug Output window is open. And I do that with debugging symbols loaded (which *really* loads down my poor little computer). Are these helpful things to do? Does a backtrace compensate for skimpiness in the "steps to reproduce"? Thanks, Terry. > > regards, > michael > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Want to Contribute to open source project
Hello, I would like to contribute to openoffice.org, but not sure where to start. I am a software engineering graduate familiar with an array of programming languages, concepts and technologies, including C++, C, Java, HTML, MS Visual Studio.NET, UNIX, Windows XP, MS Office, and MySQL. Experience teaching/training others and writing documentation. Could you provide a starting point. I am really excited to get started. Thank You, Trevillian Highter
[dev] Mouse Pointer not changed
Hello In an extension, I create a window with a button. The actionPerformed function (that is called when the button is clicked) first changes the mouse pointer of the button (with XPointer::setType) and then retrieves something on the Internet and displays the result in the window. When I click the button, the mouse pointer is changed only after the result is retrieved and displayed in the window, and not before, as it should. Thanks Patrick - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] How to use DBG_foo?
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
> On Thu, 01 Apr 2010 16:40:11 -0400
> Terrence Enger wrote:
>
>> Greetings,
>>
>> What does it take to use, for example, the DBG_ASSERT function defined
>> in debug.hxx? I have poked around on the wiki without success.
>>
>> I have added enough #include lines to get the file to compile, but now
>> the link step is failing with undefined references to DbgFunc() and
>> DbgOut(). I see that these functions are bound into libtlli.so, but
>> how do I tell the build system to--pardon the pun--make the link?
>
> In general -- dont do it. As Michael Stahl pointed out on:
>> http://wiki.services.openoffice.org/wiki/Writer/Code_Conventions
> "DBG_* is defined in module tools, and therefore evil by definition"
> Consider using OSL_ENSURE and friends from sal/inc/osl/diagnose.h
> instead.
> If you still want you use the evil old tools asserts, you would need to
> find the makefile where the linking gets done (most on the time
> ${MODULE}/util) and add the tool lib to the linked lib like this:
>
> SHL[0-9]STDLIBS+= $(TOOLSLIB)
>
> You would also need to make sure that your module depends (directly
> or indirectly) on the tools module in the prj/build.lst file.
For the tools DBG_foo stuff you also have to build a "nonproduct"
version (--enable-dbgutil in configure). OSL_foo also works in "product"
builds with DEBUG=TRUE.
Regards,
Mathias
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
