I using MFC and I want to know if there is a way to get the display screen resolution(s) without using DirectX. I just what to read it. I don what to change it.
3. Font size in different display resolutions - Borland C++ Builder VCL Components
4. What is the event we get on Display resolution changed?
hi,
can any body tell what Message we get when the display resolution is
changed?
regard Tony
5. Forms and resolution independent display - CSharp/C#
6. Interface guidelines for multi resolution display
I know this isn't really an MFC issue, but since the desired solution must be implemented with MFC, any ideas that already take into account MFC strengths and weaknesses would be appreciated. Without boring you with too many details, here is the requirement. We have a kiosk type environment running about 30 applications. The kiosk screen is small (640x480) and the apps were designed to fit. The apps have to allow editing of about 200-300 values which are logically grouped into categories. We use an SDI app, which hosts about 6 or 7 different views, each view representing a major category. The views are selectable through a toolbar. Then each view consists of several (Property)pages, each of which represents a subcategory. Some values are edited directly within edit boxes, some are represented by drop downs or radio groups. Each page also has a corner reserved for help bitmaps and text. This leaves enough room for about 17 values per page maximum. So far so good. Now we are switching to a larger screen (1220x1024). If we run our app without any changes then it fails to utilise all the screen real estate. If we maximise it then all that happens is that we get a lovely grey border to the right and bottom of the pages, which also fails to use the space. My questions is: What ideas do people have for improoving our app layout so that we can better use the increased screen size, given that we will have to support updates on both large and small screen for the foreseeable future and also, that I don't want to maintain parallel versions of the same product - one for big screen and one for small screen. Or that I don't want to have two sets of dialogs in each app (if possible). I considered some kind of expanding tree structure, since the data is well-organised along these lines already. This means that the big screen version would see more of the tree whereas the small screen users would "see life through a letter-box". Does anyone have a favourite control that fits the bill? Or better still some fresh ideas? Or examples of existing apps that tackle a similar problem? cheers, KMA
7. Resolution of secondary display
8. Load and display multi-resolution icon - Follow-up
Dear Asger/all,
Well, here's an oddity:
1. Create a new application.
2. On the form dump a 16x16 TImage.
3. Add a TOpenDialog.
4. Add a button and crate an OnClick event handler.
If you put in the code below, which loads the TImage with the
correctly-sized icon (IconFile.ico is a multiresolution icon file) and
assigns the OpenDialog to the ButtonClick handler, everything should compile
fine. Run it and all seems good (the icon should load at the correct size).
Now click the button - the OpenFile Dialog opens, but no icons are
displayed. Weird. Odder, if the last line in the constructor is commented
out (So TImageList is not deleted), then the Open File dialog works fine and
displays its icons ok.
I'd be grateful if anyone has any views on why the deletion of an
arbitrarily named TImageList should screw up the Open Dialog.
ATB
John B
The code:
//---------------------------------------------------------------------------
__fastcall TForm1::TForm1(TComponent* Owner)
: TForm(Owner)
{
TIcon *testIcon = new TIcon;
TImageList *XImageList = new TImageList(this);
SHFILEINFO Info = {0};
XImageList->Handle = SHGetFileInfo("IconFile.ico", 0, &Info,
sizeof(SHFILEINFO ),
SHGFI_SMALLICON| SHGFI_SYSICONINDEX);
XImageList->GetIcon(Info.iIcon, testIcon);
Image1->Picture->Assign(testIcon);
if(testIcon) delete testIcon;
if(XImageList) delete XImageList;
}
//---------------------------------------------------------------------------
void __fastcall TForm1::Button1Click(TObject *Sender)
{
OpenDialog1->Execute();
}
//---------------------------------------------------------------------------