search

DanielSmith1239 / HQTriviaMaster

A neat little Mac program for answering HQ Trivia questions.
GNU General Public License v3.0
83 stars 22 forks source link

Anyway to downgrade this to 10.12? #34

Closed andrewibrah1m closed 6 years ago

andrewibrah1m commented 6 years ago

Hey there,

I noticed that this only successfully runs on 10.13; on XCode, when I try to run it, it tells me to lower the minimum version.

When I lower the minimum version to 10.12, stuff starts breaking like this:

https://imgur.com/a/mDW0g

Anyway to fix this issue or get a downgraded version? I really don't want to update to High Sierra, since that breaks all gaming on Mac OSX...

I'm currently running 10.12.6.

andrewibrah1m commented 6 years ago

XCode recommended this fix (an "if version available"): https://imgur.com/a/hhBnN but that screwed up the app; it runs now, but when I scan the boundary, no question or answers pop up. Here's a picture of the output after running the app and scanning a boundary:

2018-01-28 23:45:20.156918-0600 HQ Trivia Master[15404:899544] Unknown Window class (null) in Interface Builder file, creating generic Window instead Mouse Pressed Down 2018-01-28 23:45:27.431884-0600 HQ Trivia Master[15404:899544] [Layout] Unable to simultaneously satisfy constraints: ( "<NSAutoresizingMaskLayoutConstraint:0x600000096f30 h=--& v=--& NSBox:0x101122280.width == 0.289062 (active)>", "<NSAutoresizingMaskLayoutConstraint:0x600000097110 h=-&- v=-&- H:[NSView:0x600000120500]-(-5)-| (active, names: '|':NSBox:0x101122280 )>", "<NSAutoresizingMaskLayoutConstraint:0x600000097160 h=-&- v=-&- NSView:0x600000120500.minX == 5.32422 (active, names: '|':NSBox:0x101122280 )>" )

Will attempt to recover by breaking constraint <NSAutoresizingMaskLayoutConstraint:0x600000097110 h=-&- v=-&- H:[NSView:0x600000120500]-(-5)-| (active, names: '|':NSBox:0x101122280 )>

Set the NSUserDefault NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints to YES to have -[NSWindow visualizeConstraints:] automatically called when this happens. And/or, set a symbolic breakpoint on LAYOUT_CONSTRAINTS_NOT_SATISFIABLE to catch this in the debugger.

schlossm commented 6 years ago

Hi, check out PR #35 and let me know if that works.

You can safely ignore the layout warnings, it's a built in component issue