|
I can't rly get the debuger to stop there ... It's kinda like skipping it all? Any other way of checking ?
|
|
|
|
|
Vladislav Gospodinov wrote: Any other way of checking ?
TRACE() .
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
So it doesn't TRACE() anything at all when called in
CMainFrame::OnMouseMove so it's like it doesn't get the mouse moving at all in MainFrame class...
it does trace correct values if I call it in the View class
CpositionView::OnMouseMove
however I can't find a way to send them from View to MainFrame, although I have included ***View.h and taka them like
CpositionView::positionX
I get a lot of errors :P
|
|
|
|
|
Try this!
void CDlgStatusBarDlg::OnMouseMove(UINT nFlags, CPoint point)
{
CString s;
s.Format("X=%d Y=%d",point.x,point.y);
m_bar.SetPaneText(0,s);
CDialog::OnMouseMove(nFlags, point);
}
Source: [Adding a status bar to an MFC dialog[^]]
|
|
|
|
|
I want to spend one hour a day, five days a week, for three weeks, with a small kit.
Atmel, AMD, Intel, Motorola, PIC, ST-Micro, Your_Favorite_Suggestion_Here,,,, I'm happy to look at anyone's opinion, especially those who have been there / done that.
The concept I have in my head is to review the basics, test out some simple circuits, blink some lights, read some knobs, communicate via some UARTs, write a few interrupt handlers for push button switches, set up a bluetooth connection, access a wifi connection, maybe send a ping command to some machine, arrange a USB connection,,,,
I'm thinking along the lines of a microcontroller on a printed circuit board, with pins and clips and stuff that are large enough to test with alligator clips and so on.
yackity yackity yack; whatever.
Please offer your idea(s) as to which vendor(s) offer(s) such a kit that will be most useful for this.
Top considerations are
-- PC software; e.g., compiler, debug, and an Interactive Development Environment are high on the list
-- Cost, and price.
-- Existing online user community
-- Documentation
-- Physical size large enough to get to the physical pins via printed circuit lines
-- Physical size small enough to let you work on your desktop
SUGGESTIONS ???
|
|
|
|
|
This interests me. See if it interests you:
Single Board Computer[^]
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Excellent marketing if nothing else.
Good picking it out on your part.
I looked at it and in two seconds thought "yes" without reading a single word about it.
I'll spend 90 seconds reading about it and see what I think.
If you have any personal experience with this board, put up some words that everyone can read.
|
|
|
|
|
Good stuff; the debug looks good.
I didn't see anywhere to develop USB code for your own USB projects.
Did I miss something ?
|
|
|
|
|
Never heard of the Rabbit 4000.
Anybody worked with this on a regular project ?
|
|
|
|
|
We did one project with it and it turned out fine, decent debugger, and as I recall lots of example projects. The documentation was good, the parts had good amounts of RAM and Program space, they are not the fastest processors around nut they served our needs well.
|
|
|
|
|
Was USB involved in your projects ?
|
|
|
|
|
No, it was serial and ethernet stuff (they had a nice TCP/IP stack).
|
|
|
|
|
|
Thank you for the suggestion; my answer on Arduino is no.
The reason: It's so small that I honestly have great difficulty connecting alligator clips to the various pins.
My thoughts at this time are running toward an embedded systems tutorial; possibly with a video presentation. I think I may want to make a "Barney Box" (named after Barney on Mission Impossible in the 1960s, who created small, hand-held, obviously useless plastic boxes with switches and LEDs, which would do insanely complicated procedures; turn cars around and stuff)
At this moment I want something where the pins are accessible for alligator clips; with specific accommodation for people with fumbling EL-Spaz-O-Max fingers like myself.
[Edit] Just looked at the photos of the Raspberry; ditto, too small
|
|
|
|
|
I do not know which part you want to crocodile-bite, but maybe you can plug one of these boards on a larger board with expanded crocodile-friendly biting zones. A zoomer of some sort
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
Rage wrote: A zoomer of some sort
Yes, that's the whole idea; my full contention.
i.e.,,,,,,,,
If we could make these things large enough to work with, we could create stuff on our desks, first, and make them work, and watch them in real life, and do (an awful lot of) the validation and verification ahead of time, and get the bugs out first, BEFORE we shrink them so small that they become inaccessible to human hands.
That's my whole idea: itty bitty microprocessors and microcontrollers, on boards which have posts and clip-ons and access points that are large enough for bumble-thumbs like me.
(Unless, of course, I'm the only one who can't access two pieces of metal when they're closer than a millimeter)
|
|
|
|
|
Re: The reason: It's so small that I honestly have great difficulty connecting alligator clips to the various pins.
Forget the alligator clips. Get a crimper and some socket and pin ends that match the connector or pins available. Crimp the pin/socket on the end of your wire and put anything you want on the other end. Use various colors of wire to make it easy.
To the OP, do some googling on demo and prototype boards. If you are really serious, for less than $100 you can get a demo/prototype board for just about any type of processor. Usually way less.
Edit: Get some heat shrink tubing to insulate the crimped end.
|
|
|
|
|
Device drivers are of course a good way to learn all about USB, UARTs, interrupts etc, but, you also need to learn a heck of a lot of Kernel/OS stuff too, so even though Linux is easier than Windows, kernel wtuff might be too daunting for him so I would go for a dev board with a very simple model so he can focus just on HW.
"The whole idea that carbon dioxide is the main cause of the recent global warming is based on a guess that was proved false by empirical evidence during the 1990s." climate-models-go-cold
|
|
|
|
|
|
I want to use the Windows CMD tree command in my C++ console application.it is possible ?
|
|
|
|
|
Yes.
It's both possible and very easy, as it turns out.
Drawing on an old (and frowned-upon) practise of using a system call to clear the screen or wait for a keystroke,
system("CLS");
and
system("PAUSE");
You can achieve your aim using the system function. Just remember to use forward-slashes (/) in the path-name or to use double back-slashes (\\)
E.g
system("tree c:\\xampp");
system("tree c:/xampp");
|
|
|
|
|
Error in code plz help me...
#include<stdio.h>
#include<conio.h>
#include<dos.h>
#include<windos.h>
void main(){
system("tree c:\\xampp");
getch();
}
|
|
|
|
|
Apart from the fact that you mis-spelt windows , what else is wrong?
|
|
|
|
|
compilation Error is given :
Unable to Open include File ''windows.h
|
|
|
|
|
The code you showed above has it spelled as windos.h (missing the last w character). If it is spelled correctly then ensure you have set the path(s) foe the correct include directories. If you are using visual Studio then this should have been done for you at install time.
|
|
|
|