Issue 73521 - BASIC: Macros not saved
Summary: BASIC: Macros not saved
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.2
Assignee: vg
QA Contact: issues@framework
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-01-16 14:10 UTC by joerg.skottke
Modified: 2008-05-17 23:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2007-01-16 14:10:47 UTC 
Automated Test: framework/basic/f_basic_modules.bas::tMore_Modules_Dialogs

Reproduction:
- Create a new document
- Attach a macro to the document
- Save it
- Close and reload it
-> There will be no macro security warning/The document does not contain any macros
Comment 1 ab 2007-01-17 08:50:46 UTC 
ab->sb: As discussed to you
The code for creating the Basic folder inside the document storage
is placed in src.m199\basic\source\uno\namecont.cxx, line 1603:
xLibrariesStor = xStorage->openStorageElement( maLibrariesDir, 
    embed::ElementModes::READWRITE );
In the following lines the libraries are stored into this folder.
Comment 2 Stephan Bergmann 2007-01-17 09:43:02 UTC 
This is a problem of the Sun Hamburg builds.  At least for
unx(lngi6|sol(i|s)4)[.pro], the incompatible change to
basic/inc/namecont.hxx:1.3 has not been reflected when building sfx2:

~> ll basic/inc/namecont.hxx
  ... 2007-01-03 13:11
~> ll sfx2/*/slo/appbaslib.o
  ... 2006-12-22 12:19
  ... 2006-12-22 14:20
  ... 2006-12-22 12:46
  ... 2006-12-22 12:53
  ... 2006-12-22 15:25

@vg:  Probably best to do complete re-builds of sfx2 on the next SRC680/OOF680
builds.
Comment 3 vg 2007-01-24 17:50:23 UTC 
fixed in m200
Comment 4 ace_dent 2008-05-17 21:42:43 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 5 ace_dent 2008-05-17 23:47:30 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew