C / C++ / MFC

28-Apr-05 4:13

Daniel Kanev wrote:
I have written a MDI Application opening and reading files of type *.myapp

Did you use AppWizard for this?

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

C++ multiplication

28-Apr-05 3:55

In visual studio .net ver 2003 in reguards to c++ my multiplication is messed up. I get a result of 0 when I try and multiply the following. What's wrong?

#include "stdafx.h"

#using <mscorlib.dll>
#include "math.h"

using namespace System;

int _tmain()
{
__int64 p;

p= 16 * 268435456;

Console::WriteLine(p);
return 0;
}

David Crow28-Apr-05 4:07

28-Apr-05 4:07

I assume that the WriteLine() method supports a __int64 type. What is the largest value (e.g., 2³¹) that you can successfully send to WriteLine()?

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Andrew Admire28-Apr-05 4:14

28-Apr-05 4:14

The number I am multipling with 16 is the highest number for the output.

David Crow28-Apr-05 4:20

28-Apr-05 4:20

If 2²⁸ is the highest number for the output, what does outputting 2²⁸ + 1 produce? If that does not work, I would expect 2³² to fail as well. Yes?

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Andrew Admire28-Apr-05 4:34

28-Apr-05 4:34

The highest number I can multiply it to is 7 after that I get the error message:

warning C4307: '*' : integral constant overflow

David Crow28-Apr-05 4:44

28-Apr-05 4:44

That indicates that you are running into a signed/unsigned problem. What does this yield:

p = 8U * 268435456U;

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Andrew Admire28-Apr-05 4:59

28-Apr-05 4:59

Same error.

David Crow28-Apr-05 5:05

28-Apr-05 5:05

What about:

unsigned __int64 p;
p = 16U * 268435456U;

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Andrew Admire28-Apr-05 5:12

28-Apr-05 5:12

Nope, same error.

Michael Dunn28-Apr-05 5:45

Michael Dunn

28-Apr-05 5:45

The compiler is telling you exactly what's wrong "integral constant overflow". That expression overflows the capacity of an int. You need to specify that the constants are 64-bit ints:

p = 16I64 * 268435456I64;

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ
Strange things are afoot at the U+004B U+20DD

David Crow28-Apr-05 6:30

28-Apr-05 6:30

Thanks Mike. I was aware of L and U but did not know about the I64 modifier.

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Andrew Admire28-Apr-05 9:14

hide or remove toolbar buttons?

28-Apr-05 9:14

That worked great. However is there a way I can use exponents with the 64-bit int's?

Sean McKinnon28-Apr-05 3:53

28-Apr-05 3:53

I'm sure there is something simple and obvious that I am missing here, maybe somebody can help me?

I have a toolbar that gets initialized from a toolbar resource (one big bitmap with all images in it).

The toolbar is customizable (using standard dialog), so that when the dialog is displayed, you get a list of all the buttons available on the left, and a list of all the buttons currently on the toolbar on the right.

The buttons on the left and right together are all of the buttons available in the toolbar resource bitmap.

In some cases, I would like to exclude some buttons in the toolbar resource bitmap from being displayed as available (i.e. remove them from the left list).

When the list is populated, you get messages that let you say whether the button is available, but the first time you say no, it stops asking about the remaining buttons.

Like I said, there must be something simple I am missing.

Thanks for you help!

- Sean

David Crow28-Apr-05 5:11

28-Apr-05 5:11

Sean McKinnon wrote:
In some cases, I would like to exclude some buttons in the toolbar resource bitmap from being displayed as available (i.e. remove them from the left list).

Wouldn't it be easier to just enable/diasble the buttons? If not, then you'll probably need to create multiple toolbars (one for each situation).

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

Sean McKinnon28-Apr-05 5:22

28-Apr-05 5:22

DavidCrow wrote:
Wouldn't it be easier to just enable/diasble the buttons? If not, then you'll probably need to create multiple toolbars (one for each situation).

Yes, it would be easier, and I do that in other circumstances.

My problem is that I have a single application that talks (serial or ethernet) to several different versions/types of hardware. The application automatically configures itself to the capabilities and resources of the attached hardware. (It is a user-interface for status monitoring and configuation of the hardware).

The application has always removed menu items for features that the attached hardware cannot support, and disabled menu items for features that the hardware could support, but that are not currently enabled. This works fine for menu items.

