-
[quote user="Sean McIntyre"]I awoke to the same problem. By a process of elimination, I have narrowed it down to the 'verse of the day'. When this option is unchecked, everything appears to be working fine.[/quote] I can recreate the problem in development. It appears that there is a problem with Verse of the Day on Mac. Unchecking the option will work
-
Mark, Thanks for the input. The changes you propose are not vastly different from what we do now, in that we always prefer an empty space (#1) and we try to factor type most heavily into the weighting for resources, giving Bibles a special treatment in keeping them distinct. As of 5.2 Beta 3 we do give docked windows a slight preference in scoring over
-
[quote user="Dave Hooton"] It would be a lot easier to go back to the pre-v5.2 algorithm. [/quote] That's basically what I did to fix it for program settings and for the bible/dictionary issue that Integ mentioned. The fixes will go out with the next 5.2 release.
-
[quote user="Dave Hooton"] [quote user="Tom Philpot (Logos)"]Dave, I trust you'll let me know if this change is better or worse than before.[/quote] It is not improved as Program Settings opened first in the left panel and then in the right panel, then L and then R [/quote] Thanks Dave. I was able to reproduce this behavior and I'll take a look at how
-
[quote user="Integ"]However, with the resource panels, I am having problems. Previously, Logos, at the very least, understood the difference between a Bible and a commentary. It could even tell where a dictionary was and add a new dictionary tab to the correct panel. That no longer happens. Logos adds any new resource to seemingly random panels. E.g
-
[quote user="Tom Philpot (Logos)"]The [5.2 Beta 1 & 2] algorithm makes a simplistic assumption that may break down: it assumes each panel has a "center" tab that is most representative of the contents of that panel. So if you have in one panel, two notes documents and three resources, the center is most likely to be a resource panel, based on a simple
-
[quote user="Tom Philpot (Logos)"]I just discovered a logic bug in the panel code that might arbitrarily prefer any panel with the least number of tabs in it. That probably explains a lot of the craziness you're seeing.[/quote] I take that back. My debugging software lied to me. There was no error like I described, but there are some changes I'm going
-
Dave, I just discovered a logic bug in the panel code that might arbitrarily prefer any panel with the least number of tabs in it. That probably explains a lot of the craziness you're seeing. As far as Tools go, if the Tool has a default position, it will prefer that position and will not cluster. That should be the default behavior for any panel and
-
[quote user="Graham Criddle"] [quote user="Dave Hooton"]The new 'scheme' is crazy [/quote] I do tend to agree. [/quote] Graham, Dave, Thanks for the feedback and screenshots. I'll take a look at these and make some changes.
-
Jonathan, Can you post a screenshot of your layout including floating windows, and how you're opening a new BWS? The new layout code is very dependent on what panels and windows are open, so the more information we have, the easier it will be to track down and fix. Tom
-
[quote user="Dave Hooton"] Program Settings ALWAYS opens in the first tile/panel!! It cannot open anywhere else.. Can we please go back to the predictable system of 5.1 and its predecessors. BTW It perplexingly opens in the correct tile with "Open in a new tab". [/quote] Dave, How are you opening Program Settings and what does your current layout look
-
Dave, I see what you mean about the context menu problem. I'm working on a fix in an upcoming beta release. (Beta 2 is too close to release to make the fixes in).
-
[quote user="Dave Hooton"]It doesn't appear to work any differently to the current 'intelligent' system in a populated layout:[/quote] The current algorithm makes a simplistic assumption that may break down: it assumes each panel has a "center" tab that is most representative of the contents of that panel. So if you have in one panel, two notes documents
-
Mark, [quote user="Mark Barnes"]But if you open five resources, one after the other, you'll end up with one on the right, and four on the left. I know it's impossible to predict what someone really does want, but I doubt it's that.[/quote] I can explain "why" it does what it does currently, but I agree that it's not ideal. The way the logic is implemented
-
I posted a response here: http://community.logos.com/forums/p/75415/528084.aspx#528084
-
Todd, This was a change made recently in the software for bibliographic citations. The idea was to make the citations more correct with regards to bibliographic citations which never include verse references for Bibles (although in-text parenthetical references do, of course). An unintended side affect was the fact that Copy Bible Verses uses this same
-
Robert, I can't seem to reproduce this issue. Which bibliographic style are you using? Would you mind posting some logs ( http://wiki.logos.com/Diagnostic_Logging ) of the crash here so that we can better diagnose the issue? Thanks, Tom
-
[quote user="fgh"] I don't know if this helps, but I can't remember this ever happening to me. Perhaps because I'm on 10.6? (EDIT: Because it's not a beta issue, is it? I think I've seen you complain about it on stable as well?) Jack, you're on 10.7, aren't you? Has it happened to you? [/quote] My current thought is that it's a bug in the Mono runtime
-
[quote user="alabama24"] (By the way, can you address the download and indexing without a restart?)[/quote] Here's a summary of what I'm able to reconstruct from the logs: You started Logos 5 5/01 at about 11 PM. Your licenses were updated twice between when the app started and when the app shutdown. The first time the licenses were updated, the indexer
-
I have a theory about why this could happen, but it would depend on Beta 5 having an error in the background that would prevent the app from closing down cleanly. The problem then is not with the installer, but with the app itself. Had the installer not upgraded the app, you probably would have noticed you would have had to force quit the app, if my