Participating Frequently

Answered

Has anyone got the documentation for the following Extensions please?

Forum|Forum|1 year ago
November 13, 2024
11 replies
9366 views

Please only respond if the answer to the following question is yes.

I would like copies of the on-line help files for the following PVII extensions

AMM Adaptive Menu Magic
Art Gallery Magic
Harmony
Slide out Panel magic
ZeitGeist pagePack

Have you got any please? (they were on-line html versions not pdf's. The site is now closed. I've checked in the various web archives online without luck.)

Please note.

If you want a more general discussion around the topic of Dreamweaver and its alternatives, please don't use this post but either create a seperate post or feel free to continue on my original post here

https://community.adobe.com/t5/dreamweaver-discussions/project-seven-pvii-website-and-email-unavailable-does-anyone-here-know-why/m-p/14978272#M229401

Thanks Pat

Correct answer denniscallan

Link to P7 manuals for download from my onedirve cloud follows. Apparently my previous attempt to attach pdfs here didn't work, so here is the safe link to download about 30 pdfs extension manuals and numerous notes https://1drv.ms/f/s!Alutu8kqjhMrgSG0-4cBSHf_3BoM?e=NXxn7r

denniscallan

Inspiring

Greetings again, I have a new solution for our Dreamweaver problems: convert the code to clean HTML5, delete all reference to P7, and you are reborn! My DW site was so broken because of P7 google analytics flunked me repeatedly. Converting the DW code manually would be difficult, so I had AI do it for me, and the results are perfect. I did make serious effort to convert to WordPress, but my site has about 400 pges, which would have taken too much manual effort, many boring months.

Conversion to HTML5 can be done with the correct prompt. Then you can open a favorite AI, feed it the prompt, attached your page code, and let it do the work for you.

There are other apps you can then use to view the new page and tweak the code, especially VS Code, a free app that shows code and displays the layout, similar to Dreamweaver. You could actually use DW for that step, but 2 problems at least, danger of injection of some unwated DW code, and very few useful extensions are availble for this abandoned antiquated app.

Tweak the page code if needed, then swap out your existing pages on your server with the new HTML5 pages. Done.

In my case, with 400 pages to convert, I found that Claude code was amazing. It works directly in your computer DW folder and makes copies for you of fixed pages, so need need to upload and download. There is a price to pay, $100 for 30 days of Max access, and well worth it. Free Claude gives no access to Terminal, and basic pay level of $200/yr gives limited time daily, but Max gives 5 times that access, well worth it.

I have a sophisticated prompt I can try to copy into a following message, but I'm not sure if it will be allowed. Otherwise build your own prompt, basically, get rid of all P7 content and convert to HTML5, but test the prompt with AI asking for refinements.

In onw eek I have converted my 400 pages.

denniscallan

Inspiring

notes:
Following is the text of two prompts for AI to convert DW pages coded with P7 to clean HTML5 pages.
To make things flow more easily you make two prompts, both pasted below. I used Claude, which has the unique feature called Claude code which works directly on files in your computer using Mac Terminal, enabling massive batch operations, because it works directly on files in your computer. You limit the permission to only your website folder. If you don't have that, you can use any AI by manually uploading one DW code page at a time, using the longer prompt.
So I wrote two prompts, long for the root folder, and short for the actual question targeting pages.
Here is the short prompt: you can apply this prompt to your master folder containing all pages, but is better to apply it to one folder at a time.
First, I show you the short prompt with specific instructions targeting particular pages, pointing the AI to the longer conversion prompt that you have placed on your root folder. Got it? Once set up, it is very very easy to excecute.
Following that I will show you the separate prompt I had AI create for my website.

You will need to EDIT BOTH OF THEM and replace references to my Towns of Europe website with yours. Also remove references to YouTube embed if you don't have any on your site. It is useful to run this promopt through your AI first for evaluation and rewrite for you needs.

