bottomline | PHP manipulation utility-belt that provides support

I want to add 7 custom lines as helper to user.

Like in that picture, I want to add 7 times "div.moveable-line"

Even rotation change, the lines stayed at suitible position => And I want to add them 7 times.

Can we create a line between T1 and B1 (and for the others)?

Or if you have any other solutions, I am open for them as well.

React Moveable - Github

Warpable - StoryBook

Moveable.warpable - Documentation

Here is a demo link

MY COMPONENT

I am creating a school project website and is organizing my files to different folders. From root folder to css, script, etc... This is the structure I made.

But I couldn't access my index page from subpages. If I am to go from index to about us for example:

I am trying to add a bottom line to UITextField ... what am I doing wrong?

I am trying to build an app which has a shedule manager in Python and KivyMD. The first page on the code is where the schedule will be displayed, the other page is were you will add the information. After filling the form on the second page, the dashboard window will be updated and the registered activity information will be added to an MDList widget. The top left MDCard holds the average time of the activities, the top right MDCard holds the amount of activities registered.

The user will have the opportunity to delete a previously registered activity if he/she made a mistake on registration (Swipe MDList items to the right and click the trash-can icon). Of course after deletion the widget values need to be updated. My problem comes when trying to update the average time of the activities: To calculate the average all the amounts are saved into a list, what I want to do is to obtain the index of the item deleted in the MDList. So I can delete the amount accordingly and do an accurate calculation. (Actually I just selected the index to be deleted as 0, so the deleted item will always be the first item in the list.

Python File:

I'm new to Swift programming.I have following UI:

Everytime I click on one of the rows, the line just dissapears and I dont know why. I just discovered that tableView didSelectRowAt gets called everytime a line dissapears.

I have created a small framework that provides a unified API to multiple file systems/APIs (namely Win32, Posix, NFS). Said API is somewhat similar to Posix -- to access a file you need to "open" it providing a hint for intended purpose (r, w or rw). Something like open_file("/abc/log.txt", access::rw).

Supporting Win32 API in this framework gives me a headache due to "declarative" nature of Win32 -- you are supposed to know upfront which operations you plan to perform on given handle and pass related dwDesiredAccess into related (Nt)CreateFile() call. Unfortunately framework has no idea what operation client is going to perform (i.e. change-owner, write-attributes, etc) besides generic r/w/rw hint. And I am not willing to let Win32 concepts to leak into my framework (i.e. I don't like adding dwDesiredAccess equivalent into my open_file()).

Here is what I've tried:

1. MAXIMUM_ALLOWED

Idea: Open related handles with MAXIMUM_ALLOWED -- I'll get everything I could and if some right is missing, related operation (e.g. set_mime()) will simply fail with access denied.

Problems:

• it doesn't work with read-only files or volumes ((Nt)CreateFile() fails with access denied)
• MSDN warns that if defragmentation is in progress on FAT volume -- trying to open a directory this way will fail
• in general it seems that using MAXIMUM_ALLOWED is frowned upon for some reason

2. Reopen object when necessary

Idea: Represent r/w/rw though GENERIC_READ and GENERIC_WRITE and for all operations that require additional access (e.g. delete() requires DELETE) reopen the object with required access.

Problems:

• Reopening object is not cheap
• changes made via second object can be silently overwritten, for example:
  • set_mtime() reopens the file with FILE_WRITE_ATTRIBUTES|SYNCHRONIZE
  • calls NtSetInformationFile(... FileBasicInformation) to update metadata and closes the handle
  • later original handle gets closed, it causes data flush and silently overwrites ModifiedTime previously set by set_mtime()

3. Duplicate handle instead of reopening object

Idea: same as in previous section, but instead of reopening object -- duplicate original handle (asking for new access):

I have a form component which is parent and a show-results component which is child component. I make an a call to an api and I have to use a callback to retrieve the data. In my service layer I make my call:

I keep getting this warning:

I am currently developing an application which has two UILabels inside a Vertical StackView, two UITextFields inside a Vertical StackView, and both of those Vertical StackViews inside one Horizontal StackView as such:

I have constraints put in place. When the application runs on bigger devices such as an iPhone 11, it looks perfect as you can see here:

But if I switch to a smaller device like the iPhone 8 you can see the lines hug the edge of the phone as such:

The way I make the underline for the TextField is by using a class I created called StyledTextField. It looks like this: