- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking at the replies to an earlier post (dated 5-23-2001), I found out that this problem occurs if you specify a large window and your display is set to a high combination of resolution and color depth. I have a couple of follow-up questions:
1. How can I determine the largest allowable size? Is it machine or OS-dependent? By experimentation, I found a maximum of approximately 8E6 pixels on one machine.
2. Can I reduce the color depth with SETWINDOWCONFIG? I want to use this window to display a large monochrome (not gray scale) bitmap file? SETWINDOWCONFIG is allocating 8 bits per pixel, when all I need is one bit.
3. Is there a substitute for setwindowconfig that would get around this problem? It seems that pure windows applications are able to use much higher window sizes.
Thanks,
Gabriel
1. How can I determine the largest allowable size? Is it machine or OS-dependent? By experimentation, I found a maximum of approximately 8E6 pixels on one machine.
2. Can I reduce the color depth with SETWINDOWCONFIG? I want to use this window to display a large monochrome (not gray scale) bitmap file? SETWINDOWCONFIG is allocating 8 bits per pixel, when all I need is one bit.
3. Is there a substitute for setwindowconfig that would get around this problem? It seems that pure windows applications are able to use much higher window sizes.
Thanks,
Gabriel
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The maximum window size is OS-dependent - Windows 9X/Me is much more restrictive. The color depth is taken from your video adapter settings - you can't change it with SETWINDOWCONFIG.
I asked Bill Conrad about this, and he says that if you already have a bitmap created, you can display it. Attached (I hope) is a small program that demonstrates this.
Steve
I asked Bill Conrad about this, and he says that if you already have a bitmap created, you can display it. Attached (I hope) is a small program that demonstrates this.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Thanks for your response. I still have a question. How can I determine (or how can my program determine) the maximum size for a particular OS. I already know the limits for W98, but I would like users of my program in W2000 or NT to be able to use the greater resolution. Also, the technique of calling setwindowconfig a second time ifit returns an error does not seem to work.
Thanks,
Gabriel
Thanks for your response. I still have a question. How can I determine (or how can my program determine) the maximum size for a particular OS. I already know the limits for W98, but I would like users of my program in W2000 or NT to be able to use the greater resolution. Also, the technique of calling setwindowconfig a second time ifit returns an error does not seem to work.
Thanks,
Gabriel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry - I don't know of a way to determine this in advance. I think on Windows 2000, it's limited by your available virtual memory, but on 9X, there's some smaller limit.
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got the same error message in a quick win application when enlarging the child window buffer to more than 2047 lines: I have a AC with 512 MA Ram, WIN 2000 and enough (> 1 GA) virtual memory available: it is possible to check or enlarge the allocated memory?

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page