I am trying to add "forms " to my exiting project.
I follow the Qt menus... but I do not know how to modify my constructor.
, ui(new Ui::MainWindow)
isUntitled = true;
Please help me to understand what Qt did and how to modify
my constructor so I can access my "form".
The verbal description / code annotation would be appreciated.
It is a single parameter constructor of the MainWindow class. The constructor accepts a single parameter which is a pointer to a QWidget object. The constructor sets its QMainWindow property to the input parameter - in this case the pointer named parent. It then sets its ui property by calling the Ui::MainWindow constructor, to create a new object of that class. To find out what the latter returns you need to look at the Ui class documentation.
But maybe you don't want to actually implement a terminal application? In which case, either I've misunderstood your query, or you need to reframe your question to better reflect what it is you are trying to do.
Thanks for reply. I am actually looking for "discussion forum" . I am running out of ideas how to fix my problem.
Yes , I did try qterminal - it has no option to run command with options - so I ended up with xterm.
It works OK, but I cannot figure out how to FULLY integrate it with my application.
I am able to display the command output in my app "window" but it is NOT really my app window - some folks call it "xterm native window ".
So I can display it - it is "inside my other window" , I can move it , using my app "wrapper window", but I cannot process anything in it.
I am actually hoping that somebody with good grasp of "windows hierarchy" can shed some light on this.
In not so techie terms - how do I process data in xterm native window ?
I will take a look at xterm man again, maybe the answer is there.
You have declared Sp1 to be an array of pointers, each of which points to a strTst structure. So to get one of the pointers you just need normal array addressing, e.g. Sp1 returns the second element of the array. So all you need is:
strTst *pt = Sp1; // pt now equals &spst2
intvalue = pt->s2; // get the value of spst2.s2
strTst *pt = Sp1;
pt->s1; // is spst1.s1
pt->s2; // is spst1.s2
pt->s3; // is spst1.s3
pt = Sp1;
pt->s1; // is spst2.s1
pt->s2; // is spst2.s2
pt->s3; // is spst2.s3// alternative
strTst **ppt = Sp1;
ppt->s1; // is spst1.s1
ppt->s2; // is spst1.s2
ppt->s3; // is spst1.s3
ppt->s1; // is spst2.s1
ppt->s2; // is spst2.s2
ppt->s3; // is spst2.s3
My working environment is: Windows 10, Visual Studio Community 2017 (and 2008 for older projects), programming takes place only in C/C++.
I need my program to be able to send emails with a PDF file attachment. The easiest way to send emails is to use ShellExecute with the parameter "mailto:email@example.com ... etc". But this method does not allow you to transfer attachments.
However, when I trying to send an email on another computer, it leads to an error in the MAPISendMail function MAPI_E_NOT_SUPPORTED (code 26). In this case, the MAPILogon(Ex) function is executed without errors. Both computers, mine and the other, are on the same network and use the same mail server and Outlook as the client for users. On the other computer send/receive of the emails works perfectly. I searched the Internet for a long time for an explanation of this error, but found nothing. A search on the site CodeProject also did not give anything.
Please explain me what this error means and how to fix it. Thank you very much!
The issue is that some parameter that is in that SendMail call is incorrect according to the client or server that is handling the request. But there is no way anyone here can tell which it is. You need to capture more information somehow.
We had similar problems (sending e-mails with attachments). But since all our customers use MS Outlook as a standard e-mail application, we just implemented the Outlook automation. So the problem was solved.
Unfortunately, we do not use Outlook automation, we just have Microsoft Office installed with the Outlook mail program. In addition, it is important to me that my program can send an email from different computers. And finally I want to understand what's the matter here
It is not a big problem to implement the Outlook automation: about two to three working days (including tests and reading documentation).
The only problem I see is some of your customers may use some other (non-Outlook) mail-application, so my suggestion won't work for them.