1: " tools -> Program settings" the window has the error message "No view exists for this panel kind."
How does one access program settings in LOGOS 4 MAC A7?
The system is iMAC 27" i7 w/Snow Leopard.
The menu items are there for all the items, but many screens are blank. These serve as placeholders until the design team fills in everything.
Blessings and welcome to the Alpha testing phase.
Thanks for the reply.
Is there somewhere that the programmers have told us what they would like to see exercised during testing? Most of my work requires interlinears, which do not seem to work yet. So my personal work won't take place in MAC side yet. It would be nice to have some idea of what the developers need to see used and perhaps which resources to concentrate on. Otherwise all I am likely to do is reading books.
I usually read the release notes and test each items they say is new, or fixed. If I get an error, I report it as a bug. The info on how to report is linked in my signature.
Yes, but part of what I am wondering is bout the crashes. I've had three plus a hang so far but they are not reproducible. Do we try reporting them, or report only on a particular subsystem, or what? the release notes don't tell us what else might have changed. Do they have a regression test list so we (with many different systems and add-ons) can checl that stuff recently uworked on still work.
It might be useful to have a list of procedures that they want to see everyone perform.
Once we can do real work with the MAC system there will be a lot more exercising that we can do. I will keep bashing on it but the testing won't be very efficient at finding bugs.
I tend to report any crash when it is my first time experience. Even if others have reported it, I assume my logs might be different and therefore of some value.
Yes, but part of what I am wondering is bout the crashes. I've had three plus a hang so far but they are not reproducible. Do we try reporting them, or report only on a particular subsystem, or what?
Please feel free to report any/all crashes, and attach the associated logs (before restarting the app, BTW) at least once. Also, a note as to whether or not it's reproducible or not is helpful. Detailed instructions for how to report crashes and get your logs and upload them are linked in my signature.
If we fix a crasher, we typically mention it in the release notes.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
