|
I need smthing that works with c++. 
"The Only Limit Is Only Your Imagination."
|
|
|
|
|
If you can do C++, then you can surely translate from C#. Especially since the functions you need to call are right in the code. 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Windows API has the function GetTopWindow
GetTopWindow function (Windows)[^]
From the TopWindow you want walk down thru the chain via GetNextWindow
GetNextWindow function (Windows)[^]
So in your case you want to ask the topWindow of the window that contains both FileZilla window and a Notepad Window. You can then walk along the chain using GetNextWindow and see which is above which just by asking the window title.
Something like this will work
char buf[256];
HWND Wnd = GetTopWindow( );
GetWindowText(Wnd, &buf[0], sizeof(buf));
while (Wnd != 0 && !stricmp(&buf[0], "FileZilla") && !stricmp(&buf[0], "NotePad"))
{
Wnd = GetNextWindow(Wnd, GW_HWNDNEXT); GetWindowText(Wnd, &buf[0], sizeof(buf)); }
if (Wnd == 0) {
}
else {
}
It is equivalent to
EnumChildWindows function (Windows)[^]
However for the simplicity you have it isn't worth setting up the enumeration function.
In vino veritas
|
|
|
|
|
Is there an Api to implement exception handling on function/frame thread basis without the _try _except/_catch statements as that limits me to only certain type of exceptions
It would be nice to have an api on a function or frame Even on a thread basis
The function and the frame saves the programmer from doing unwinding
with AddVectoredExceptionHandler I catch everything but then I have to figure out from which function the exception occurred
Thanks
|
|
|
|
|
it's been 2 days. i'm struggle with this things. this's still new. the documented it just only help a bit. i want to check session created or not. a.k.a Connected or not. i don't know why the developer MySQL make new terms to call a thing. in this code. everytime i change something credential thing like host, port, user,pass. it return same. and return unexpected result with long zero 00000000000000 if use cout to sess. in my server i already enable X Plugin. my enviroment is Visual Studio Community 2017 c++ desktop.
#include <iostream>
#include "mysql_xapi.h"
using namespace std;
int main()
{
mysqlx_session_t * sess;
char conn_error[MYSQLX_MAX_ERROR_LEN];
int err_code;
sess = mysqlx_get_session("127.0.0.1", 3306, "root", "root", "test", conn_error, &err_code);
if(!sess)
{
cout << "It's not connect";
}
else
{
cout << "It's connect";
}
mysqlx_session_close(sess);
return 0;
}
|
|
|
|
|
The function provides an error code and an error message upon failure. So print those out to get information on what went wrong:
sess = mysqlx_get_session("127.0.0.1", 3306, "root", "root", "test", conn_error, &err_code);
if (NULL == sess)
{
cout << "Connection failed; error " << err_code << ": " << conn_error << endl;
}
|
|
|
|
|
The error nothing helping. it shows string unexpected result and integer 1.
can u figure out when the error like that? i think can't.
|
|
|
|
|
I would expect a meaningful error message if one the parameters is wrong.
That generic message might indicate that it is networking problem. Because you are using localhost (127.0.0.1) it is probably not due to blocking by a firewall. You should check the port number and ensure that it is the port on which your server is listening.
Depending on the operating system, you might also us a command line utility to show listening ports (as root/adminstrator: Linux: lsof -nPi, Windows: netstat -ban).
|
|
|
|
|
Hi,
int x=11;
printf("%d %d %d ", x++,++x,++x);
It prints 13 14 14, But I thought 13 14 15
Why ?
|
|
|
|
|
Because you should never use such expressions. The compiler writers are allowed to handle the order of incrementation in any way they like, so the results may or may not be what you expect. Bottom line: don't do it.
|
|
|
|
|
I agree. but my doubt was how it happens.
|
|
|
|
|
|
|
It isn't a good answer it's wrong the result is undefined.
Try it on VS2017 and you will likely get "13 13 13 " because of the way the optimizer works.
In vino veritas
|
|
|
|
|
This expression is undefined by the C Standard, meaning that the compiler can do anything with it, including formatting your disk or causing demons to fly out of your nose. You should consider yourself lucky that the compiler only incremented 'x' in a weird manner. 
Note that even changing the compiler options (e.g. optimization) might change the printed results, so even if this "appears to work properly" on your system - DON'T DO IT!
(On comp.std.c and comp.lang.c they used to refer to a notional system, the DeathStation 9000, that would actually create Nasal Demons when it encountered undefined expressions )
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
thank you ..
|
|
|
|
|
Hi,
Is there a data type wchar_t in C?If so, how it differ from char?
|
|
|
|
|
Quote: Is there a data type wchar_t in C?
Yes, apparently[^].
Quote: If so, how it differ from char?
It is compiler dependent.
|
|
|
|
|
|
Thanks. I tried finding size of it and got 4 bytes. If so, It should be able to take something like "abc". But its not happening. Why?
|
|
|
|
|
Because "abc" is a char* string and not a wchar_t which represents a single character.
wchar_t are used to store fixed length Unicode characters like UTF-16 or UTF-32 while char can store fixed length ASCII or ANSI characters (with an associated code page) or variable length characters like UTF-8 or Microsoft multi byte characters.
|
|
|
|
|
Jochen Arndt wrote: wchar_t are used to store fixed length Unicode characters like UTF-16 or UTF-32
Just noting that statement is somewhat of a generalization.
For starters, unicode, for those bit sizes never represents all characters via single character. One needs to go to 128 bits for a full representation. Maybe that isn't even big enough.
Additionally it is not limited to unicode. Although perhaps these days that would be the predominant usage in the western world.
|
|
|
|
|
Quote: "wchar_t are used to store fixed length Unicode characters like UTF-16 or UTF-32"
Just noting that statement is somewhat of a generalization.
Why? As far as I know wchar_t is not used for variable length encodings.
jschell wrote: for those bit sizes never represents all characters via single character
While that is true for UTF-16 it is not for UTF-32.
jschell wrote: One needs to go to 128 bits for a full representation
That is wrong.
Tuesday, June 20, 2017
Version 10.0 of the Unicode Standard is now available. For the first time, both the core specification and the data files are available on the same date. Version 10.0 adds 8,518 characters, for a total of 136,690 characters. These additions include four new scripts, for a total of 139 scripts, as well as 56 new emoji characters. Still 14 of 32 bits unused.
|
|
|
|
|
Jochen Arndt wrote: Why? As far as I know wchar_t is not used for variable length encodings.
It is intended for any character set, not just unicode. Most representations are not unicode.
And unicode IS a variable length encoding to some meaning of that definition. There are escape characters in the 8/16/32 bit unicode character sets that allow for the definition of additional characters using multiple 'character' values. So two wchar_t might be needed for a single character.
Jochen Arndt wrote: While that is true for UTF-16 it is not for UTF-32.
"UTF-32 does not make calculating the displayed width of a string easier, since even with a "fixed width" font there may be more than one code point per character position"
UTF-32 - Wikipedia[^]
I will state that it is unlikely for this to be used.
Jochen Arndt wrote: That is wrong.
Presumably you are claiming that UTF-32 contains every possible character.
So based on that logic what exactly is in UTF-64? Just UTF-32 for the first half and the empty space for the rest?
Jochen Arndt wrote: Still 14 of 32 bits unused.
That isn't relevant. It isn't how the character set is defined but rather the extent and how it is used.
There are unused spots in a number of places in unicode in general. No idea why. Perhaps they figure a specific range of the character set might have a few more characters added in the future.
Far as I can recall many character sets beyond 7 bits end up duplicating or adding to a real character set. For example the normal extended ascii set has several dashes and a few mathematical symbols. And that is only using 8 bits.
|
|
|
|
|
Quote: It is intended for any character set, not just unicode. Most representations are not unicode.
Examples (I don't know one except when wchar_t is defined as char)?
Quote: And unicode IS a variable length encoding to some meaning of that definition
There are multiple Unicode encodings where some are fixed length and some are variable length.
Quote: So two wchar_t might be needed for a single character.
It is intended to be used for single characters. Allowing more than one requires a much more complex implementation (like with the char based Microsoft multi byte character sets).
Quote: "UTF-32 does not make calculating the displayed width of a string easier, since even with a "fixed width" font there may be more than one code point per character position"
Fonts and there display length is not related to character encoding specifications.
Quote: That isn't relevant. It isn't how the character set is defined but rather the extent and how it is used.
It is all about the definition regarding the required storage size.
The unused code points are there because the codes are grouped (each script or symbol type has an assigned range). See Unicode block - Wikipedia[^]. So new characters / symbols can be added later to the belonging group (a rather old example is the Euro symbol).
The grouping has been choosen because with 32 bits there is enough room. Unicode already contains nearly all known scripts including ancient ones like Runes and Mayan glyphs and a wide range of symbols.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
