1) Not being a program meant to be specific to a particular OS,
I'm not overly concerned about this. A "critical" or "blocker" bug
is classified as - Did it break the program or did we lose major
core functionality? I wouldn't release an RC3 for a mere glitch
for Windows not being able to figure out the program is an RC2 vs.
RC1. I am going to do an RC3 for several fixes/features that were
discovered missing that I feel should make the 6.08.00 release,
but not because Windows has issues. If you felt this is important
enough to warrant concern why haven't you opened a bug for it?
2) I don't control HOMEBREW sources,
anything I cannot control is irrelevant to our release schedule.
We have a support team on Discord and here to assist you update
your out-of-date set. FEAT is an illegal tag, and should have been
converted to ABILITY back in 6.06.00 if not sooner. The team
focuses on things we control and manage. If you want support for
your homebrew, ask for the help, and we will gladly tell you what
you need to update/change/convert to be compliant with the current
3) As #1 states, we are an OS Neutral Program. Coding in OS
specific settings requires folks who have the knowledge. I have *NEVER*
had an issue creating PDFs nor printing them, and I have been
using PCGen for 17 years. Merely set your paper settings in the
preferences and you'll be fine.
To tag onto Stefan's comment, if you won't do the code, at least
point out a source that our team can reference to tackle the
issue. I've always held to a principle of point out the problem
and a potential solution if possible. I wasn't aware that
cross-training in multiple languages was considered a detriment.
And for actual bugs, we have a BUG tracker system located here
--> https://pcgenorg.atlassian.net where all the issues can be
discussed or solutions presented.
On 12/14/2018 10:30 AM, markjmeans
Windows uninstall entry in Windows > Settings > Apps
& Features lists PCGen as ï¿½6.08.00RC1ï¿½ as the product
name and shows nothing for program title or version number.
What is expected is that the program name, version number
and publisher name fields be defined correctly in the
installer so that the uninstall process follows Windows
guidelines and is intuitive to Windows users. In my
opinion this is a critical bug that should delay release
until resolved. However, it should be a very
simple one to fix. Itï¿½s a 30 second task using Microsoft
installer projects within MS Visual Studio and I will assume
itï¿½s nearly as simple using the nullsoft installer that
PCGen uses (but I have no experience with nullsoft installer
projects). Whomever wrote the installer project should
examine the project properties and correct them. This fix
alone should require an RC3 version before going ahead to
homebrew set that loads in RC1 will not load in RC2. See
attached homebrew files. The error log does not indicate
specifically what is wrong, i.e. doesnï¿½t say which campaign
is unable to load.
main Main:138 Starting PCGen v6.08.00 RC2
main LanguageBundle:134 Initialising language bundle with
LSTWARN main CampaignFeatToken:56 FEAT has been deprecated,
use ABILITY: and put CATEGORY: entries in the LST file
SEVERE Thread-2 SourceFileLoader:248 Failed to load sources
You must select at least one campaign to load.
at java.base/java.lang.Thread.run(Unknown Source)
And while not a problem with RC2
specifically, there is a long standing problem with PCGen and
the paper format. PCGen should detect the OS culture settings
and if it is US/English, should set the paper size to Letter
instead of A4. I donï¿½t know how many sheets of paper Iï¿½ve
wasted because of this.