It is a long, detailed prompt, which I saved as a text file then placed into the root folder of my site on my computer. That made it easier when conducting actual prompt instructions in Terminal to Claude code, which could be much shorter, directing the AI to refer to this prompt in the root folder.
Short prompt for the AI enquiry, then long prompt (conversion-prompt) for root folder.
All of the following is done within Terminal, not in an AI web browser.
-------
{startup commands. This assumes you have already placed the longer conversion-prompt in the root folder.} {Open Terminal and type: }
cd /Volumes/[to the folder containing your dreamweaver site]{enter}
claude --dangerously-skip-permissions {enter}
{then type the prompt:}
Read conversion-prompt.txt and apply those instructions to all .html files in Switzerland/. Write each to the converted/ folder preserving subfolder structure. Do not modify originals. Log each filename and flag any failures. {enter}
----
Substitute `Switzerland/` with whichever country folder you are working on each time.
===================================
Here is the longer prompt that you save as a text file then place in your root folder:
===================================
# Towns of Europe — Page Conversion Prompt
You are converting pages from the Towns of Europe website (townsofeurope.com) from a legacy Dreamweaver / Project Seven setup to clean, valid HTML5 with embedded CSS and no external dependencies except Google Fonts. Apply every rule below exactly and without exception.
---
## Dependencies to remove
- All Project Seven CSS and JS references: any file or class name carrying a `p7` prefix, including `p7HMY`, `p7MXM`, `p7AMM`, `p7STT`, `p7MGM`, `p7DMM`, `p7SCS`, `p7Zeitgeist`, `p7TKGADGETS`, and any others following the same pattern
- All external `<link>` CSS tags except the Google Fonts link specified below
- All external `<script src="...">` tags
- All inline `<script>` blocks that initialise or configure P7 widgets
- All Google Analytics or other tracking scripts
- All duplicate `<meta name="viewport">` tags — keep exactly one: `<meta name="viewport" content="width=device-width, initial-scale=1">`
- The `<meta id="p7HMY">` and `<meta id="p7MXM">` tags
- The p7STT scroll-to-top widget — replace with the vanilla JS scroll-to-top button specified below
- Any `<img>` tag used as the site logo in the header, regardless of its `src` path — replace with the CSS text logo specified below
---
## Google Fonts
Place these three tags in this exact order in `<head>`, immediately before the `<style>` block:
```html
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Montserrat:wght@300;400;600;700;800&display=optional" rel="stylesheet">
```
Use `display=optional` (not `display=swap`) to prevent font-swap CLS. Use this font stack in the CSS `--font` variable:
```css
--font: 'Montserrat', -apple-system, BlinkMacSystemFont, 'Segoe UI', Arial, sans-serif;
```
---
## Design tokens — use these exact values throughout
```css
--red: #c0392b;
--wine: #7b1a2e;
--dark: #1a1a1a;
--mid: #333;
--light: #f5f0eb;
--white: #fff;
--font: 'Montserrat', -apple-system, BlinkMacSystemFont, 'Segoe UI', Arial, sans-serif;
--header-h: 128px;
```
---
## Document structure
Produce valid HTML5 using these semantic elements:
- `<header class="site-header" role="banner">` — contains logo and both navigation rows
- `<main>` — contains all page content
- `<footer role="contentinfo">` — copyright bar
Place a single `<style>` block in `<head>` containing all CSS. No inline styles except where explicitly noted.
---
## Header and navigation
### Site logo
The header logo must be a CSS text link, not an image. Do not use any `<img>` tag for the logo regardless of what appears in the source. Place the logo as the first element inside `<header>`, inside a `<div class="header-top">`:
```html
<div class="header-top">
<a class="site-logo" href="../index.html" aria-label="Towns of Europe – Home">
Towns of Europe
</a>
</div>
```
Adjust the `../` depth to match the current page's subfolder level. A page at the site root uses `index.html`, one level deep uses `../index.html`, two levels deep uses `../../index.html`, and so on.
```css
.site-logo {
font-size: 16px;
font-weight: 800;
letter-spacing: 1.5px;
text-transform: uppercase;
color: var(--white);
text-decoration: none;
}
.site-logo:hover { color: var(--red); }
```
### Two-row tab navigation
Retain the two-row navigation bar that appears on all pages. Strip all p7MXM widget markup, mega-menu panels, dropdown sub-menus, and their enclosing wrapper divs. Retain only the root-level tab links. Render them as two plain `<nav class="nav-line">` elements immediately after `.header-top`, each containing a single `<ul>` of `<li><a>` items.
Standard row 1: Home, France, Italy, UK, Ireland, Switzerland, Netherlands, Belgium
Standard row 2: Northern, Central, Greece, Germany, Spain, Austria, YouTube, More
Take the `href` values and link text from the source page's root-level navigation items. If the source page uses an older single-row template or is missing row 2, apply the standard two-row configuration above. Adjust all relative `href` values for the current page's subfolder depth using the correct `../` prefix. The YouTube link should carry `target="_blank" rel="noopener"`.
Do not produce any dropdown, hover menu, or JavaScript-driven navigation. The tab bar is plain links only.
### Navigation CSS
```css
.site-header {
background: var(--dark);
position: sticky; top: 0; z-index: 100;
box-shadow: 0 2px 8px rgba(0,0,0,.5);
}
.header-top {
display: flex; align-items: center;
padding: 10px 24px;
border-bottom: 1px solid #2a2a2a;
min-height: 48px;
}
.nav-line { background: #1e1e1e; border-bottom: 1px solid #2e2e2e; }
.nav-line ul { list-style: none; display: flex; flex-wrap: wrap; padding: 0 12px; }
.nav-line ul li a {
display: block; padding: 9px 11px;
font-size: 12px; font-weight: 700; letter-spacing: .35px;
color: #ddd; text-decoration: none;
transition: color .15s;
}
.nav-line ul li a:hover { color: var(--red); }
```
---
## Page layout
### Sidebar pages (most pages)
Most content pages have a main content area and a sidebar. Produce a two-column grid layout:
```css
.page-wrap {
max-width: 1366px; margin: 0 auto;
padding: 32px 24px;
display: grid;
grid-template-columns: 1fr 240px;
gap: 32px;
align-items: start;
}
@media (max-width: 860px) {
.page-wrap { grid-template-columns: 1fr; }
.page-sidebar { order: -1; }
}
```
### Full-width pages (index and other no-sidebar pages)
Pages with no sidebar — identified by the absence of a p7DMM widget — should omit `.page-wrap` and render `<main>` as a single full-width content column with `max-width: 1366px; margin: 0 auto; padding: 32px 24px`.
---
## Sidebar conversion
The original sidebar is produced by a `p7DMM` widget. Extract all links from the p7DMM `<ul>` and render them as:
```html
<aside class="page-sidebar" aria-label="Section navigation">
<nav>
<h4>[Section heading]</h4>
<ul class="sidebar-nav">
<li><a href="[exact original href]">[link text]</a></li>

</ul>
</nav>
</aside>
```
Choose the `<h4>` section heading to accurately reflect the regional or thematic grouping of the links in that sidebar (for example, the region or country section the page belongs to).
If the sidebar contains a gallery link or other link placed above the p7DMM list, preserve it above the `<nav>` as a styled anchor inside a `<div class="sidebar-gallery">`.
Preserve all original `href` values exactly. Do not add, remove, or rename any sidebar links.
### Sidebar CSS
```css
.page-sidebar {
background: var(--white); padding: 20px;
border-radius: 2px;
position: sticky;
top: calc(var(--header-h) + 16px);
}
.sidebar-gallery {
margin-bottom: 14px; padding-bottom: 12px;
border-bottom: 2px solid var(--light);
}
.sidebar-gallery a { font-size: 13px; font-weight: 700; color: var(--red); }
.sidebar-gallery a:hover { text-decoration: underline; }
.page-sidebar h4 {
font-size: 11px; font-weight: 800;
text-transform: uppercase; letter-spacing: .8px;
color: var(--red); margin-bottom: 12px;
}
.sidebar-nav { list-style: none; }
.sidebar-nav li { border-bottom: 1px solid #f0f0f0; }
.sidebar-nav a {
display: block; padding: 7px 0;
font-size: 13px; font-weight: 600; color: var(--mid);
text-decoration: none; transition: color .15s;
}
.sidebar-nav a:hover { color: var(--red); }
```
---
## Content to preserve exactly
- The `<title>` text and `<meta name="description">` content from the original
- All body copy, headings, and lists verbatim — do not rewrite or summarise any text
- All image `src` paths exactly as they appear, including any spaces or irregular characters in the path
- All image `width` and `height` attributes exactly as they appear in the original
- All internal link `href` values exactly as they appear
- All external links, including `target="_blank"` and `rel="noopener"` attributes
---
## Heading hierarchy
Ensure headings follow a sequentially descending order: `h1` → `h2` → `h3` → `h4`. Do not skip levels. If the original uses an `h3` or `h4` as a decorative subtitle immediately below an `h1` (for example a tagline or subheading), convert it to a `<p class="page-subtitle">` styled in `var(--wine)` rather than a heading element, to preserve visual appearance without breaking hierarchy.
```css
.page-subtitle {
font-size: 1.05rem;
font-weight: 600;
color: var(--wine);
margin-bottom: 20px;
}
```
---
## Image handling — CLS and performance
Every image on the page must carry explicit `width` and `height` attributes matching the original values. This reserves layout space before the image loads and prevents CLS.
Apply `loading="lazy"` to every `<img>` tag except the first image in the main content area. The first image should omit the attribute (the browser default is eager), as it is a candidate for the Largest Contentful Paint element and must not be deferred.
---
## Video iframes (YouTube)
Wrap every YouTube `<iframe>` in a positioned div using `aspect-ratio` to maintain a 16:9 ratio at any width. Never use the old `padding-bottom: 56.25%; height: 0` hack.
```html
<div class="video-wrap">
<iframe src="https://www.youtube.com/embed/[ID]?rel=0"
title="[descriptive title]"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
allowfullscreen></iframe>
</div>
```
The first YouTube embed on the page should omit `loading="lazy"`. All subsequent YouTube embeds should carry `loading="lazy"`.
```css
.video-wrap {
position: relative; aspect-ratio: 16 / 9;
margin: 20px 0; background: #000;
border: 2px solid #bbb;
box-shadow: 0 2px 8px rgba(0,0,0,.2);
border-radius: 2px;
}
.video-wrap iframe {
position: absolute; inset: 0;
width: 100%; height: 100%; border: 0;
}
```
---
## Map iframes (Google Maps)
Wrap every Google Maps `<iframe>` in a positioned div using `aspect-ratio: 4 / 3`. Remove any inline `width` and `height` attributes from the iframe itself. Add `loading="lazy"` to all map iframes as they are always below the fold.
```html
<div class="map-wrap">
<iframe src="[original src]" title="[descriptive title]" loading="lazy"></iframe>
</div>
```
```css
.map-wrap {
position: relative; aspect-ratio: 4 / 3;
margin: 20px 0;
border: 2px solid #bbb;
box-shadow: 0 2px 8px rgba(0,0,0,.2);
border-radius: 2px; overflow: hidden;
}
.map-wrap iframe {
position: absolute; inset: 0;
width: 100%; height: 100%; border: 0;
}
```
---
## Image galleries
Pages with a photo gallery grid should present images in a responsive CSS grid: 3 columns on desktop, 2 on tablet, 1 on mobile. All gallery images should carry `loading="lazy"`.
```css
.gallery-grid {
display: grid;
grid-template-columns: repeat(3, 1fr);
gap: 12px; margin: 20px 0;
}
@media (max-width: 860px) { .gallery-grid { grid-template-columns: repeat(2, 1fr); } }
@media (max-width: 480px) { .gallery-grid { grid-template-columns: 1fr; } }
.gallery-grid img { width: 100%; height: auto; display: block; border-radius: 2px; }
```
---
## Tables
Wrap every `<table>` in a `<div class="table-wrap">` to enable horizontal scrolling on narrow viewports:
```html
<div class="table-wrap">
<table>...</table>
</div>
```
```css
.table-wrap { overflow-x: auto; margin: 20px 0; }
```
---
## Video child pages
For every page processed except `index.html` and except any page whose filename
already contains the word "video" or "video-tour"(case-insensitive), check whether the source
page contains an embedded YouTube iframe.
Note: pages whose filenames already contain the word "video" or "video-tour" must still be
converted to clean HTML5 like any other page. The exclusion below applies only
to the creation of NEW companion video pages — it does not exclude existing
video pages from the conversion process itself.
If the page contains an embedded YouTube iframe, create a companion video page
in the same folder as the parent, named `[pagename]-video.html`.
If the page does NOT contain an embedded YouTube iframe, do not create a video
companion page and do not add the "Click here to watch the video" link to the
parent page. Instead, add the page filename to a running list of pages with no
embedded video.
When all files in the current batch are processed, write that list to a file
called `no-video-pages.txt` in the `converted/` folder, appending to it if it
already exists so that lists from multiple sessions accumulate. Each line should
contain the full relative path of the source file, for example:
France/North/Caen.html
France/Southwest/Bordeaux.html
This file will serve as a reference for pages where embedded video should be
added in a future pass.
The video child page uses the same header, two-row nav, and footer as its parent, with all paths identical. It uses a full-width single-column layout with no sidebar. The main content area contains:
```html
<h1>YouTube Video</h1>
<div class="video-wrap">


</div>
<p class="video-link-note">
<a href="[pagename].html">Return to story page.</a>
</p>
```
The `<title>` tag of the child page should read `[original page title] — Video`. The `<meta name="description">` should read `Watch the video for [original page title]`.
At the bottom of the main content area of the parent page, immediately before the closing `</article>` tag, add:
```html
<p class="video-link-note">
<a href="[pagename]-video.html">Click here to watch the video on a separate page.</a>
</p>
```
### Video link note CSS
```css
.video-link-note {
margin-top: 32px;
padding-top: 16px;
border-top: 1px solid #e0e0e0;
font-size: 14px; font-weight: 600;
}
.video-link-note a { color: var(--red); }
.video-link-note a:hover { text-decoration: underline; }
```
---
## Footer
```html
<footer role="contentinfo">
<p class="copyright">© Dennis Callan —
<a href="mailto:info@townsofeurope.com">CONTACT</a> —
<a href="../more/About.html">ABOUT</a> —
<a href="../sitemap.html">Sitemap</a> —
<a href="../index.html">HOME</a>
</p>
</footer>
```
Adjust `../` depth as needed. Preserve the original footer link text and targets exactly.
```css
footer[role="contentinfo"] {
background: var(--dark); color: #999;
text-align: center; padding: 20px 24px;
font-size: 13px; margin-top: 40px;
}
footer[role="contentinfo"] a { color: #ccc; text-decoration: none; }
footer[role="contentinfo"] a:hover { color: var(--red); }
```
---
## Scroll-to-top button
Replace the p7STT widget with this vanilla implementation. Place the button immediately before the closing `</body>` tag, followed by the script block.
```html
<button id="scroll-top" aria-label="Scroll to top">▲ Top</button>
<script>
(function(){
var btn = document.getElementById('scroll-top');
window.addEventListener('scroll', function(){
btn.classList.toggle('visible', window.scrollY > 300);
});
btn.addEventListener('click', function(){
window.scrollTo({ top: 0, behavior: 'smooth' });
});
})();
</script>
```
```css
#scroll-top {
position: fixed; bottom: 24px; right: 24px;
background: var(--red); color: #fff;
border: none; border-radius: 4px;
padding: 9px 14px;
font-family: var(--font); font-size: 12px; font-weight: 700;
cursor: pointer; opacity: 0; pointer-events: none;
transition: opacity .3s; z-index: 999;
}
#scroll-top.visible { opacity: 1; pointer-events: auto; }
```
---
## Mobile responsiveness
```css
@media (max-width: 600px) {
.header-top { padding: 8px 14px; }
.nav-line ul { padding: 0 6px; }
.nav-line ul li a { padding: 8px 7px; font-size: 11px; }
.page-wrap { padding: 20px 14px; }
}
```
---
## Output
For each source page, produce two output files:
1. The converted parent page at the same relative path as the source
2. The companion video child page at `[same folder]/[pagename]-video.html`
Process all files one at a time sequentially. Do not launch parallel agents or
background tasks. Complete each file fully before moving to the next. Return
complete, self-contained HTML for both files. No explanation, no markdown code
fences, no truncation. Both files must be ready to save and upload directly.

