unravel | WordPress plugin to separate concerns | Content Management System library

edited with a clearer example, and included solution

I'd like to slice an arbitrary dimensional array, where I pin the first n dimensions and keep the remaining dimensions. In addition, I'd like to be able to store the n pinning dimensions in a variable. For example

This didnt work for me. I am scraping the website slider.kz. But when i scrape the website it pulls the html of the main page instead of the specified url. My code

I have a numpy array of shape (samples, sequence_length, number_of_features) e.g. (10000, 1024, 2)

I want to break this down into (10000, 1024, 1) where I am only taking the first feature - what is the most efficient way of doing this with numpy without unravelling the array?

There is a portion of my f90 program that is taking up a significant amount of compute time. I am basically looping through three matrices (of the same size, with dimensions as large as 250-by-250), and trying to make sure values stay bounded within the interval [-1.0, 1.0]. I know that it is best practice to avoid conditionals in loops, but I am having trouble figuring out how to re-write this block of code for optimal performance. Is there a way to "unravel" the loop or use a built-in function of some sort to "vectorize" the conditional statements?

First off all: with regions, I do not mean the region, for which that Window is for (Location on the planet), but rather the Window regions: https://docs.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-createrectrgn

The Operating System: Windows 10
Coding Environment: C \ Win32

To change the shape of a window in Windows, one can use the SetWindowRgn() function. As its second parameter, it takes a Window Region created - for example - with the CreateRectRgn from above and many more.

I am using this function to update the shape of a window up to 10 times per second.
After a few seconds of the program running the SetWindowRgn returns 0, which means that something went wrong.
My first idea was, that one of the paramter was invalid, but I keep track of their state (I check 1 line prior, if their state is valid): The Window Handle is never changed and as far as I know, will never be invalid, until as the window exists/is getting closed (which it doesn't/isn't, even after it returns 0).
The Region Handle is also not invalid, as I (1st) check if it is initialized (To combine a region with another one, the destination Region needs to exists), then (2nd) if it is NULL (which it isn't as well), and then (3rd) if it is a valid Handle (it also is). I Also use GetLastError(), to check, if an Error is set (It is not). The third parameter does not change the outcome.

I then thought, that maybe, even though the Windows Docs say:

In particular, do not delete this region handle. The system deletes the region handle when it no longer needed.

That the Handles are not deleted, and unused handles are piling up in the memory: This is not the case (I checked with a threaded loop, that checks, wether the GetProcessHandleCount() changed or not)

Then I started timing the whole thing, to see, if there are some consistencies, some things, that allways happen before SetWindowRgn returns 0: The Time was not allways the same, but I added a variable to check how many times I use the SetWindowRgn() function: For that specific Window, I am calling this function allways exactly 4993 in Code, but I do have 2 other Windows from the same process, which all in all makes me call this Windows function 4995 times in code.
Imagining, that the CreateWindow functions call this function as well, it might be 4998 calls. After that many, SetWindowRgn() fails for that window. (I am not using it again for the other 2 windows).

The whole thing currently runs in one big thread. I am checking nearly every win32 call, to see if an error occoured (, but sometimes I wish, it would just crash instead :S ).

TL;DR: Windows let's me use SetWindowRgn() only about 5000 times

My Question now is: Is this true? Is there a limit on how often one can use that function? Might it be possible, that all the other regions are cluttered on the graphics device and won't be cleaned, resulting in a memory overflow? (Perhaps somehow flushing could help..) Did I just unravel an undocumented, hardcoded limit? What can I do, to still use SetWindowRgn()?

I appologize if some things may still be unclear and I will clarify, if you ask :), and also thank you for your time and answer!

I've read many previous posts on multithreading in .NET, and tried a number of approaches but I'm struggling to get my specific case and c#.NET code to behave. My code is designed to run long-running processes in the background and report ongoing progress into a log display in my Windows Forms UI and to a progress bar control on the same form. As of right now it's operational, but the UI thread is locking up and the messages don't get pushed to the UI till the background process reaches completion.

For the sake of brevity, I'll summarize the current framework here...

User Interface Form

During initialization, we set the Synchronization context as follows ...

I was attempting to use the threading package in Python 3 and ran into a situation about trailing commas I don't understand.

I've seen variations of this question asked a few times but so far haven't seen any answers that get to the heart of this general case. I have an n-dimensional array of shape [a, b, c, ...] . For some dimension x, I want to look at each sub-array and find the coordinates of the maximum.

For example, say b = 2, and that's the dimension I'm interested in. I want the coordinates of the maximum of [:, 0, :, ...] and [:, 1, :, ...] in the form a_max = [a_max_b0, a_max_b1], c_max = [c_max_b0, c_max_b1], etc.

I've tried to do this by reshaping my input matrix to a 2d array [b, a*c*d*...], using argmax along axis 0, and unraveling the indices, but the output coordinates don't wind up giving the maxima in my dataset. In this case, n = 3 and I'm interested in axis 1.

This is a definition in the Microchip Legato Graphics library. I do not understand what that does. Maybe someone here knows what this is trying to do?

Whilst I write a lot of C, I am not across this type of stuff and I am struggling to port older code to fit in with this library.

Here is the definition of the Macro and related structures in header files.