I had been using breakpoint 2.5 for quite sometime. I got a new Mac and setup breakpoint on it. I installed 2.7.0 Clearly there has been some changes between 2.5.0 and 2.7.0 of breakpoint.
Here is the contents of my breakpoint.scss file (ignore the px values, they are just random ones I typed in)
$breakpoint-to-ems: true;
$breakpoint-no-query-fallbacks: true;
$breakpoint-default-media: screen;
$xsmall: 320px;
$small: 480px;
$medium: 760px, 'no-query' '.lt-ie9';
$large: 960px, 'no-query' '.lt-ie9';
$xl: 1200px;
$mega: 1700px;
I would then call a mixin such as the following if I wanted to target the $medium breakpoint:
#include breakpoint($medium) {
font-size: 60px;
}
Using that with breakpoint 2.5.0 was fine. Using it with 2.7.0 is causing several warnings.
WARNING: In order to avoid variable namspace collisions, we have updated the way to change settings for Breakpoint. Please change all instances of $breakpoint-default-media: {{setting}} to #include breakpoint-set('default media', {{setting}}). Variable settings, as well as this warning will be deprecated in a future release.
WARNING: In order to avoid variable namspace collisions, we have updated the way to change settings for Breakpoint. Please change all instances of $breakpoint-to-ems: {{setting}} to #include breakpoint-set('to ems', {{setting}}). Variable settings, as well as this warning will be deprecated in a future release.
WARNING: In order to avoid variable namspace collisions, we have updated the way to change settings for Breakpoint. Please change all instances of $breakpoint-no-queries: {{setting}} to #include breakpoint-set('no queries', {{setting}}). Variable settings, as well as this warning will be deprecated in a future release.
WARNING: In order to avoid variable namspace collisions, we have updated the way to change settings for Breakpoint. Please change all instances of $breakpoint-no-query-fallbacks: {{setting}} to #include breakpoint-set('no query fallbacks', {{setting}}). Variable settings, as well as this warning will be deprecated in a future release.
I was able to clear up those 3 fairly easily with a search of good old Google.
I changed
$breakpoint-to-ems: true;
to be
#include breakpoint-set('to ems', true);
I changed
$breakpoint-no-query-fallbacks: true;
to be
#include breakpoint-set('no query fallbacks', true);
I changed
$breakpoint-default-media: screen;
to be
#include breakpoint-set('default media', screen);
The issue I am having now is that every instance of the breakpoint mixin being used in my bluehive.scss file using the $medium or $large breakpoint, such as
#include breakpoint($medium) {
font-size: 60px;
}
is throwing a warning:
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-queries: {{setting}} to #include
breakpoint-set('no queries', {{setting}}). Variable settings, as well
as this warning will be deprecated in a future release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 62 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-query-fallbacks: {{setting}} to
#include breakpoint-set('no query fallbacks', {{setting}}). Variable
settings, as well as this warning will be deprecated in a future
release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 62 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-queries: {{setting}} to #include
breakpoint-set('no queries', {{setting}}). Variable settings, as well
as this warning will be deprecated in a future release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 87 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-query-fallbacks: {{setting}} to
#include breakpoint-set('no query fallbacks', {{setting}}). Variable
settings, as well as this warning will be deprecated in a future
release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 87 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-queries: {{setting}} to #include
breakpoint-set('no queries', {{setting}}). Variable settings, as well
as this warning will be deprecated in a future release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 90 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-query-fallbacks: {{setting}} to
#include breakpoint-set('no query fallbacks', {{setting}}). Variable
settings, as well as this warning will be deprecated in a future
release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 90 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-queries: {{setting}} to #include
breakpoint-set('no queries', {{setting}}). Variable settings, as well
as this warning will be deprecated in a future release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 99 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
WARNING: In order to avoid variable namspace collisions, we have
updated the way to change settings for Breakpoint. Please change all
instances of $breakpoint-no-query-fallbacks: {{setting}} to
#include breakpoint-set('no query fallbacks', {{setting}}). Variable
settings, as well as this warning will be deprecated in a future
release.
on line 16 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_legacy-settings.scss,
in legacy-settings-warning'
from line 41 of /Users/chadwarren/.rvm/gems/ruby-2.3.0/gems/breakpoint-2.7.0/stylesheets/_breakpoint.scss,
inbreakpoint'
from line 99 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/_bluehive.scss
from line 14 of /Users/chadwarren/Dropbox/Bluehive Interactive/Website
2016/Theme/bluehiveinteractive-2016/assets/scss/styles.scss
Is there a new way of declaring and using the breakpoints in version 2.7.0 ? I've been unable to find anything which says that this has changed.
Thank you :-)
Try including #import "breakpoint"; in your styles.scss, after use
#include breakpoint-set('no queries', true);
#include breakpoint-set('no query fallbacks', true);
Related
I was wondering how I would fix this error in the Logos.pl file, this is what I'm getting:
WillPhone:/var/mobile/sbtest1 root# make package install
/var/mobile/sbtest1/theos/makefiles/targets/Darwin-arm/iphone.mk:43: Targeting iOS 4.0 and higher is not supported with iphone-gcc. Forcing clang.
Making all for tweak sbtest1...
Preprocessing Tweak.xm...
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Constants from lexical variables potentially modified elsewhere are deprecated at /private/var/theos/bin/lib/aliased.pm line 42.
Can't call method "isNew" on an undefined value at /var/mobile/sbtest1/theos/bin/logos.pl line 382.
make[2]: *** [obj/Tweak.xm.a114fd55.o] Error 255
make[1]: *** [internal-library-all_] Error 2
make: *** [sbtest1.all.tweak.variables] Error 2'˚`
Thanks! - Will B
You can go to Theos Github to submit this issue.
Here are some other projects with this issue.I hope it will help you.
https://github.com/preaction/Statocles/issues/190
https://github.com/Crowdtilt/Business-BalancedPayments/issues/53
Suddenly I'm getting an error in _types.h on the line with typedef. How can I track this down?
#ifdef __GNUC__
typedef __signed char __int8_t;
#else /* !__GNUC__ */
This is pretty much always caused by a syntax error just prior to whatever included the file with the actual error.
So, have a look in the file that (indirectly) included _types.h. You likely have an unbalanced (.
Usually these cryptic errors in system header files result from your having other code (perhaps in another header file which was #import'ed earlier) that is missing a closing parenthesis. Often whenever you get strange compile errors, you have to look at the lines of code that the compiler encountered before the reported line and see if that earlier code was properly terminated.
I have add following line to the code.
#ifdef DEBUG
//DEBUG only code
#endif
And I have go to the project->info tab in the xcode and set 'command-line builds use' to debug and run the code the code snippet inside the 'if' executed. The problem is when i set the command-line build' use to release and run the code. The code snippet inside the if condition still runs. I have set the preprocessor DEBUG macros to 'DEBUG=1'without quotes. How to solve this.
The #ifdef syntax means "is defined", without regard to value; in other words, it is defined if it has any value at all (0 or 1).
You probably want the #if syntax instead. This requires that the value actually be set to 1.
I keep a future-break objc_exception_throw in my .gdbinit (because I generally debug in AppCode, which doesn't yet have a GUI means of configuring breaks on objective-c exceptions).
Is there an equivalent for LLDB?
If you create a ".lldbinit" file in the directory from which you are debugging and then specify the file on the command line:
% cat ./.lldbinit
breakpoint set --name objc_exception_throw
% lldb /bin/ls
(lldb) breakpoint list --full
Current breakpoints:
1: name = 'objc_exception_throw', locations = 0 (pending)
This should help you to work around the issue for now.
The ".lldbinit" file ordering is:
check for app specific ~/.lldbinit-lldb file (where "lldb" is the name of the application that is running the LLDB.framework, you can add a ~/.lldbinit-Xcode for Xcode only command) if available
if no app specific file from step 1, then source "~/.lldbinit" if it exists
load the file and process the options from the "lldb" command line command
parse the local "./.lldbinit" file from the current working directory.
You can't currently do that with lldb. Until lldb has set up a Target (which will happen when you specify a binary), you can't add a breakpoint. This is something that will need to be added in the future.
I'm trying to learn YAML with C++, i made the given yaml-cpp files into a .dll and .lib file with VC++ Express 2010 by using CMake. I have set up my project the same way i set up other libraries like SFML.
My issue is, when i try to build a Release version of the example code given on the yaml-cpp site i get:
Ogre
Dragon
Wizzard
However, when i try to build a Debug version, i get:
Assertion failed: false, file d:\microsoft visual studio 10.0\vc\include\yaml-cp
p\nodeimpl.h, line 39
I don't know how to handle this. Do i need to build a debug version of the library? If yes, how? I don't know which project options could affect this if i managed to change something.
When i'm compiling, i get a warning:
d:\microsoft visual studio 10.0\vc\include\yaml-cpp\conversion.h(51): warning C4146: unary minus operator applied to unsigned type, result still unsigned
With alot of template printouts, f.e. :
1> d:\microsoft visual studio 10.0\vc\include\yaml-cpp\nodereadimpl.h(35) : see reference to function template instantiation 'bool YAML::ConvertScalar<T>(const YAML::Node &,T &)' being compiled
1> with
1> [
1> T=unsigned int
1> ]
Is this a problem on my side? Bad CMake file and compilation?
> yaml_test.exe!main() Line 108 C++
yaml_test.exe!__tmainCRTStartup() Line 555 + 0x19 bytes C
yaml_test.exe!mainCRTStartup() Line 371 C
kernel32.dll!7c817077()
[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
Aborts at:
doc[i] >> monster;
The program doesn't try to enter the overloaded function.
In my own code it breaks when i try to use my first >> operator, which is the build in one for int.
I'm using the code from http://pastebin.com/PdKWDgQa, though for the original yaml-cpp example code it does the same. The output in Release mode is right, Debug stops and returns the same assert code.
For reference, the stack call in Release mode at the { bracket in the >> function for monster looks like this:
> yaml_test.exe!operator>>(const YAML::Node & node={...}, Monster & monster={...}) Line 36 C++
yaml_test.exe!main() Line 109 C++
msvcr100.dll!_initterm(void (void)* * pfbegin=0x00000001, void (void)* * pfend=0x003a5050) Line 873 C
yaml_test.exe!__tmainCRTStartup() Line 555 + 0x17 bytes C
kernel32.dll!7c817077()
[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
EDIT:
Actually, i have rebuilt the yaml-cpp project i made with CMake as Debug, everything runs fine when i use it now. I'm sorry if this is obvious, i'm new to these kind of issues.