Resources in a C gauge

[Rocky 128]

Do you know if there is a limit in the number of bitmap resources defined in the .rc file?I have a srange "Out of memory" error that I can't understand, and it may come from th eincreasing number of bitmaps used in my gauge.Thanks for any help.Eric

[Rocky 128]

Please ignore my question, sorry for this...I found the solution to my problem, which is not a limit in the number of resources managed in a gauge. I guess there is no limit.Sorry for disturbing...Eric

[n4gix 4,947]

>Please ignore my question, sorry for this...>I found the solution to my problem, which is not a limit in>the number of resources managed in a gauge. I guess there is>no limit.I should think you would run out of memory long before reaching the real limit of #FFFF... ;)

[Rocky 128]

That is right !! ;-)BTW, I will let you know what the problem was:Some of the bitmaps I used are "corrupted". I don't exactly know what it means, because these BMP files could be open and edited in any editor. What I know is that they were causing an "out of memory" error in FS. I simply open the BMP and re-saved them, and everything was fine !!Strange, isn't it ?Eric

[Guest bartels]

Like Bill said you'll run out of memory before you run out of ids. But there is a limit, I think at 0x7FFF, for ids the resource compiler can handle. If you are too generous (e.g. use an offset of 1000 from subgauge to subgauge) you can run out of ids pretty soon even if the actual number of ids is quite small.Also don't forget the +500 offset for high-res bitmaps. You can choose ids quite freely, but not totally without thinking.Arne Bartels

[Guest bartels]

A "corrupted" message is also thrown if a resource id is used twice, you might check that also.Arne Bartels