Remy Lebeau

That won't work, as PROCESS_QUERY_LIMITED_INFORMATION is not a conditional you can test with {$IFNDEF}. Use {$IF NOT DECLARED} instead: {$IF NOT DECLARED(PROCESS_QUERY_LIMITED_INFORMATION)} const PROCESS_QUERY_LIMITED_INFORMATION = $1000; {$IFEND}

What I described earlier is based on stepping through the actual RTL source code. Adding Variant(string) + Variant(TBcd) converts the string to a TBcd, it does not convert the TBcd to a string.

You don't really need a per-topic option. Read the topics that you are actually interested in, and then you can "Mark site read" to clear out the unwanted topics. If you are on mobile, the option is in the top-right menu in the Account section. If you are on desktop, the option is on the bottom footer of every page.

Such as? Can you be more specific? What exactly are you entering into postman? Not without knowing what the endpoint is actually expecting, and what your actual code looks like that is not working for you.

I'm not bashing you around. I'm trying to be straight with you. StackOverflow is a Q&A site, not a help forum. It can be a pretty hard place on beginners who don't take the time to read the documentation and follow the guidelines. Your question in its initial form was not a good fit for the site, that's why it got closed pretty quick. But rather than fix it, you chose to delete it. As is your right. But, I suggest you take some time to learn how the site actually works before posting a new question there again. That's Visual Basic, not Pascal. VB and Pascal are very different languages, with different syntaxes and semantics. You made some minor mistakes in the translation. Specifically: you aren't setting a couple of VSSpell's properties your while loop is looking at the wrong value your switch block is missing a case when VSR_CHECK_CANCELED is detected, you are exiting the whole function instead of just breaking the loop. Try this: SpellChk->EventOptions = 0; SpellChk->AutoPopup = false; SpellChk->CheckText = Memo1->Text; int ResCode = SpellChk->ResultCode; while (ResCode < 0) { switch (ResCode) { case VSR_WORD_MISSPELLED: case VSIR_IGNORE: SpellChk->PopupWordMisspelled = 1; ResCode = SpellChk->ResultCode; break; case VSR_BREAK: SpellChk->ReplaceRecheck; break; } if (ResCode == VSR_CHECK_CANCELED) break; ResCode = SpellChk->ResumeCheck; } Memo1->Text = SpellChk->Text;

