Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


visual studio 2013 collapse expand problem


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 lomateron   Members   -  Reputation: 363

Like
0Likes
Like

Posted 31 August 2014 - 09:53 AM

I use a lot the collapse and expand feature, with "#pragma region" code too and visual studio has this problem,

sometimes when I write a word or just press the space key, some random collapsed regions will expand.

This can happen too when I am going through the history by pressing <ctrl+z> or <ctrl+y>  so it will accidentally delete the "redo" history.

This happens in the "update 1","update 2","update 3"

 

anyone here with this problem too?



Sponsor:

#2 lomateron   Members   -  Reputation: 363

Like
0Likes
Like

Posted 31 August 2014 - 06:44 PM

wut?

no one here is a heavy "#pragma region" user?

In c++ I use it a lot because I don't use classes, I have all the code of my game only on one file, 15k lines of code on a .cpp file and 10k lines in a .fx 

does someone here does this too?



#3 Jan2go   Members   -  Reputation: 895

Like
0Likes
Like

Posted 01 September 2014 - 12:40 AM

I have all the code of my game only on one file, 15k lines of code on a .cpp file and 10k lines in a .fx


Any special reason why you are doing this? blink.png It's probably one of the worst way to structure a project... And perhaps even VS doesn't like files of that size if it screws up the outlining. Try smaller files and see if it still happens.

#4 hahajoker181   Members   -  Reputation: 124

Like
0Likes
Like

Posted 01 September 2014 - 02:59 PM

 

I have all the code of my game only on one file, 15k lines of code on a .cpp file and 10k lines in a .fx


Any special reason why you are doing this? blink.png It's probably one of the worst way to structure a project... And perhaps even VS doesn't like files of that size if it screws up the outlining. Try smaller files and see if it still happens.

 

Agreed. You shouldn't keep 15k lines in one file, it is the best to keep them in separate file. This may increase the performance and also there are other reasons to go along. If you lose the file, than it will be frustrating to rewrite the entire program again. 






Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS