Re: [dev] anonymous namespace

Hello Takashi, > Maybe it is better to move the contents of > dbaccess/source/core/misc/propertybag.hxx > and ucb/source/inc/regexpmap.tpt to the main source respectively. They seem > to be > used in only single main source. Since I'm in charge of the propertybag implementation, feel free to

Re: [dev] Wiki: C++ Helper Documentations

Hi Eike, > Anyway, does someone know where the extension's ugly colours can > be redefined? Light cyan on a light background, even if light grey, is > almost impossible to read. I raised that on [EMAIL PROTECTED], the current state is: It should be possible in the Wiki installation, we don't kno

Re: [dev] interface-announce feedback

Hi Bernd, > So the question is what shall we do for api changes mails as opposed to > feature-mails. Just always use [EMAIL PROTECTED] or look > at the ModulesAffected list and direct to appropiate project specific > list? If the later is the case what do we do if more than one module is > aff

[dev] interface-announce feedback (was: [dev] feature feedback channels)

Hi Bernd, >> This can even be automated (sic!), since for the feature mail, you need >> to specify a project, anyway, which means the mail goes to >> [EMAIL PROTECTED] Adding some additional "feedback to >> [EMAIL PROTECTED]" should be easily possible, /me thinks. > > Just adding that mentally to

[dev] Wiki: C++ Helper Documentations

Hi, Long ago, I suggested in this list to collect documentation about C++ helper classes in our various helper modules (comphelper/unotools, at least), since I had (and still have) the uncertain feeling that a lot of the helper code is not widely known, resulting in duplication of code across the

Re: [dev] read-only configuration data - unremoveable set nodes?