MarvinHeston

Inspiring

Hello Pat,
Nevermind. I managed to find an old backup that had the zip file. 🙂

--------------------------------------------------
Marv

Hopefully you were able to download the manuals.

Perhaps you can help me, I lost a HD and with it my AMM Adaptive Menu Magic files. I would be grateful if you can help me with a download.

Marv

Pat_McAuthor

Participating Frequently

Sorry Marvin - Just saw this. Glad your sorted

garykopy

Participating Frequently

Consistent with what may be a sign of the times, I did not know ProjectSeven was gone. They were my preferred, always the best. Still have a bunch of their extensions, but I'm not doing much design in Dreamweaver anymore.

I still teach design using Dreamweaver. Still the best. I'll miss P7. Al Sparber (RIP) and company were visionaries. They brought us all far.

pegprice

Participating Frequently

Does anyone remember the fix for, PVII extensions are installed, yet when I select "Insert", Studio VII is there,, but no extensions appear. I recall this happening years ago after a Dreamweaver update, but can't remember the steps to fix. Thank you!

denniscallan

Inspiring

The extensions still work for me, using the latest update of Dreamweaver.

johnd59898678

Inspiring

Looks like that dreaded day has come! I think I have every PVII Extension ever offered and have about 50 client websites that are all dependent on those extensions and DW. This may end up driving me out of business as nobody is going to pay me to rebuild their sites on another platform! ALL of my PVII sites have been performig flawlessly - some going back 15 years. This is really sad news.