The toolbar used to be fixed (and only included items that were supported on all hardware platforms). Now, we've added customizable toolbars, so I now have buttons for features that may not be supported on various hardware platforms. I can (and do) still disable toolbar buttons for features that are supported but not enabled (and I also do this for toolbar buttons for features that are not supported at all, but would really prefer to hide/remove these buttons like I do for menu items).

Creating multiple toolbars for all the possible configurations would be a nightmare for sure.

I guess this isn't as easy as I had hoped for?

Thanks - Sean

cmk29-Apr-05 21:04

cmk

29-Apr-05 21:04

If you are using MFC:

CToolBar tb;
tb.GetToolBarCtrl().HideButton(ID_CONNECT, TRUE);
tb.GetToolBarCtrl().HideButton(ID_DISCONNECT, FALSE);

also (from MSDN):
Customizing a Toolbar
A toolbar has built-in customization features that you can make available to the user by giving the toolbar the CCS_ADJUSTABLE common control style. The customization features allow the user to drag a button to a new position or to remove a button by dragging it off the toolbar. In addition, the user can double-click the toolbar to display the Customize Toolbar dialog box, which allows the user to add, delete, and rearrange toolbar buttons. To display the dialog box, use the TB_CUSTOMIZE message. An application determines whether the customization features are available to the user and controls the extent to which the user can customize the toolbar.

As part of the customization process, applications often need to save and restore a toolbar's state. For instance, many applications store the toolbar state before the user begins customizing the toolbar in case the user later wants to restore the toolbar to its original state. The toolbar control does not automatically keep a record of its precustomization state. Your application must save the toolbar state in order to restore it. For more information, see Customizing Toolbars and Using Hot-tracking with Toolbars.

...cmk

Save the whales - collect the whole set

Sean McKinnon2-May-05 4:30

2-May-05 4:30

Thanks for the reply!

I am using MFC, and the HideButton method works for hiding buttons on the Toolbar in the MainFrame, but does not work when showing the customization dialog. When the customization dialog is shown, hidden buttons ARE shown in the right-hand list (populated buttons), but are shown with grey text (indicating they are hidden/disabled). ALL buttons not already in the toolbar are shown in the left-hand list (available buttons).

I need to be able to prevent buttons in the toolbar resource from showing up in both the available and populated button lists on the customize dialog. (i.e. make it look like the button does not exist at all).

During the building of the customization dialog lists, there are messages sent that query whether a button should be included, but if you indicate that it should not, then the process stops right there, and no more queries are sent for buttons that follow that one in the resource. (i.e. the first time you say "No" to a button, it aborts the queries for any remaining buttons).

I thought there might be a way to either respond differently to the message, respond to a different message that I am unaware of, or get access to the dialog lists and manually remove the unwanted items before the dialog is displayed.

Thanks again,

Sean

cmk2-May-05 10:10

cmk

2-May-05 10:10

Then i expect you will have to manually add/delete buttons after you create the toolbar from the resource. Once deleted the buttons should not show in either the left or right cutomization lists.

The problem is you are trying to impliment 2-level customization support and the built-in toolbar customization only supports 1-level. You will have to code the wrapping customization level.

...cmk

Save the whales - collect the whole set

Sean McKinnon2-May-05 10:27

2-May-05 10:27

cmk wrote:
you will have to manually add/delete buttons after you create the toolbar from the resource

Ah Ha! Yes, this is what I had been trying to do, but DeleteButton didn't appear to work for me.

I went back to try again, and I now realize my mistake. HideButton takes a command ID to hide, but DeleteButton takes an index (which you have to get by using CommandToIndex). I had been calling DeleteButton with a command ID. Now I can delete the unnecessary buttons at startup, once I've determined the configuration I need.

I knew there had to be an easy answer.

Thanks very much for your help!

Cheers - Sean

Sean McKinnon2-May-05 10:39

2-May-05 10:39

Well, not quite.

DeleteButton (with index) does delete the button from the toolbar, so it no longer shows up in the right-side list of the customize dialog (like it did when the button was hidden), but it DOES still appear in the left-side (available list).

Doh!

Is there another way to delete/remove the button from the CToolBarCtrl after it has been loaded from the resource?

Thanks again,

Sean

Sean McKinnon2-May-05 10:58