• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
BaneTrapper

Visual studio 2010 ignore warrning

9 posts in this topic

Hello.
I am just being annoyed by a warning and i cant find how to remove them =,= srsly....

Warning :: "warning C4244: 'argument' : conversion from 'int' to 'float', possible loss of data"
Am doing something like this
void setTextPosition(float a, float b); int main(){    setTextPosition(static_cast<int>(posX), static_cast<int>(posY)); //Note posX and posY are floats and i really need to pass int values the setTextPosition is a sfml2.0 function and i don't want to mess with sfml code}
[font=comic sans ms']The question:[/font]
How do i remove warning in "Visual studio 2010" for specified line/lines Edited by BaneTrapper
0

Share this post


Link to post
Share on other sites
You can use #pragma warning to disable specific warnings. If you want to disable it for just one line you can use #pragma warning(suppress : 4244).
2

Share this post


Link to post
Share on other sites

You can also use a proper static_cast:

int a = 100;
float b = static_cast<float>(a); // int to float

Or:

float b = 100.0f;
int a = static_cast<int>(b); // float to int
Edited by Cornstalks
1

Share this post


Link to post
Share on other sites
You can also use a proper static_cast:
int a = 100;float b = static_cast<float>(a); // int to float
Or:
float b = 100.0f;int a = static_cast<int>(b); // float to int
I am quite unsure, how or what i did different then you, or what you meant by proper usage of static cast.

And if you are referring to "Khatharr" post, then you should quote it, also i don't see anything "Inappropriate" about him mentioning / using c style cast to int.

I used it like this
float posX;float posY;int main(){    setTextPosition(static_cast <int> (posX) ,static_cast <int> (posY) ) ;    return 0;}
EDIT::
I noticed what did you mean...
The code was tipped in the post, and i made a mistake i shall fix that.
Also the whole post messes up the code section when its edited sorry. Edited by BaneTrapper
0

Share this post


Link to post
Share on other sites

I really don't understand why you're casting floats to ints for a function that takes floats. If you want to change them to whole numbers you should just cast them seperately to remove the ambiguity or use some kind of round function instead of shearing the last bits off by casting. Rounding would actually be better if you're trying to move them closer to a logical position.

 

Often warnings are there for a reason and I'm not sure why people are so apt to disable them when the extra code to disable them could just as easily -fix- the warning.

Edited by Satharis
1

Share this post


Link to post
Share on other sites
I really don't understand why you're casting floats to ints for a function that takes floats. If you want to change them to whole numbers you should just cast them seperately to remove the ambiguity or use some kind of round function instead of shearing the last bits off by casting. Rounding would actually be better if you're trying to move them closer to a logical position.

 

Often warnings are there for a reason and I'm not sure why people are so apt to disable them when the extra code to disable them could just as easily -fix- the warning.

Reason behind this is:
In the function, if posX and posY are not round numbers the text may appear blurry. Therefore i cast them to int before passing into function to remove occasion of blurry text.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0