Lana B Cal

Participating Frequently

Hi John,

I started with P7 in 2013. Prior, I was hand coding and using jquery, etc. A web friend told me about P7. P7 coding is stable, clean and the templates can be custom designed. I was in shock to learn P7 shut down without any notice. However after several days and posting in this conversation, I have decided not to rush to change and continue using Dreamweaver and the P7 extensions. My client from 2014 just reconnected for a new page added to his website. My templates go forward for now!! http://www.dreambuildersofthefloridakeys.com/index.html. So, I am not going to be hasty to leave P7.

There is SO much information on coding in the user guides!! I would love to get P7 user guides from you that I need if you have them.. Would this be possible? Thank you!

Lana

johnd59898678

Inspiring

Ii don't have any user guides. I used to rely heavily on the PVII Forum when I would run into issues, but they took the forum offline about a year or so ago. The Forum had LOTS of answers.

denniscallan

Inspiring

Considering all issues here about how obsolete DW has become, I'm considering migrating to WordPress. Any exxperience or thoughts about that?

Lana B Cal

Participating Frequently

Hi Dennis,

I once asked Al Sparber for a text recommendation:

CSS The Definitive Guide by Eric A. Meyer & Estelle Weyl

And to quote Pat_Mc earlier well said post: "Ah well, every day is a school day as they say."

