This one’s a bit subtle, and only bit me because I was writing documentation. However, it’d bite anyone else flipping back and forth between output styles.
Take any series, any number of races, any number of competitors, with results, and scored. The file I’m using is attached.
Publish results.
Choose the tickbox to have page breaks.
Next.
Default is the selected style. Browser is the destination.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default plus.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default.
Preview
Chrome opens a tab.
Print. Preview opens, page breaks are missing, all tables are on one page.
Default vs default plus is not the issue - I can reproduce this with other styles as I flip back and forth. Going back to the publish setup, and then forward again, will reset the option on the style that lost it, and preview/publish works correctly.
The core issue seems to be that after the first table, div class=“applicant-break” is not written in the case where page breaks are lost. The style control is written before the first table (and doesn’t have type=“text/css”) correctly in cases where page breaks work, and in cases where they don’t.
Logbook says this is 2.19.8 (out of curiosity, why no semi-standard Help > About Sailwave?).
Hi Duncan - Thanks for the report.
After investigation what is happening is when you click the next to go to the last tab the main html code is generated. When you click preview or publish it adds the styles and effects and it also removes the last page break to prevent a blank page being created. I hope I’ve fixed this now in 2.22.0 available at https://dl.dropboxusercontent.com/u/220425/sailwave.exe Please note this version also has some as yet undocumented features but it you would like to test the pagination that would be good.
This one’s a bit subtle, and only bit me because I was writing documentation. However, it’d bite anyone else flipping back and forth between output styles.
Take any series, any number of races, any number of competitors, with results, and scored. The file I’m using is attached.
Publish results.
Choose the tickbox to have page breaks.
Next.
Default is the selected style. Browser is the destination.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default plus.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default.
Preview
Chrome opens a tab.
Print. Preview opens, page breaks are missing, all tables are on one page.
Default vs default plus is not the issue - I can reproduce this with other styles as I flip back and forth. Going back to the publish setup, and then forward again, will reset the option on the style that lost it, and preview/publish works correctly.
The core issue seems to be that after the first table, div class=“applicant-break” is not written in the case where page breaks are lost. The style control is written before the first table (and doesn’t have type=“text/css”) correctly in cases where page breaks work, and in cases where they don’t.
Logbook says this is 2.19.8 (out of curiosity, why no semi-standard Help > About Sailwave?).
Hah, so I only hit the condition because that test file only had 3 fleets in it. Good to know.
That build doesn’t have a working Publish menu. Can hover over Publish, can click it, no dropdown. Ctrl + P doesn’t trigger it either.
···
On 2016-06-16 00:45, Jon Eskdale jon@sailwave.com [sailwave] wrote:
Hi Duncan - Thanks for the report.
After investigation what is happening is when you click the next to go to the last tab the main html code is generated. When you click preview or publish it adds the styles and effects and it also removes the last page break to prevent a blank page being created. I hope I’ve fixed this now in 2.22.0 available at https://dl.dropboxusercontent.com/u/220425/sailwave.exe Please note this version also has some as yet undocumented features but it you would like to test the pagination that would be good.
This one’s a bit subtle, and only bit me because I was writing documentation. However, it’d bite anyone else flipping back and forth between output styles.
Take any series, any number of races, any number of competitors, with results, and scored. The file I’m using is attached.
Publish results.
Choose the tickbox to have page breaks.
Next.
Default is the selected style. Browser is the destination.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default plus.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default.
Preview
Chrome opens a tab.
Print. Preview opens, page breaks are missing, all tables are on one page.
Default vs default plus is not the issue - I can reproduce this with other styles as I flip back and forth. Going back to the publish setup, and then forward again, will reset the option on the style that lost it, and preview/publish works correctly.
The core issue seems to be that after the first table, div class=“applicant-break” is not written in the case where page breaks are lost. The style control is written before the first table (and doesn’t have type=“text/css”) correctly in cases where page breaks work, and in cases where they don’t.
Logbook says this is 2.19.8 (out of curiosity, why no semi-standard Help > About Sailwave?).
This one's a bit subtle, and only bit me because I was
writing documentation. However, it’d bite anyone else
flipping back and forth between output styles.
Take any series, any number of races, any number of
competitors, with results, and scored. The file I’m using
is attached.
Publish results.
Choose the tickbox to have page breaks.
Next.
Default is the selected style. Browser is the
destination.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because
each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default plus.
Preview.
Chrome opens a tab.
Print. Preview opens, page breaks are working, because
each fleet table is on its own page.
Switch back to Sailwave.
Change the style to Default.
Preview
Chrome opens a tab.
Print. Preview opens, page breaks are missing, all
tables are on one page.
Default vs default plus is not the issue - I can
reproduce this with other styles as I flip back and forth.
Going back to the publish setup, and then forward again,
will reset the option on the style that lost it, and
preview/publish works correctly.
The core issue seems to be that after the first table,
div class=“applicant-break” is not written in the case
where page breaks are lost. The style control is written
before the first table (and doesn’t have type=“text/css”)
correctly in cases where page breaks work, and in cases
where they don’t.
Logbook says this is 2.19.8 (out of curiosity, why no
In most programs for Windows, there’s a 'About ’ item that’s found in the Help menu. It tends to contain the version of the program, perhaps a release date etc.
As for that guide, I am aware of it, but I’m documenting our local use (the same as how that one has a lot of local references).
I would posit that a lot of what’s in that guide should be available on the Sailwave site, in terms of how to use the software. If you search Google for “Sailwave alias” (to go back to my previous mail to the list), the only mention on the Sailwave site is that the feature exists, and that it’s a field name.
Unless you have actively hidden the property bar the about is displayed by default
Where you will see the program version and also the version of the program that was used to create the current file.
The version of the .exe is also stored in the .exe and if you hover over the Sailwave.exe then the OS will display its version. On older systems you may need to right click and select properties.
If you go to the Sailwave site and the third party resources there is also two guides from Datchet
The Sunday one is for multiple fleets while the Wednesday one is for a single start handicap.
Sailwave is an extremely flexible program and many things can be done in different ways. To write a very general use guide is very difficult because of the so many differing end user requirements. There are several youtube video’s you can watch but the general consensus is that is not quite how we do it. Once you have played with one or two of the examples most people can use the basic features either intuitively or using the tool tips and the reference guide on the Sailwave web site.
I don’t disagree that perhaps we should add a section in the Reference section on Aliases
Although there is some documentation on the Sailwave site - If you put Aliases in the search of the Sailwave home page it will display which sections you need to read. Many of the new features are documented with the version in which it was released e.g. http://www.sailwave.com/version-2-7-2
Based on Version 2.7.0 with the following changes
New Feature of Score Teams by Rank and Points
New Feature of Edit – Create Aliases
Adds a new feature of Scoring Teams by Rank in addition to by Points. Hopefully this is self explanatory when you select it from the Publish Menu.
You can now very quickly set up Aliases from the Edit Menu and New Competitor Alias (And even quicker via Ctl+Alt+n). Note before you can use Aliases you have to enable them in the Setup UI. If they are not enabled there the option is not visible on the Edit Menu. First sort your columns by the appropriate selection. e.g. sort by fleet if you want to apply aliases to a particular fleet. Then select the first one of the fleet you want to use. Then Edit – New Competitor Alias. You see a large list box with the competitors in it all in the same order as you sorted them. Select the ones you want to create Aliases for using which ever method you find easiest. You can block select using the Mouse and Shift key or you can select them using the arrow keys and the space bar. The choice is yours. When you select OK Aliases will be created for them all.
There is also this video which I produced to demonstrate setting up Aliases for use with dual scoring.
Not sure what you mean by your last comment. But in case you mean some sort of guide then can I gently point you in the direction of Mark Townsend’s Sailwave User Guide is available from http://www.abyc.org/upload/Sailwave_ABYC_User_Guide.pdf.
This link is in the footer of of all messages posted to the SUG. Mark’s guide could probably do with a bit of updating as new functionality has been added to Sailwave since it was written.
In most programs for Windows, there’s a 'About ’ item that’s found in the Help menu. It tends to contain the version of the program, perhaps a release date etc.
As for that guide, I am aware of it, but I’m documenting our local use (the same as how that one has a lot of local references).
I would posit that a lot of what’s in that guide should be available on the Sailwave site, in terms of how to use the software. If you search Google for “Sailwave alias” (to go back to my previous mail to the list), the only mention on the Sailwave site is that the feature exists, and that it’s a field name.