It compiles and runs perfectly fine for me. What version of C++Builder are you using? The _D() macro is defined in sysmac.h (a core system header) and has been available since C++Builder 2009 when the RTL switched to Unicode. The macro ensures a string/character literal matches the same data type used by System::Char depending on which platform you are compiling for - wchar_t on Windows and char16_t on Posix. There are no Variant's or Currency's in this code, so you should not be getting those errors. The only use of operator+ is to concatenate a string literal with a System::String, and that is a well-defined operation. I'm starting to think you are trying to run VCL GUI code in a project that does not actually have the VCL enabled properly. That is because you declared the square() method as having an 'int' return type, but there was no 'return' statement inside the method's body. If you look at the code I gave you, I declared square() with a 'void' return type instead. Because there is no value worth returning to the caller. But, you are not USING THEM for anything, they are just sitting there. The rest of your code uses only LOCAL VARIABLES of the same names, which shadow the class members, All data members of a TObject-derived class (like TForm is) are initialized to zeroes before the constructor is called. And then you were not assigning any new values to them afterwards. But you did rewrite it nonetheless, even if unintentionally. Which is exactly what the code I gave you does. This code is written wrong. You removed the couts, but you did not remove the loops, too. You are calling square() inside the 1st loop, and calling 'return' in the 2nd loop. So, this code behaves as-if you had written it like this: void __fastcall TForm1::Button1Click(TObject *Sender) { int i, nums[] = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}; for(i = 0; i < 10; i++) { square(nums, 10); } for(i = 0; i < 10; i++) { return; } } You are using the num variable that is local to the square() method, not the num variable that is declared as a member of the TForm1 class. And num is ALWAYS 0 when the 'return' statement is reached. This code is displaying the values of the class members, which you are NEVER assigning any values to, so they just have their initial values of 0. If you really want to use class members, then the code should look something more like this: class TForm1 : public TForm { __published: TButton *Button1; TButton *Button2; TLabel *Label1; TLabel *Label2; void __fastcall Button1Click(TObject *Sender); void __fastcall Button2Click(TObject *Sender); private: // User declarations int nums[10], num; void square(); ... }; void __fastcall TForm1::Button1Click(TObject *Sender) { for(int i = 0; i < 10; ++i) { nums[i] = i+1; } num = 10; square(); } //--------------------------------------------------------------------------- void TForm1::square() { int *n = nums; while(num) { *n = *n * *n; num--; n++; } } //--------------------------------------------------------------------------- void __fastcall TForm1::Button2Click(TObject *Sender) { String s = _D("Array values:"); for(int i = 0; i < 10; ++i) { s += (_D(" ") + IntToStr(nums[i])); } Label1->Caption = s; Label2->Caption = IntToStr(num); } //---------------------------------------------------------------------------

It does, but in this case, since the operation involves a native type (string) on the left and a custom user type (TBcd) on the right, the operation gives the custom type an opportunity to decide whether to cast the left side to the custom type, which it does in this situation, and then the failure occurs during that cast from string to TBcd.

Why? Those variables are not being used anywhere, so there is no point in declaring them there. Why are you calling the function 10 times? The original OP code called it only 1 time. Each time the function is called, the contents of the array are altered, but your code is not using the array values for anything, so there's really no point in altering the array at all. At least the OP's code was outputting the original values and then the altered values. You are not doing that. Why are you updating the Label 10 times with the same value? Perhaps you meant to display nums[ i ] instead? But then you would end up displaying only the last integer in the array. If you want to display all 10 values at one time, this is not the correct code for that task. You are updating the Labels in different places using different variables that have different values, so of course the results are going to be different. When updating Label1, you are using the nums variable that is local to the Button1Click() method. For starters, that code should not even compile as shown, as nums is an array, but the Sysutils::IntToStr() function does not accept an array as input, If this is indeed your actual code, the only way it could work is if the compiler decays the array into an int* pointer to the 1st array element, and then implicitly converts that pointer into a boolean, and then implicitly converts that boolean into an integer. That is too many implicit conversions for one statement, per the C++ standard. But, lets assume your compiler ignores that fact, then that would explain how you end up with a final output of "1", as a non-null pointer converts to a boolean true, and true converts to an integer 1. When updating Label2, you are using the num parameter that is local to the square() method, which was decremented to 0 while the loop ran. If you really want to replicate the OP's code but display the results in a GUI instead of a console, then try something more like this instead: class TForm1 : public TForm { TButton *Button1; TLabel *Label1; TLabel *Label2; void __fastcall Button1Click(TObject *Sender); private: void square(int *n, int num); }; void __fastcall TForm1::Button1Click(TObject *Sender) { int i, nums[] = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}; String s; s = _D("Original array values:"); for(i = 0; i < 10; ++i) s += (_D(" ") + IntToStr(nums[i])); Label1->Caption = s; square(nums, 10); s = _D("Altered array values:"); for(i = 0; i < 10; ++i) s += (_D(" ") + IntToStr(nums[i])); Label2->Caption = s; } //--------------------------------------------------------------------------- void TForm1::square(int *n, int num) { while(num) { *n = *n * *n; num--; n++; } } //---------------------------------------------------------------------------

Because, that is essentially what you did ask for - a tutorial on how to use the OCX control. THAT is what you should have asked for instead. That would have made for a better StackOverflow question, and less likely to be closed. Also, since you clearly know what you are looking for, you should have explained/shown what you had already tried that didn't work for you. Then you should have included one of those examples in your StackOverflow question and asked how to accomplish the same thing in C++. I can't find any documentation or examples of the OCX control, in ANY programing language. Can you provide a source?

No. There are only 10 integers declared in the array (values 1..10). Valid indexes into the array are only 0..9, inclusive.

The Parent will not be nil for top-level items, it will instead be pointing at the TMainMenu.Items property.

Again, appA MUST use startActivityForResult() in order to receive TMessageReceivedNotification with the result from appB.

I would suggest making the Action hold a pointer to the desired Form, and simply read the Form's current Name whenever needed. And if the Form's Name changes, then have the Form notify any Action that is pointing at it so they can use the new Name as needed. Easy to do if Actions register themselves with the Form so it can maintain a list of pointers to the Actions.

That code is performing floating-point division. And as Lejos mentioned, floating-point exceptions behave differently in Delphi 12 than they did in earlier versions. https://dalijap.blogspot.com/2023/09/coming-in-delphi-12-disabled-floating.html This is also documented by Embarcadero: https://docwiki.embarcadero.com/RADStudio/Athens/en/What's_New#Disabling_Floating-Point_Exceptions_on_All_Platforms If you want to see a Call Stack at runtime, you have to display it yourself. You can catch the Exception (or use the TApplication(Events).OnException event) and then read the Exception.StackTrace property. However, this requires you to install a 3rd party exception logging library, such as MadExcept or EurekaLog, to populate the trace details. Embarcadero does not provide that functionality. In which case, you may as well use that library's own logging capabilities.

Not natively, no. But I'm sure a 3rd party one exists if you search around.

Are you using C++ or Delphi? Integer division or floating-point division? Can you provide an example that is not working for you?

You are not going to get a notification if you use startActivity(), you need to use startActivityForResult().

Even if you could lookup the database server's IP quickly, there is no guarantee that the database engine is actually running/responding, so you still have to wait for the full connection before you can do anything with the database, and still handle any failure that may occur. So, may as well just do that by itself, and deal with the slowness of reporting a failure (you should probably file a ticket about that).

Without having explicit knowledge of your home network setup, there is simply no way for your app to detect whether you are connected to your home network or not. You could try looking for a connected LAN adapter, but what if you are in a hotel that offers LAN access? You could try looking for a connected Wifi adapter, but most public networks are Wifi. You would need your Wifi's SSID to differentiate between a home Wifi and a public Wifi. I think you are making the issue harder then it needs to be. I would suggest taking out the guesswork completely and simply just provide two options in your program's configuration: - connect to a tcp hostname - local copy only And then make it easy to switch between the two configurations as needed. Perhaps wrap them in profiles and then switch the active profile when you leave home and then come home. Another option would be to just skip the local copy altogether and just always connect to your home database server even when you're on the road. Setup port forwarding on your home router and then register a static DynDNS hostname so you can easily find your router's WAN ip/port from public networks (and for added security, setup a VPN server on your home network and then connect to the VPN when on a public network). This way, you always have access to your database server and can connect to it via its IP or hostname on your private LAN. If you really want to go down this route, then you need to assign a unique static hostname to your database server, and then you can use gethostbyname() (or better, getaddrinfo()) to lookup that hostname whenever you connect to the database. No need to validate the IP prefix. If you connect to the database by hostname instead of by IP, then you don't even need to perform the lookup yourself, as most TCP libraries/database drivers will handle this task for you. But either way, if the hostname fails to resolve, then you are likely not connected to your home network. Done.

Ask the user. The OS only knows whether there is a network connection or not. It doesn't care where the network is located or what it's connected to. That's up to the hardware to deal with. No. And as far as sockets are concerned, there is no difference whatsoever whether you are connected to a wired LAN, or to a Wifi, or a cellular provider, etc. The socket API works the same way. The difference is in how the hardware routes the traffic. Likely because this is not what that API is intended for. What EXACTLY are you trying to accomplish in the first place?

Running a process as an (impersonated) admin user, and running a process in an elevated state, are two different things. Being an admin user does not imply automatic elevation, but an elevation prompt does require an admin user. In any case, perhaps have a look at the CreateProcessWithLogonElevatedW() and CreateProcessWithTokenElevatedW() functions provided in the Elevate DLL of this old CodeProject article: Vista UAC: The Definitive Guide (I think the site is down undergoing a redesign at the moment, though. Maybe you can find another copy of the DLL elsewhere).

You are catching the FORM'S paint event, not the BUTTON'S paint event. Every window receives its own painting messages (WM_PAINT, WM_DRAWITEM, etc). Your code can be simplified a little. If you use the button's WindowProc property, you won't need to call GetWindowLongPtr() directly (and even then, SetWindowSubclass() would have been a better choice). Also, since your DrawColoredTxt() function is completely erasing the button and drawing it yourself, there is no point in calling the default paint handler at all. Try this: ... procedure DrawColoredTxt(aBtn: TButton; aCaption: string); private FOriginalButtonProc: TWndMethod; procedure ButtonWndProc(var Message: TMessage); ... procedure TForm1.DrawColoredTxt(aBtn: TButton; aCaption: string); begin ... end; procedure TForm1.ButtonWndProc(var Message: TMessage); var PS: TPaintStruct; begin case Message.Msg of WM_PAINT: begin BeginPaint(Button2.Handle, PS); try FOriginalButtonProc(Message); DrawColoredTxt(Button2, 'Admin'); finally EndPaint(Button2.Handle, PS); end; end; // Forward all other messages to original handler else FOriginalButtonProc(Message); end; end; procedure TForm1.Button1Click(Sender: TObject); begin FOriginalButtonProc := Button2.WindowProc; Button2.WindowProc := ButtonWndProc; Button2.Repaint; end; procedure TForm1.Button3Click(Sender: TObject); begin if Assigned(FOriginalButtonProc) then begin Button2.WindowProc := FOriginalButtonProc; FOriginalButtonProc := nil; end; Button2.Caption := 'Admin'; Button2.Repaint; end; But, that being said, since you are drawing the entire button anyway, you may as well just use the BS_OWNERDRAW style and handle the WM_DRAWITEM message, as explained earlier in this discussion thread.

That is because you are drawing outside of a painting event. As soon as the button gets repainted for any reason, your drawing is lost. This is why you must owner-draw the button so that any custom drawing can be persisted across multiple paint events.

I don't think you need to call WsocketErrorDesc() as ESocketException also has an ErrorMessage property.

Have you tried calling WSAGetLastError() directly? At the point where OnError is called, the last socket error code might not have been overwritten yet. The error code is stored in the raised ESocketException in its ErrorCode property. Sounds like a bug that should be reported to the ICS author.