The first thing to do is go and read the MSDN documentation for the control you are interested in; that would lead you to this page[^]. Scroll down until you reach the table entry for SS_EDITCONTROL, and you have a potential solution.
If you call Create() directly there's usually options for clipping and/or going to the next line. Usually if you have too long of a line it gets clipped automatically but it should still display something.
Also, make sure you actually have set the hight of the static control correctly, as there is no automatic expansion of its borders, or flow layout using HTML speak, if the text does not fit vertically.
Hello group. i have a very large c program with several hundreds of
structures. is there is a tool which could detect bad structure
Thanks & Regards Prasun
I think No.
Which editor are you using to code your C program? I'm using Visual Studio 2008 IDE. In that I've to select the block I want to format(by pressing SHIFT+ARROWKEY or using mouse),and then press CTRL+F to format.
I don't know, but Lint[^] comes to mind when dealing with static code analyses. Don't know if it can handle inefficient member alignment though. There is also a code analyzer in VS2010 if you have Ultimate edition.
You might end up in trouble trying to optimize for space like this, if the order of the members is used in any way in the program. Some C (and C++) programmers tend to take shortcuts once in awhile.
Just a word of warning.
Your memory will obvouisly grow when working with data since all this memory is most likely read into the memory, so nothing strange there in my opinion. However you are loading 50.000! items in a list and that is a bad practise for several reasons:
1) Performance, it slows down the application because it has to load 50000 items at once
2) Usability, A user will not be happy scrolling through 50.000 items. Give them filtering and paging
3) Memory, 50.000 items can consume a lot of memory.
So my suggestion: Limit the amount of data by implementing paging (somewhere between 20 and 50 items each time) and filtering.
Your argument is valid in principle, but you shouldn't base your it on the assumption that this list is actually being displayed to a user - there is no mention of such a thing. In fact there may be no UI involved at all.
The only issue we know of so far is memory consumption. Paging is a solution, but whether a page should hold 20 or 20000 items depends on the actual problem.