>>> in addition to oor:finalized you can use oor:mandatory here so the >>> content can't be changed and removed. >> That did the trick! Thanks a lot, that's exactly what I need! > > I was too fast ... :( > > In fact this works great when adding to a node in the shared > configuration layer > (sh

Re: [dev] read-only configuration data - unremoveable set nodes?

>> in addition to oor:finalized you can use oor:mandatory here so the >> content can't be changed and removed. > > That did the trick! Thanks a lot, that's exactly what I need! I was too fast ... :( In fact this works great when adding to a node in the shared configuration layer (share/registry

Re: [dev] read-only configuration data - unremoveable set nodes?

Hi Peter, > in addition to oor:finalized you can use oor:mandatory here so the > content can't be changed and removed. That did the trick! Thanks a lot, that's exactly what I need! Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems

Re: [dev] I'd love to fix bug #82798

Hi Mike, Hi Thomas, > To get your fix integrated in the codebase is a little harder, look > on the wiki for developer and cws. Not really, provided it has sufficient quality. In the given case: Thomas, when you have a fix, make a diff (unified context diff is preferred), attach it to the issue

Re: [dev] feature feedback channels

Hi Eike, > This seems to be a misunderstanding, the @ooo I used above was meant to > be read as @openoffice.org, no project involved. Okay, I in fact misunderstood it. So you also suggested one global feedback list ... >> Perhaps [EMAIL PROTECTED] could be the choice >> then. It would contradict

Re: [dev] feature feedback channels

Hi Eike, >>> This can even be automated (sic!), since for the feature mail, you need >>> to specify a project, anyway, which means the mail goes to >>> [EMAIL PROTECTED] Adding some additional "feedback to >>> [EMAIL PROTECTED]" should be easily possible, /me thinks. > Just adding that mentally t

Re: [dev] Re: feature feedback channels

Hi Joe, >> ... >> I like this idea. ... > > Cool! /me liking it doesn't mean anything about the probability for it to be implemented :) > Of course now there are some replies appearing on > [EMAIL PROTECTED], so maybe that's the simplest thing. > > I read the list through Gmane, where it appea

[dev] feature feedback channels (was: [dev] Re: [allfeatures] new/OOo 2.4 : Context menu entry to quickly insert picture background for slides)

Hi Joe, > There should be some link on the feature announcement, either to an > issue id, or to a mailing address ([EMAIL PROTECTED] is not > useful to outsiders!) or mailing list where comments can be made that > will definitely be seen by the iTeam. I expect most will get no > comments, but

Re: [dev] automatic release notes

Hi Cor. > Could this meet 'your' needs, Frank > http://wiki.services.openoffice.org/wiki/New_Features_2.3#Full_list Ah, that's cool! Who is in charge of this page? Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.

[dev] automatic release notes (was: [dev] REMINDER: use specification templates for specifications)

>>> Note that everywhere where there is a "feature-info:" in the "Spec. >>> abstract" column of the Release Notes the process used a dirty fallback >> Why is that fallback "dirty"? I don't think that everything mentioned in >> the release notes needs a full blown specification. > > Seconded. /m

Re: [dev] $Author$

Hi Heiner, >> A reason to drop at least the $Author$ field from the legal headers, to >> avoid confusion? (I wonder, anyway, why RCSs are designed and used in a >> way where the RCS modifies the stored content---expanding $...$ >> fields---, as that cannot work in general.) > > Yes, yes pleas

Re: [dev] odb file format

Hi Ariel, > I'm sure in [EMAIL PROTECTED], the mailing list for development > inside the Database Access project, you will be able to ask directly Thanks for attracting more people to this list ;) > to > the project's leader: Frank Schönheit. I'm not sure if he is following > this mailing list

Re: [dev] odb file format

Hi Andy, > I posted to OOForums a little enquiry about how you are accessing HSQL > files in the zipped .odb file. I'm writing some standalone java code to > access an odb file. I've seen plenty examples in the SDK for calls to an > instance of UNO, but can this be done with reference to a self

Re: [dev] Re: GetWorkingDocument in ScVbaApplication

Hi Noel, >> Only if the document/model is implemented using an >> SfxObjectShell/SfxBaseModel. > well currently I am only interested in calc which fits the bill but I > take your point ( /me wonders what documents aren't based off > SfxBaseModel ( probably a stupid question but ) ) databas

Re: [dev] Re: GetWorkingDocument in ScVbaApplication

Hi Noel, >> which is the correct way IMO. If you already addressed this elsewhere - >> even better, saves time on my side :) > well its not clear when cws-npower7 ( where the fix is ) will be > integrated so probably you should just go ahead ( maybe try and keep the > change on the same line t

[dev] Re: GetWorkingDocument in ScVbaApplication

Hi Noel, I continue this in dev@openoffice.org, since I think we meanwhile have some important clarifications on the topic ... >> Is the sc/source/uivba directory built, actually (it breaks when >> including the sfxbasemodel.hxx, in m222)? > erm yes and no, it's not built by default, of course no

[dev] SfxObjectShell::Set/GetWorkingDocument, and how to get rid of it

Hi, in the course of UNOizing the Basic IDE (so it will finally be able to work on documents which are not implemented using the SfxObjectShell), I stumbled upon SfxObjectShell::Set/GetWorkingDocument. As I understand it, the WorkingDocument is a dedicated document (SfxObjectShell, that is), whic

Re: [dev] proposal for change of cws policies

Hi Mathias, >> a "product" version is one that has .pro suffix at the output trees >> (that's the default case). A "non-product" has no such suffix, and >> gets enabled via --enable-dbgutil at the configure line. We should >> rather advertise this a bit more, because people then get assertions >>

Re: [dev] proposal for change of cws policies

Hi Martin, > Unfortunately they will also get assertions with a vanilla build, > which makes this less useful. I wasted a lot of time trying to > track down the cause of an assertion, assuming it was due to a > change I had introduced, before discovering it still occurred > with a clean checkout.

Re: [dev] proposal for change of cws policies

Hi Kohei, > 1) The use of "product" and "non-product" terms seems unclear to me. > What do they mean exactly? http://wiki.services.openoffice.org/wiki/Non_Product_Build Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http:/

Re: [dev] Deprecated license SISSL in the source code again!

Hi Pavel, >>> But we should not allow any new files with this license to be >>> integrated! >> Do you suggest to enforce this by tooling? > Yes. And not only by tools, but also by humans ;-) Oops ... how would this be look like. Will RE have guns underneath their desk? What I wanted to say: Erro

Re: [dev] Deprecated license SISSL in the source code again!

Hi Pavel, > do you remember my previous "SISSL" mails? The license still comes > back to our sources... Which is unbelievable for me. one reason for this (at least for the files in your list where it's my responsibility) is that the files where introduced in CWS' long before the license change,

Re: [dev] rtl::Reference vs. [com::sun::star::]uno::References

Hi Andreas, > why not preventing "using namespace" in general As a general rule? No, I wouldn't like to impose this on everybody, this is an unnecessary restriction, IMO. As a personal habit? Well, why not. > and using namespace alias instead ... > ... Personally, my preferred solution is a seq

Re: [dev] rtl::Reference vs. [com::sun::star::]uno::References

Hi Kay, > We assume, that people using "using rtl;" mostly intend to use the RTL > string That's my experience, too. Whenever I stumbled upon the problem you described, replacing "using namespace rtl" with "using ::rtl::OUString" fixed it. > and string buffer classes. Therefor we suggest to jus

Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?

Hi Mathias, > About the problem you > mentioned: it would need a permanent maintenance to keep the versions > updated, yes. But that happens anyway when new versions arrive. So let's > hope old versions can be removed as easy as new ones can be added. Sorry, but "let's hope" isn't a good basis.

Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?

Hi Allen, > How about just changing the UI on the website? We could make it so that > normally only the "active" versions would be displayed in the scrolling > list, but somewhere there would be a checkbox or other option to make it > display all versions. In the search screen, we could also add

Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?

Hi Caolan, > I'd hope that we could just remove the ability to *add* new bugs against > those milestones. i.e. that we'd just list the last couple of milestones > and the actual releases as options on the bug submission pages. I'm all > for leaving the current "version" that bugs are logged agains

Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?

Hi Caolan, > There are 470, four hundred and seventy! "versions" listed by issuezilla > for e.g. tools. way too much, agreed. The better solution would be if Version was a free-text field, but alas ... > Can we cull these to at least remove all the milestones < current - 5, > and consider droppi

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Hi Joerg, > We haven't identified the tests. The requirements was that they should > be "rock solid" and we have given those RESOURCE and MAIN FUNCTIONALITY > tests to customers and they were able to deal with them. > > It makes sense to use firstly less than these ~45 and have a look if we >

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Hi Joerg, > Do you agree to make regression testing with the testttol BEFORE you > (the developer) give your work to the QA to get CWSes faster integrated? > You won't have to maintain the testing code neither do you have to learn > the script language or debugging the test code Hmm? Do you

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Hi Thorsten, > Currently we talked about a subset of 45 test cases, which were used for > release testing also. These tests needs round about one night - max 12 > hours. As I remember correctly the discussions with Jörg, we want to > make a subset of these tests as required first. They should run

Re: [dev] Re: [qa-dev] Can we do more regression testing?

Hi Thorsten, >>That's important indeed. If I have to wait several days betwen finishing >>my builds and passing the CWS to QA, just "because" of the test, this >>would certainly be a serious hurdle. > > Generally, no. For a normal CWS, cycle time in QA is weeks, so this > really does not add sign

Re: [dev] info about red tinderbox status in EIS now available in OOoWiki

Hi Bernd, > A new Wiki page for the red tinderbox status shown in EIS and what you > can do if you have that to get more detailed information etc. is now > available. > > The Wiki Entry is at: > > http://wiki.services.openoffice.org/wiki/RedTinderboxStatusInEIS A good start for the whole issu

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Bjoern, >> However, Mathias seemed to suggest that cwsanalyze is able to detect >> problems which are not detected by cwsresync. At least this is how I >> understood his mail. And that's the part I don't understand. > > I don't understand that, too. But, I have evidence that it is true. > ...

Re: [dev] How to include inter-module headers

Hi Stephan, > > > delivered us from hedabu. > > However, the way this was done lead to the module-local inc/$PRJNAME > (where PRJNAME is the module name) to be added to the C/C++ compiler > include search path

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Rüdiger, > there always may be special cases which cannot be detected automatically. > Image f.e. on your CWS you removed a header. With m209's hedaburemove01 > that header got moved on the master workspace. CVS does not know about > moving files, so it is a removal and a new file elsewhere.

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Mathias, > In case you wonder how you can find out which header files you might > have changed: use cwsanalyze to find all changes in your CWS. This is > the best way to avoid problems, it is known that not all possible > combinations of header changes cause errors or alerts in the resync > pro

Re: [dev] Removing the ability to write data into ODB files

Hi Matthias, > On 2/14/07, Frank Schönheit - Sun Microsystems Germany > <[EMAIL PROTECTED]> wrote: >> Okay, didn't know there was a list of all drivers in the DevGuide. >> Sounds strange and not very fruitful. > > This table is very useful. It lists the drivers, the URLs to specify > for getting

Re: [dev] Removing the ability to write data into ODB files

Hi Matthias, > Okay. That's a piece of information I've been missing. I checked the > Dev Guide but didn't find HSQL listed in the table of drivers and > since the table is prefixed with "Below is a list of all available > drivers." I concluded that storing data directly in ODB files is > special

Re: [dev] Removing the ability to write data into ODB files

Hi Matthias, > For policy reasons we want to prevent users from storing data directly > inside ODB files. But we want to retain all of OpenOffice.org features > for other database types that use external storage. Does anyone have > an idea how we can achieve this? Try removing the hsqldb2.dll (re

[dev] copying/stripping "basic" to "binfilter"

Hi, In the course of issue 73329, I copied a stripped version of the "basic" module to "binfilter" (binfilter/bf_basic, building a bf_sb lib). The code base used for this was a 680m199. As a consequence, and as long as the respective CWS (basmgr02) is not integrated (which might take a while due

Re: [dev] Extending the binfilter Module

Hi Rüdiger, > Thanks for the details. Yes, I totally understand your problem, I think. > But, what you did is what I proposed, not what was written here as > recipe. You first evaluated to adapt binfilter to the incompatible > changes. After spotting all the difficulties you searched for an alt

Re: [dev] Extending the binfilter Module

Hi Rüdiger, being late to the thread, and being the one who implicitly initiated this ... > Why would you copy additional stuff into binfilter? Because binfilter has a code base which lives several years in the past, whilst the current code base moves forward constantly. At some point, you simpl

Re: [dev] Unable to create ODBC tables and unreadable error dialog.

Hi Henrik, > I haven't got any response on this in the users-list or in the > issue-zilla. You could/should have tried [EMAIL PROTECTED], too :) (though entering IZ is usually a good idea, too). > see: http://qa.openoffice.org/issues/show_bug.cgi?id=73636 I suppose you ran into another occuranc

Re: [dev] inline funtions: control may reach end of non-void function (compiler bug on Mac OS X)

Hi Pavel, > I see several "fixes" to this: > > - adding return FALSE; at the end of the inline function This might lead to warning "unreachable code" with other compilers, so > - removing "else" seems better. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - S

Re: [dev] Working with the Invisible-mode

Hi Fabian, > I tried this but StarDesktop seems to be a StarBASIC-only-variable but I use > the Java-Interface. The corresponding Java-class "XDesktop" does not have the > mehtod loadComponentFromURL() You need to create an instance of the com.sun.star.frame.Desktop service, and query it for XC

Re: [dev] Distributing data sources to multiple machines

Hi Matthias, >>If you desire the "data source" to be a registered data source, well, >>then you must run a script to register each base document. > > You say "script", does that mean there is a command line tool or > options to call soffice with that will do that? Or do you mean I'll > have to wr

Re: [dev] base

Hi Glen, > I was looking to work on base. I would like to do forms and reports. What exactly are you looking for? Contribution of source code, bug fixes, features, documentation, QA? Do you have own detailed plans what you want to do, or are you still looking for something to start with? If the l

Re: [dev] In the Works: New OOo C++ Coding Standards

Hi Thorsten, >>A little bit of naming convention is certainly needed. Nobody wants to >>see a mixture of >> Foo aFoo(maFoo); >> CFoo foo(_foo); >> foo f_(f); >>even if it's in different modules. > > OK - so, what naming scheme would you propose? *gulp* No, please let's not start this. Chance

Re: [dev] An attempt of a summary: specification process possibilities

Hi Jörg, > to go a step further: Do we need such feature mails at all? Couldn't we > instead offer RSS feeds (per project?) which list the most recently > integrated CWSs and their feature descriptions? It's a matter of taste and/or working habit whether you want to read a Feed or a mailing lis

Re: [dev] updating database form controls on events

Hi tofergus, > option two was to find the parent of the control which would presumably > be the form and search for the required peer item. this also appears > impossible as the control is not actually a FormComponent. I suppose that your event is sent by the control, not the control *model*. On

Re: [dev] An attempt of a summary: specification process possibilities

Hi Mathias, > At the risk of being caught ignorant: should feature/changes mails on > these lists be posted before the CWS is approved? I think that odds > aren't low that something might get changed after handing over the CWS, > especially in case of new developers. AFAIK policies require mails

Re: [dev] Bad PRJNAMEs

Hi Stephan, > Attached are two quick and dirty scripts that worked for me (within > Hamburg build environment on a Linux box) to find all the places where > PRJNAME is probably set wrongly (see below). Feel free to fix those you > feel responsible for. In case nobody already volunteered to fi

[dev] test frameworks (was: [dev] Specifications - summary & suggestions ...)

Hi Thorsten, > well, there actually _are_ several test frameworks in place. From what > you've probably in mind, testshl2 should come close. It's basically > cppunit dressed up to work in OOo's build environment. See > e.g. o3tl/qa/makefile.mk on how to employ it. Always learning something new ..

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Christian, >>Yes: It's one time 9 days of work, as opposed to 9 times one day of work :) > No. For the user it is 3 times a different behaviour instead of one > change. Okay, wasn't clear that you talk about changes in the feature after users have seen it. Even then - if this happened in a sn

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Christian, >>>And if you need to change your whole feature multiple times, then you >>>ought to thing before. (and again this doesn't relate on how to actually >>>code it, but on what the feature is supposed to do) >> >> Anyone that thinks they can sit down and design a perfect system and

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Thorsten, >>However, far more important than a string review, IMHO, would be to drop >>German as a developer provided second source localization. Let's get rid >>of that. > > Aww, of course. I thought we already did that. :-/ +1 here. That's an obsolete requirement for an international projec

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Nikolai, >>>The developer not only should be, but is responsible for this. >>... >>Wouldn't you agree that in case the developer is "only" the developer, >>but does not take any of the other two mentioned roles, then it's *not* >>her responsibility to ensure the synchrony? > > No, I wouldn't.

Re: [dev] The QuickStarter Spec.

Hi Michael, > However - reading the win32 spec - it -seems- that the specification > for this feature is almost totally absent involving the immortal lines: > > "...is kept unchanged to the implementation used in OOo 1.1". > ... > There is a screenshot, but no technical detail -

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Nikolai, >>Ideally, the developer should also be responsible for updating the >>spec document to ensure that it keeps up with the requirement change >>over the development cycle. > > The developer not only should be, but is responsible for this. Really? The new specification template separa

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi David, > For issue 12719 I attempted to have a faster and more accessible > specification process > This involved developing the spec collaboratively in the wiki > Unfortunately the spec team did not like this idea and have gone for an > OOo template for designing specifications with > This i

Re: [dev] Specification Process Possibilities ...

Hi Hirano, > I encourage community developers and CJK developers to access the spec > project wiki [1] and the spec template [2]. > > http://specs.openoffice.org/servlets/ReadMsg?list=dev&msgNo=59 > http://specs.openoffice.org/servlets/ReadMsg?list=dev&msgNo=83 > > Can you help fix them? I just

Re: [dev] OOo Digital Signatures

Hi Rene, > We should try to get rid of the Mozilla crap (remember: we still are shipping > a > unmaintained, old, unsupported, security-buggy version), also for LDAP > access, but > that's an other story... Glad to hear you volunteer to work on this, it is definitely most welcome. For both the

Re: [dev] A word about (missing) Specification Documents and (late) Feature Mails

Hi Rüdiger, > while you made some valid points, this one does not hold: > 1) Timing of integration is not under control of CWS owner. Program > Management is responsible here. > 2) Integrating the CWS on 2006-10-06 is in time. UI freeze of 2006-10-05 > means that your CWS has to be approved by Q

Re: [dev] A word about (missing) Specification Documents and (late) Feature Mails

Hi Michael, Additional to the good points already raised by Mathias (which I agree to in really every item), my opinion on this: The general idea is: Involve people early, not after it's done and integrated. Nobody can oversee *everything* alone, and if you ask other stakeholders, they might have

Re: [dev] Text Labels in Properties Dialog

Hi Alan, > When you edit a form in the database app, and view the properties of a > column, the properties dialog has labels for each field. Those labels > are composed of the text labelling the field and dots which fill out the > space between the text and the field's value. In RTL, the dots a

Re: [dev] How to remove Database from File/New

Hi Matthias, > Is it possible to remove the "Database" entry from File/New? see share/registry/org/openoffice/Office/Common/Common-base.xcu in your installation. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.su

[dev] introducing DialogDump

Hi, for those of you who need to create VCL dialogs more or less frequently ... you might be interested in DialogDump: http://wiki.services.openoffice.org/wiki/Dialog_Dump Citing the introduction: Every OpenOffice.org developer who ever needed to create a VCL dialog knows that this can be a ...

Re: [dev] Warning free code: some more warnings that might be disabled

Hi Thorsten, > What I intended to say was, that this feature is not obvious, seldomly > used, and therefore 'obscured' from plain sight - do I make sense now? Yeah, probably. (What I intended to say was: what I've learned during reading zillions of line of code inherited from others is that patt

Re: [dev] Warning free code: some more warnings that might be disabled

Hi Thorsten, off-topic, but ... > I consider this behaviour a useful (if obscure) feature of c++ "useful and obscure" ... I'm tempted to call this an oxymoron :) Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.s

Re: [dev] Interface getSdbcScheme

Hi Takashi, > Recently new interface getSdbcScheme is added to mozabdrv but in > connectivity/source/drivers/mozab/MConnection.(cxx|hxx), the function has C++ > linkage. > > Is it done intentionally? It breaks mingw port build and I wonder if I should > wrap > 'extern "C"' with '#ifdef __MING

Re: [dev] Where do control colors come from?

Hi Éric, >>>The colors you describe - are they from the theming of your OS? >> >>Indeed, they do seem to react to the KDE Color Theme I select in kcontrol. >>I should have tried this earlier. >> >>Thanks. That's all I wanted know. > > I am quite puzzled by this answer. Me too :) I don't know th

Re: [dev] Warning free code: the missing modules

Hi Stephan, > forgive me if I missed this in >>the thread: About which order of magnitued do we talk here? 10 places? >>1? > > 10^2--10^3 would be my guess Hmm, that's quite a lot ... Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems

Re: [dev] Warning free code: the missing modules

Hi Stephan, > In the case of sal_Bool, it might be true that false is a better default > value than true (no pun intended), but that need not be the case always, > so you would have to analyze each place in the code where you add "= > false", which is tedious due to the large number of places i

Re: [dev] Warning free code: the missing modules

Hi Stephan, >>So, it seems that we have used the wrong operator here. Therefor I tend >>to agree to Frank, that we may want to fix this. > > The choice of operator is indeed unfortunate. However, I do not agree that > >- T b; >+ T b = T(); > > is in general a fix that improves code qu

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > I'm realizing that it make this useful, a system administrator would > probably need a way to insert the user's username or WinNT domain\username > into the path. So for example, the system administrator could set > RestrictedPath to \\fileserver\userfiles\$(username) and OOo would ma

Re: [dev] Warning free code: the missing modules

Hi Henrik, >>>if (a >>= b) { > ... > But isn't it the left (a) side that gets assigned in a >>= b? > I.e. b is still not assigned and the warning is good and fixing it is > no mutilation? No. >>= here is an overloaded operator which by definition returns sal_True if and only if b could success

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > It would be less complex and therefore less prone to system administrator > and programmer error to just treat a nil and empty string the same. I > suggest: I don't have a strong preference here. In theory, treating "nil" and "empty list" equally is somewhat ... dirty, so I would pr

Re: [dev] RestrictedPath working under Windows?

Hi Joerg, > So how was that supposed to be used? I assume that would be by editing > the soffice script to set that variable before invoking soffice.bin? > (Otherwise a user could always overwrite an environment variable just as > easily.) Not well suited for Windows use then, where there is no

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > That's easy to find. There are only about a dozen matches in the source > code for RestrictedPath and RestrictedPaths ;-) :) > On Windows XP, you have both "system variables" and "user variables". If > both values are set, the user value overrides the system value. In fact, I > ju

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > The answer is "yes, but". I would be interested in fixing it, but I'm not > sure when I would be able to get to it. I do have a potential customer who > is interested in this feature, and if that is an issue for him then I will > fix it. Ah, I'm looking forward to when you come aski

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > With that setting, RestrictedPath mostly worked. With only one directory in > the RestrictedPath, the behavior was not quite what I expected. It allowed > me to navigate up to the parent directories, all the way to the root (c:\). > It didn't allow me to save there, but it was unexpe

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > I'm using what is compiled into the OOo Windows binary distribution and > configured by default, which I'm guessing is the system dialogs. Is there a > way to select OOo's dialogs, either at run-time or build-time? At runtime, Tools|Options|OpenOffice.org|General|[X] Use OpenOffice

Re: [dev] Warning free code: the missing modules

Hi Stephan, > Opinions, anyone? sounds good, except that I would not give complete M2, M3, M4 to one person each. Those are huge tasks, and touch code where you sometimes better know what you're doing, so I suggest to do like before: Let everybody fix his/her own code here. Ciao Frank -- - Fra

Re: [dev] RestrictedPath working under Windows?

Hi Allen, > I'm trying to get "RestrictedPath" working, as described under "Declaring > the Permitted Folders" in > http://ui.openoffice.org/specification/FileDialog_RestrictedPaths.sxw > > I'm using OOo v2.0.3 under WinXP. Do you use system dialogs, or OOo's own dialogs? The feature only works

Re: [dev] Where do control colors come from?

Hi Matthias, > top and left outside: #808080 > top and left inside: #404040 > bottom and right: #d4d0c8 > > When I save this document and open it under Linux, I get the following colors: > top and left outside: #adaead > top and left inside: #00 > bottom and right: #efefef This shouldn't be

Re: [dev] Where do control colors come from?

Hi Matthias, > I've just noticed that form controls have different colors (i.e. > different shades of gray for the 3D-borders) under Windows and Linux. > Where do those colors come from? I'd like to make OOo under Linux look > exactly like OOo under Windows. How do I achieve this? There shouldn't

Re: [dev] getting a file added to the install sets

Hi Michael, > How does the install set know which files from the solver to pack up? I > would like to add some files for my CWS. Is this specified in > instoo_native?? no, scp2. Depending on which file to add, you need to find the right place. I suggest finding an already-packed file with simil

Re: [dev] Suggestion to simplify OpenOffice_Dev installations

Hi Christian, > To answer that: You don't need to use the commandline, > $favourite_GUI_archive_manager/file_manager could do the same... Neither $file_manager nor $favourite_GUI_archive_manager are defined on my system :) Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROT

Re: [dev] Suggestion to simplify OpenOffice_Dev installations

Hi Ingrid, > Yes, one can use "/a" option - but only if one knows about it. This > knowledge is an extra hurdle again. Furthermore it is not sufficient if > you want to install a download package without system integration. > Because you will need to extract the package with a special option fi

Re: [dev] Suggestion to simplify OpenOffice_Dev installations

Hi Christian, >>2) The different installations may conflict in the user installation >>directory as this is shared. So you might get strange bugs. > > the dev-builds have a different user-installation than the stable one. but two different dev builds use the same user installation, and thus can

Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus

Hi Philipp, > Bullshit. The object dying notifies you that it gets destroyed and you > still cannot refrain from using it ? Maybe that's just me, but i would > call THAT a destructive attitude ;-) Mathias already explained that you got me wrong here - in the scenario I described, there was no

Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus

Hi Philipp, > This is based on the fact that the Window destructor does a Hide() > before setting the focus to somewhere else. But this won't help. Window::~Window has not yet been called. In Carsten's example, MyTabPage::~MyTabPage is just being called, and it's just about to destroy its member

Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus

> SomeWindow::SomeWindow() > { > DELETEZ( m_pBar ); > DELETEZ( m_pFoo ); > // note: less obvious versions of this use a > // ::std::auto_ptr< Control > for both m_pFoo and m_pBar, which makes > // the issue harder to spot > } should have been SomeWindow::~SomeWindow, of course Ciao Fran

Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus

Hi Carsten, > we have just found a nasty pitfall in one of our tab pages, which lead > to memory corruption. We needed about one week to track down this issue, > so I hope that someone else can profit from our findings. > ... > If one uses the virtual methods at the Window class > virtual void

  1   2   >