|
Sorry for the incorrect edit.
The string was str which was getting the input and the string which reads the file is different as you said in the code.
I searched for the last word in the file and then it says found !. So that means it is working correctly but it's only searching for the last word in the file.
What to do ?
|
|
|
|
|
Put the test for equivalency inside the while loop. Currently the while loop reads all strings, when it exits the last string is in the variable, which you then test for.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
It's still searching for the last word Even after putting it into the while loop. Plz Help
|
|
|
|
|
Bro it's still the same. It's only searching for the last word of the file. Plz tell me what to do. I don't know what's happening
|
|
|
|
|
I am using a sample / example C++ (?) code and run into this, new to me , expression
array<Int32>^ DirMag;
I can ask Mrs Google. she knows stuff like that, but like to know if there are major advantages in using "string" array instead of customary C++ defined variable types.
In this example I would rather use "uint32_t" if it does not matter much.
Thanks
Cheers
|
|
|
|
|
This looks like "Managed C++", Microsoft's mutilation of C++ so that it fits into the .NET environment. IIRC, it was written as a "gateway drug" to get Standard C++ programmers to use the .NET environment, eventually graduating to C#.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Thanks.
It is going to be an uphill battle to convert whatever it is to plain C++.
Will keep me of the street.
|
|
|
|
|
It's C++/CLI the ^ denotes a handle to a reference.
C++/CLI - Wikipedia[^]
The key point to understanding it
Quote: Operator overloading works analogously to standard C++. Every * becomes a ^, every & becomes an %, but the rest of the syntax is unchanged
You need to reverse that to turn it into C++ code you would recognize.
I suggest you also want int32_t not uint32_t as just from it's name I am guessing it is a signed direction
In vino veritas
modified 29-Nov-18 21:21pm.
|
|
|
|
|
i want learn this,but i cannot to do
|
|
|
|
|
Well its deep, so, possibly, not easy.
I would start from the very Wikipedia page on the topic: Deep learning.
|
|
|
|
|
My brain hurt just reading through the highlights of that article! 
"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
|
|
|
|
|
Luckily, I don't need to learn that. 
|
|
|
|
|
I have tried implementing the tooltip using ctooltipctrl for drop-down list items on a combobox.
Have created one combo class to get the combo box handle and list box handle value.
From combobox I have called the presubclasswindow method of listbox and enabled tooltips using enabletooltips(true) and inside the list box class I override the ontoolhittest to get the row and rect area.
After this tnn_needtext notification has to be triggered to get the tooltip value.but in my case it is not getting triggered.
Please help me to solve this issue.
For the individual controls on dialogu box the tnn_needtext is getting triggered.
|
|
|
|
|
|
With the tracking tool tips the tooltip is getting displayed for each drop-down list item. Cant we implement the same tool tip functionality using CToolTipctrl.
I have tried all the possible scenarios to implement using ctooltipctrl, but it is not working for combo box. Except for Combo box the remaining controls i.e. listbox and other controls the Ctooltipctrl is working.
For combo box only we are not getting the TNN_NeedText notification
|
|
|
|
|
Well, the problem with "not getting TNN_NeedText" for the listbox appears to be because this listbox's parent is neither dialog nor combobox window. Instead it is a desktop!
However, TNN_NeedText like the other notifications are sent with WM_NOTIFY to the parent window.
|
|
|
|
|
Thanks victor for the providing the much needed answer
is there any other possibility to overcome this issue by using any other methods like setting the parent window as combo-box for dropdown list using setparent() mfc method.
|
|
|
|
|
You can find here[^] an extension of CComboBox, which do what you need, and more other.
|
|
|
|
|
i have used the tracking tool tips as mentioned in the provided link and it is working as expected.
As per my project requirement i have to use CToolTipctrl to implement the tooltip for ComboBox.
My question is can we implement tool-tip for combobox drop-down list using CtoolTipCtrl
|
|
|
|
|
|
I am sure this is a wrong place to post this , so do not crucify me.
I need to change gcc configuration to DIFFERENT "ARM" device.
WHERE do I find from where different "versions" of "gnueabifh" come from?
Here is a "prefix" sample I found.
It is really not only "prefix", but that is not relevant for now.
These configurations are in /usr/bin , so how do I determine which one to use ?
./configure -host=arm -prefix=$(DEVELROOT) CC=arm-linux-gnueabihf-gcc-4.8 ar=arm-linux-gnueabihf-ar-4.8
Cheers
|
|
|
|
|
Most GCC versions of GCC do processor families
If you are playing around with the Raspberry Pi again
BCM2835 Pi, Pi zero etc flag is -mcpu=arm1176jzf-s
BCM2836 Pi 2 flag is -mcpu=cortex-a7
BCM2837 Pi 3 flag is -mcpu=cortex-a53
If you want them with hard float points it's longer
BCM2835 Pi, Pi zero etc flag is -mcpu=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard
BCM2836 Pi 2 flag is -mcpu=cortex-a7 -mfpu=neon -mfloat-abi=hard
BCM2837 Pi 3 flag is -mcpu=cortex-a53 -mfpu=neon -mfloat-abi=hard
If you have a different CPU it's usually -mcpu="ARM CPU ID"
Finally version 6 or maybe 7 GCC is current version on Raspbian Stretch
sudo apt-get update your version OR download new version sudo apt-get install gcc
If you are Crossing from Windows/MAC/other linux variants the newest ARM CORP version is always here
GNU Toolchain | GNU-RM Downloads – Arm Developer[^]
On version 6 and above GCC you can now ask for supported processors with
gcc -mcpu=list
It spits something like this
Quote: arm-none-eabi-gcc: note: valid arguments to '-mcpu=' are: arm1020e arm1020t arm1022e arm1026ej-s arm10e arm10tdmi arm1136j-s arm1136jf-s arm1156t2-s arm1156t2f-s arm1176jz-s arm1176jzf-s arm2 arm250 arm3 arm6 arm60 arm600 arm610 arm620 arm7 arm70 arm700 arm700i arm710 arm7100 arm710c arm710t arm720 arm720t arm740t arm7500 arm7500fe arm7d arm7di arm7dm arm7dmi arm7m arm7tdmi arm7tdmi-s arm8 arm810 arm9 arm920 arm920t arm922t arm926ej-s arm940t arm946e-s arm966e-s arm968e-s arm9e arm9tdmi cortex-a12 cortex-a15 cortex-a15.cortex-a7 cortex-a17 cortex-a17.cortex-a7 cortex-a32 cortex-a35 cortex-a5 cortex-a53 cortex-a57 cortex-a57.cortex-a53 cortex-a7 cortex-a72 cortex-a72.cortex-a53 cortex-a73 cortex-a73.cortex-a35 cortex-a73.cortex-a53 cortex-a8 cortex-a9 cortex-m0 cortex-m0.small-multiply cortex-m0plus cortex-m0plus.small-multiply cortex-m1 cortex-m1.small-multiply cortex-m23 cortex-m3 cortex-m33 cortex-m33+nodsp cortex-m4 cortex-m7 cortex-r4 cortex-r4f cortex-r5 cortex-r52 cortex-r7 cortex-r8 ep9312 exynos-m1 fa526 fa606te fa626 fa626te fa726te fmp626 generic-armv7-a iwmmxt iwmmxt2 marvell-pj4 mpcore mpcorenovfp native strongarm strongarm110 strongarm1100 strongarm1110 xgene1 xscale
-mfpu=list
Quote: arm-none-eabi-gcc: note: valid arguments to '-mfpu=' are: auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16 neon neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2 vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 vfpv4-d16
In vino veritas
modified 21-Nov-18 0:45am.
|
|
|
|
|
Thanks Leon.
Here is "MY problem" - as far as I can tell I am ONLY setting "Cross compiler prefix" as "arm-linux-gnueabihf-" and "Path" where it can be found as "/usr/bin".
I have no idea where this "prefix" came from - I have been at this project for a while , off and on.
It shows up in "include" tree on the Eclipse project form.
The code complies and runs on BCM2837 - RPi 3B.
Without changing any GCC setting the code compiles and sort of runs on BCM2835.
At least it starts.
I get a ton of errors and a simple , clean "hello word" obviously does not show in "TCF Debug Process Terminal" where I get all the coded messages and responses when I run same code on BCM2837.
I have been advised to check and possibly reinstall TCF Agent when connected to BCM2835.
I need to find, again, the real, not 3rd party copies, of TCF Agent installation tutorial.
However, if it solves the problem it kinda-of defeats the "universal" purpose of TCF.
Many thanks for your input.
PS
Forgive OF ,senior moment, you are in Holland , right?
|
|
|
|
|
No I am in Australia .. ancestors are Dutch, South African
Anyhow you have many and varied problems ... Now all GCC have a name format called ABC
Quote: GCC A-B-C name convention
A indicates the target (arm for AArch32 little-endian, aarch64 for AArch64 little-endian).
B indicates the vendor (none or unknown for generic) . Note that this is optional (Eg: not present in arm-linux-gnueabihf)
C indicates the ABI in use (linux-gnu* for Linux, linux-android* for Android, elf or eabi for ELF based bare-metal).
C has values which seem odd until you understand the history behind it (basically AArch32 used to have a linux-gnu ABI which got changed so needed a new name so we have linux-gnueabi). For AArch32 we have linux-gnueabi and linux-gnueabihf which indicate soft float, and hard float respectively.
The bare-metal ABI will assume a different C library (newlib for example, or even no C library) to the Linux ABI (which assumes glibc). Therefore, the compiler may make different function calls depending on what it believes is available above and beyond the Standard C library.
So you have A-C your compiler is linux gnu and the output is hard floats.
What it doesn't tell me is if you are compiling on Raspbian Pi or some other linux version because that isn't inbuilt into the name. What I do know is you are putting out the right thing if you are trying to do baremetal.
Now the big problem there are big differences between where peripherals are and what they do between a Pi1, Pi2, Pi3.
So first the peripheral base address is different on a Pi1 all peripherals are at 0x20000000 on a Pi2/Pi3 they are at 0x3F000000
So that means if you ever see a peripheral with 0x20xxxxxx you know it is for a Pi1 and if you are on a Pi3 you need to change it
to 0x3Fxxxxxx. There are no exceptions every peripheral is physically moved to allow for more memory. The converse is also true
any address with 0x3Fxxxxxx is for a Pi3 and wont work on a Pi1 and you change the first two to 0x20xxxxxx
Generally we #define a variable called PI_IO_BASE or such and we just change that one number the alternative is you can autodetect it
by looking for USB hub vendor string which is on every model. The logic goes look at the Pi location if it isnt there its at the other.
volatile uint32_t* vendorid = (uint32_t*)0x20980040;
if (*vendorid == 0x4F54280A) PI_IO_BASE = 0x20000000;
else PI_IO_BASE = 0x3F000000;
So you deal with that first thing in your code and then you have the different model peripheral address covered.
There is one final snark, the UART change between models if you use it as a terminal and it is covered here
The Raspberry Pi UARTs - Raspberry Pi Documentation[^]
Quote: By default, on Raspberry Pis equipped with the wireless/Bluetooth module (Raspberry Pi 3 and Raspberry Pi Zero W), the PL011 UART is connected to the BT module, while the mini UART is used for Linux console output. On all other models the PL011 is used for the Linux console output.
So they are the programming differences between all the PI models and it is what it is.
I suspect your code is running into one or multiple problems related to those because you can't just write code for one Pi and have it work on another unless you strictly write only using the linux drivers. The moment you start poking anything with hardware you need to be aware of model differences.
If you get stuck just ask, we bash the thing around baremetal I never use linux at all ... so we know it pretty well.
In vino veritas
modified 21-Nov-18 11:34am.
|
|
|
|
|
Thanks, I am embarrassed , I think you told me the "prefix format" long time ago.
I am just getting too old for all this stuff.
My uncle whom I never met "emigrated " in 1948 to Australia after Communists took over.
We for obvious reasons we did not keep in touch, but I remember in the only letter we got from him he said he bought Jawa, Czech made, motorcycle and eating prawns was a "shell spitting affair".
Of course we knew about Jawa , but prawns?
I think with computers abilities I could do some search for relatives still living in "down under".
I just reinstalled TCF and can run its diagnostic test.
Still no output to TCF terminal. But its a start.
I actually build simple "hello world" app and that should (?) work independently from memories of these processors.
I think the processor dependencies or in-dependencies is "hidden" somewhere in TCF make.
But that is little out of my league.
Cheers
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