My 2-cents: There's more control in hand coding for design and SEO

Lana

denniscallan

Inspiring

Ironic that Al would say that! But it's true if you can handle it. I'm too busy making travel videos to spend that much time learning minutia of CSS, so I rely on plugins.

Lana B Cal

Participating Frequently

Pat,

I also am looking for P7 User guides and wonder if you have any of these:

• Affinity_Garnet

• BAM Background Animator Magic BAM

• BFA Before & After Comparison BFA

• BSE Background scroll Effects order

• CSS STYLE CLASS SWITCHER

• DDM Drill Down Menu Magic

• FGM Flex Grid Magic FGM

• GBA Gradient Background Animator

• HARMONIUM page pak

• HTML Toolkits - Breadcrumb Builder

• HTML Toolkits - Images

• IFX Image Effects Magic IFX

• ISM INFO SLIDER

• LEM Lag Effect

• OPM omni panel magic

• PCH Panache

• PKB PEEKABOO PKB

• SOM SLIDE OUT MENU

• SOP Slide Out Panel Magic

• TTM Tool TIp Magic

• TYPECRAFTERS page pak

• VBM Video Background Magic

• VIBRATION page pak

Thank you

Lana

Pat_McAuthor

Participating Frequently

Hi Lana

Unfortunately, no, I don't have any of those (I actually only ever bought 8 extensions in total. The only one I am missing is also on your List SOP - Slide out Panels magic.

You invested heavily in PVII so good luck in your quest.

Pat

Lana B Cal

Participating Frequently

Hi Pat,

Thank you for starting this query regarding the P7 extensions. In 2013 a WEB friend told me about Project Seven. She was using their templates and extensions... the code is so clean and reliable. I had bee hand coding and using Jquery, etc. and switched. It has been a great to have the templates, widgets, designer community, and phone support. all from ONE source, P7 and consequently my toolbox has grown over the years.

Thank you Dennis for providing so many of the P7 user manual. https://onedrive.live.com/?authkey=%21ALT7hwFId%5F%5FcGgw&id=2B138E2AC9BBAD5B%21161&cid=2B138E2AC9BBAD5B

I posted a list in an earlier message and what I have that does not duplicate Dennis’s user guides. I would like to upload to Dennis' one-drive but the upload is not accepting? You and others are welcome to what I have.

The shock is wearing off... I never imagined that P7 would vanish as it did!!

Look forward to staying in touch professionally.

Cheers
Lana

denniscallan

Inspiring

All, except Slide Out, are in the cloud collection referenced below.

Pat_McAuthor

Participating Frequently

Thanks again Dennis. (Grabbed all mine from there yesterday). I doubt Slide Out Panel will appear but it's no biggie, not many options and , as usual, well annotated.

I should have captured my own back in the day, nothing is forever. Ah well, every day is a school day as they say.

Thanks Pat

Pat_McAuthor

Participating Frequently

Thank you to Nancy & Ben for replying here. I have now received a really helpful response on my original post (linked above) where a Dennis Callan has posted a link to a host of help files for P7 (Thanks Dennis).

I now have everything I need apart from 'Slide Out Panel Magic help file.

Thanks again

Pat

denniscallanCorrect answer

Inspiring

Pat_McAuthor

Participating Frequently

Sir, you are both a gentleman and a scholar! That's a life saver for me so Thank You very much.

Thankfully you had the foresight to download and capture those HTML help files.

The only help document I am short of now (if anyone out there has it) is 'Slide Out Panel Magic'

Thanks Again.

Pat

Lana B Cal

Participating Frequently

Hi Pat, It is wonderful that we are all pulling together in this unusual moment. I am grateful to hear that you have manyal user guides and PDFS. Cheers, Lana