#qt6 | Explore Tumblr Posts and Blogs

hydrus · 2 years

Text

Version 500

The first Windows build was broken, if you got that please check again--the links have been updated to a hotfix.

windows

Qt5 zip

Qt6 zip

Qt6 exe

macOS

Qt5 app

Qt6 app

linux

Qt5 tar.gz

Qt6 tar.gz

I had a good week-and-a-bit returning to normal hydrus schedule after my personal issues. There are some important bug fixes, particularly for windows crashes, and some neat updates to tag search logic.

Those who use the Windows Qt5 release will want to perform a 'Clean Install' this week: https://hydrusnetwork.github.io/hydrus/getting_started_installing.html#clean_installs

crashes and bugs

I messed up the new mpv version in v499. My golden rule is to never put out bleeding-edge library updates, but without thinking I gave Windows users a dll from late August. This caused instability for a variety of installs, but thanks to some great reports and user testing, we were able to figure out the problem and solution. I regret I wasn't able to roll out an official fix until now, but I will remember this issue for future--never fold in the latest build of anything.

There are two fixes here. Windows Qt6 users simply get a more stable mpv-2.dll today. You don't have to do anything special, just install as normal and your hydrus should be more stable. Windows Qt5 users will be rolling back to mpv-1.dll, so if you are a Qt5 user who updated to v499, you should perform a 'Clean Install', as here: https://hydrusnetwork.github.io/hydrus/getting_started_installing.html#clean_installs . Just follow the guide and you should be good again, but let me know if you have any trouble!

I also fixed a critical issue that was affecting a couple of users with damaged similar file search trees. If you have had 'similar file tree rebalancing' maintenance that seemed to go on forever before locking up your client, this is now fixed. Some related simple errors when the maintenance routine ran into a damaged or looped tree are also fixed.

The Client API now handles disconnects more gracefully. Some logspam is cleared up, and very slow file and tag searches via API now cancel on disconnect just like in the UI (e.g. when you type a new character in autocomplete tag search, it'll cancel the older slower search and start a newer faster one). If you run a busy Hydrus Companion or another Client API application that really hammers your client, let me know how you get on.

tag search logic

I have updated the tag search logic in two important ways:

- First, if you give a file search a tag that currently has a better sibling (loading up old favourite searches can do this), let's say you enter 'shinji', which would now normally display as 'character:shinji', the database now recognises that this tag has a better sibling and will give you the results as if you had entered 'character:shinji'. Previously, it would give you no results since that tag 'didn't exist' any more. This sounds like a small easy thing to change, but as I peeled this system apart this week, I recognised there were several logical problems and inefficiencies with edge-case sibling search, so I rebuilt the bad parts and cleared several issues up. In any case, sibling tag search = better.

- Second, searching files for the tag 'asuka' will no longer give files that have 'character:asuka'. This 'unnamespaced search tags give all namespaced variants too' rule has been in place since the start of the program, but it has always been awkward to implement, sometimes confusing, and it makes it difficult to search for an unnamespaced tag explicitly. If you would like to search for all namespaced variants of a subtag, please enter '*:asuka', which is now acceptable input.

Note that this does not affect tag lookups. If you type 'rei', you will see 'character:rei' in the result list to choose from. But entering 'rei' will not find files with any namespaced version of the tag.

Wildcards follow the new unnamespaced rule too, now. If you enter 'm*na', you will not get files with 'character:mana'. '*:m*na' will, though, and these 'any namespace' wildcard rules are now supplied as suggestions whenever you enter an unnamespaced wildcard.

other highlights

You can now fully edit tag, namespace, and wildcard search predicates. Either shift+double-click some active tag search predicates, or right-click and select 'edit', and you can now change their text. You can also convert between one or another just by typing.

Thanks to a user, the 'pattern' you use when declaring export filenames now supports '{#}', which will give you the same as the incrementing number '#' column in the manual export dialog. You can now export files and give them a filename based on their current thumbnail order.

full list

crashes:

I messed the mpv update up in v499. my golden rule is never to put out bleeding-edge library updates, but without thinking I gave everyone a dll from late august. it turns out this thing was pretty crashy, and many users were getting other unusual behaviour as well. it seems like people on very new versions of Windows were mostly ok, but a little instability, whereas some older-Windows users were unable to start the client or could boot but couldn't load mpv at all. these latter cases were plagued with other problems. thanks to user help, we discovered it was the newer mpv dll causing all the problems, and an older one, from early May, seems to be fine

so, I am rolling back the mpv in the windows releases. the 'v3' 2022-08-29 I bundled in 499 was causing several users serious problems, possibly because of the advanced 'v3' chipset instructions or related advanced compiler tech. for the Qt6 release, we are going back to 2022-05-01, which several users report as stable, and for the Qt5 we are rolling back to the 498 version, 2021-02-28, which is back to mpv-1.dll. Since Qt5 users are increasingly going to be Win 7, we'll go super safe. THEREFORE, Qt5 extract users will want to perform a clean install this week: https://hydrusnetwork.github.io/hydrus/getting_started_installing.html#clean_installs

(you can alternately just delete the now-surplus mpv-2.dll in your install directory, but a full clean install is good to do from time to time, so may as well)

updated the sqlite dll in the windows release to 2022-05, and the exe in the db directory to 2022-09

rewrote how some internal MPV events are signalled to Qt. they now have their own clean custom event types rather than piggy-backing on some bad old hydrus pubsub code

I either fixed a rare boot crash related to the popup messaging system, maybe exclusively on macOS, or I improved it and we'll get a richer error now

tag sibling search:

if you search explicitly for a tag that has a better sibling (one way this can happen is when loading up an old favourite search), the client will now auto-convert that tag to the ideal in the search code and give you results for the siblinged tag

this started off as a predicted five minute thing and spilled out into a multi-hour saga of me realising some tag sibling search code was A) wrong in edge cases and B) slow in edge cases. I have subtly reshaped how core file-tag search works in the client so that it consults each tag service in turn based on its siblings and its mappings, rather than mixing them together. this does not matter for 99.98% of cases, but if you have some weird overlapping siblings across different services, you should now get the correct results. also, some optimisations are more effective, so any instance of searching for tags on small tag services on 'all known tags' is now a bit quicker

big brain: please note the logic here is complex, and I have not yet updated autocomplete counting to handle this situation. if you type 'cat' and get 'cat (3)' from the three 'cat' tags on 'my tags', but 'cat' is siblinged to 'species:feline' on a big service like the PTR, it will still say (3), rather than (403) or whatever from the auto-corrected PTR results. I have a plan to fix this in a future cleanup round

tag subtags and namespace wildcards:

searching for 'samus aran' no longer delivers files that have 'character:samus aran'. the subtag->namespace logic no longer applies. this was a fun idea from the very start of the program, but it was never all that useful as default behaviour and added several headaches, now eliminated. if you wish to perform this search going forward, please enter '*:samus aran', which is now an acceptable wildcard input

tag lookup is unaffected. typing 'samus aran' will still provide 'character:samus aran' as a tag to choose from

a heap of rinky-dink counting logic went along with this, such as providing tag search results like ('character:samus aran (100)', 'samus aran (100-105)'), where it tried to predict how many results would come with the unnamespaced search. this no longer exists, and a decent bit of CPU is now saved in any large tag search

wildcard searching works on similar rules now, so if you enter 'sa*s ar', you will see 'character:samus aran' as a result in the tag list, but searching for it will not give results with 'character:samus aran'. again, enter '*:sa*s ar*' to search for all namespaces (which is now provided as a quick suggestion any time you enter an unnamespaced wildcard), or enter 'character:sa*s ar*' explicitly

'system:tag as number' also now follows similar rules, so if you leave the namespace field blank, it will search unnamespaced numbers. it now supports namespace wildcards, so you can enter '*' to get the old behaviour. the placeholder text on the namespace input now states this

'system:number of tags' now uses the same UI as 'system:tag as number', where you enter '*' as the namespace to mean all namespaces, rather than checking a box

misc:

all tag, namespace, and wildcard search predicates are now properly editable from the active search box. shift+double-click or select from the right-click menu, and you now get a simple text input alongside any system predicate panels. previously, this would only offer you a button to invert the tag to -tag and _vice versa_. now, you can add or remove the '-' and '*' characters yourself info to freely convert between tags, namespace:anything, and wildcard search predicates (issue #1235)

thanks to a user, you can now add '{#}' to an export filename pattern to get the '#' column in your filename (useful if you want to export files in the order they are currently in on the page)

furthermore, if you delete items from the manual file export window, the '#' column now recalculates itself to stay contiguous and in order (previously, it left gaps)

fixed a bug when deleting siblings on a local tags service. sorry for the trouble!

on manage siblings, when you remove, add, or replace a pair on a local tags service, you will now get a simple 'note' reason informing you more on what is going on. the 'REPLACEMENT:' thing recently added to tag repositories should now work for you too

when a downloader or similar adds files to a page, and you have at least one existing file selected, the status bar now updates correctly

fixed a critical issue that was affecting some users with damaged similar file search trees. when starting similar file search tree rebalancing maintenence, their client would go into an infinite loop and spool the cyclic branch into an ever-growing journal file in their temp directory until their system drive briefly ran out of space. sorry for the trouble, and thank you for the excellent reports that helped to figure this out (issue #1239)

the similar files search tree rebalance maintenance now detects more sorts of damaged trees and handles them gracefully, and the full tree regeneration clears out any damaged maintenance information too

fixed another problem with the tree branch maintenance system when the root was accidentally queued for branch rebalance

when you right-click->copy a wildcard search tag, it now copies the actual wildcard text, not the display text with (wildcard search) over the top

I added ',' to the list of non-decodable characters in the hacky URL Class encoding/decoding routine. sites that use an encoded comma (%_2C) for regular path components or query parameters should now work

a user has fixed a regex parsing problem in the predicate parser for system:hash

OR search predicates now sort their sub-predicates on construction/editing, meaning the label is always of set order, and they can now compare with and hence reliably nullify each other

the manage logins dialog now boots a little taller

the main gui tab bar may look a bit nicer/more appropriate in macOS

updated the help text on gui pages where it talks about overflowing rows of tabs, which auto-scroll even worse in Qt6, hooray

client api:

the client api now handles request disconnects better. the hydrus server code benefits from the same engine improvements

the 'twisted.internet.defer.CancelledError' logspam is cleaned up!

if a client disconnects before a client api autocomplete tag search or a file search is complete, that database job is now cancelled quickly just like when you type new characters in the client UI or stop a slow search

if you are a client api dev, please let me know how this works out IRL. I'm not 100% sure what a 'disconnect' means in this context, but if you want to develope autocomplete quick lookup as the user types, and you have a way clientside to cancel/kill an ongoing request before it is complete, please give it a go and let me know if this all works. cancelled requests don't make a log record right now, but you should see the client's db lock free up instantly. at the very least, I have the proper infrastructure for this now, so I can add more/better 'cancel' hooks as we need them

uninteresting code cleanup:

refactored the file note mapping db code to a new module

refactored the file service pathing db code (this does directory structures and multihashes for ipfs) to a new module

refactored some tag display, tag filtering, and tag autocomplete calls down to appropriate db modules

refactored and extended some tag sibling database methods and names to clarify whether they were working with ids or strings

next week

I was not able to get to many things I wanted to this week. Things have piled up, so I'm just a bit buried right now. I will just continue working on urgent issues and smaller issues and see how we are on the crashing.

I'm stressed about my Dad, more than anything because there has just been a ton of energy-draining stuff to do, but not as upset as I thought. As I said before, we had a great relationship, so there are no huge regrets. I'm sure it will kick in more in a couple months. Since the hydrus userbase trends young and my Dad died a bit early, I don't expect many of you have organised a funeral. My serious advice is A) talk to your parents now about what they want in a funeral, and B) make sure they have a will. We were good on both fronts, and it has made the whole thing so much easier. Almost all children bury their parents, so get it done now, while it is easy.

As for hydrus, getting out 500 versions is pretty cool. I've been at this for ten years, and the codebase is now 10 MB over almost 300 files. I still enjoy working on it, and I want to keep at it as long as there is interesting stuff to do. The hydrus userbase has grown significantly this year, and my todo list is overflowing more than ever, so running short on work is not a worry. Handling stress and burnout has been tricky at times, but assuming I stay healthy on that front, I can comfortably see 750 in the distance. Let's see what machine learning does to us all over the next five years.

Thanks everyone!

#release

2 notes · View notes

haomeiconcretebatchingplant · 3 months

Text

Concrete Block Moulding Machine

Concrete block moulding machine QT series adopts German technology, with high efficiency, practical, reliable quality and so on. The main products models of concrete block molding machine are QT4-15, QT6-15, QT8-15, QT10-15, QT12-15, QT16-15, etc., the most suitable for the production of fly ash, shale, coal gangue, ceramic, sand, slag, cement, construction waste and other raw materials, the production of a variety of specifications of free-burning bricks, hollow blocks and other products.

When searching on the market, there are many concrete block moulding machine manufacturers and products, to ensure the normal and stable working condition, we should buy high quality concrete block molding machine, then how can we choose high quality block making machine? High quality concrete block molding machine should usually meet the following standards: 1.Production capacity: With stable production capacity, able to meet the requirements of concrete block production needed for the project. 2.Molding precision: Able to ensure the size precision and shape consistency of the concrete blocks, and make sure the joints between the blocks are close. 3.Degree of automation: With a certain degree of automation, easy to operate and reduce manual labor intensity. 4.Durability: The concrete block moulding machine equipment has a solid structure, excellent quality of parts and components, and has a long service life. 5.Safety: Equipment operation is safe and reliable, with the necessary safety protection devices. 6.Convenient maintenance: The concrete block molding machine equipment is easy to maintain, easy to carry out routine maintenance and maintenance work. 7.Environmental protection: Meet the requirements of environmental protection, no pollution in the production process, in line with relevant national standards and regulations. Choosing a high-quality concrete block molding machine can ensure the production of high-quality blocks and improve the quality and efficiency of the project. When purchasing the concrete block moulding machine equipment, it is recommended to choose products produced by regular manufacturers and pay attention to the performance parameters and warranty service of the equipment.

This resource is from http://www.haomeibatchplant.com/news/concrete-block-moulding-machine.html Should you be interested in buying our product, please contact us at: Haomei Machinery Equipment Co.,ltd Whatsapp/Wechat: 0086 181 3788 9531 Email: [email protected]

#concrete brick machine #concrete block machine #block making machine

0 notes

nazionlinux · 4 months

Text

Void Linux è arrivato Plasma 6

Da poco entrato nei depositi di Void Linux il nuovo ambiente grafico di KDE basato sulle librerie Qt6. Plasma 6 porta molte novità ed un miglioramente delle sue prestazioni: 200% più veloce nella ricerca tra i documenti recenti 60% più veloce nella ricerca di un’applicazione 30% in meno di cicli di CPU Il pannello come impostazione predefinita è mobile, ma è sempre possibile impostarlo come…

View On WordPress

0 notes

dkplayer · 6 months

Photo

Выпущен GOverlay 1.1.1 менеджер MangoHud

В GOverlay 1.1.1 приложение перевели на использование библиотек QT6, а так же исправили другие ошибки.

https://www.gamebuntu.ru/news/vypuschen-goverlay-1-1-1-menedzher-mangohud/

#mangohud #обновление #утилиты #Новости

0 notes

linyiraytone · 1 year

Text

Boost Your Business with QT6-15 Automatic Cement Block-Making Machine

QT6-15 automatic cement block-making machine is capable of producing high-quality cement blocks and paver bricks quickly and efficiently With advanced technology. Its automated operation ensures consistency and precision, reducing the risk of defects and errors. Order now QT6-15 and take your business to the next level!

0 notes

adventuresinfpc · 2 years

Text

Menu Conundrums

One of the big problems I am suffering from is:

I am on Linux. Details :

❯ pacman -Q qt6-base qt6-base 6.4.2-1.1

❯ uname -a Linux █ █ █ █ █ █ 6.1.11-1-cachyos #1 SMP PREEMPT_DYNAMIC Thu, 09 Feb 2023 14:06:43 +0000 x86_64 GNU/Linux

I am running the Emerald theme, that looks like this:

If I make a Lazarus application, the menu however looks like this :

The menu is black. It is not legible.

The usual method is to set the ownerDraw property of the menu to be set to true, then something like this:

procedure TForm1.MainMenu1DrawItem(Sender: TObject; ACanvas: TCanvas; ARect: TRect; AState: TOwnerDrawState); begin showMessage('1'); ACanvas.Brush.Color := clBlack; ACanvas.FillRect(ARect); ACanvas.Font.Color := clYellow; ACanvas.TextOut(ARect.Left, ARect.Top, 'TEST'); end; procedure TForm1.MenuItem1DrawItem(Sender: TObject; ACanvas: TCanvas; ARect: TRect; AState: TOwnerDrawState); var s: string; begin showMessage('2'); ACanvas.Brush.Color := clBlack; ACanvas.FillRect(ARect); ACanvas.Font.Color := clYellow; ACanvas.TextOut(ARect.Left, ARect.Top, TMenuItem(Sender).Caption); end;

But in my case, this did not work. In Windows, there is the doDrawItem call, but not on linux.

So one thing I gotta do is: create my own Menu Widget.

0 notes

gainintech · 2 years

Photo

Warm Greetings from Gain In Technology- Bangalore, IN.

We are supporting SAP Real-Time Online Training with Industrial Experts who have min 8 yrs of experience.

Find below to get more details about SAP TM (Transport Management) Training

Module: SAP TM (Transport Management)

Duration: 25 to 30 hrs

Batch : Depends on Consultant availability

Meeting Software: GoToMeeting

Materials: Daily Class recording, Trainer hands-on Document.

Server Access: 3 Months

We are starting a new batch on the SAP TM if anyone interested please Contact us on

Mobile/Whatsapp: 9606239101

Mail: [email protected]

Weblink: https://lnkd.in/g3Zf-qt6

#sap #saponlinetraining #onlinetraining #onlinecourse #saptm #transportmanagement #ewm #wm #mm #logistics #Bangalore #Hyderabad #Chennai #Pune #india #training #experience #management #transport

0 notes

hydrus · 1 year

Text

Version 527

https://www.youtube.com/shorts/xK5SJ6CuezY

windows

zip

exe

macOS

app

linux

tar.gz

I had a good week working on important updates to the build and a new media player prototype.

This build has special update instructions! All users who update from 526 or earlier to 527 or later will have to do this once!

full changelog

build update

A couple of weeks ago, I tried updating OpenCV (our image library) for everyone, but it caused a dll conflict and the program wouldn't boot. I am trying again this week, and since we have to do this change, I am also rolling in a long-planned change to the main exectuable names. 'client' is now 'hydrus_client' and 'server' is now 'hydrus_server'. Some users will have to do a 'clean install', and most will have to update their shortcuts or launch scripts.

As always--but particularly this week--please make a backup before you update. The following instructions are simple, but if anything goes wrong, you can always roll back to a safe backup.

Ok, the instructions, by situation, are:

- If you use the Windows installer, update as normal. It will do the clean install for you. Your start menu 'hydrus client' shortcut should also be overwritten with one to the new executable, but if you use a custom shortcut, you will need to update that yourself.

- If you use one of the normal extract builds, do a clean install. You also need to update any program shortcuts.

- If you use the macOS app, there are no special instructions. Update as normal.

- If you run from source, git pull as normal. If you haven't already, feel free to run setup_venv again to get the new OpenCV. Update any custom launch scripts to point at the new hydrus_client.py file.

A 'clean install' is as here: https://hydrusnetwork.github.io/hydrus/getting_started_installing.html#clean_installs -- You are basically going to be deleting everything except your database (to clear out old dll files) and then updating as normal.

To update your shortcut or launch script, simply edit it, and where it says 'install_dir\client.exe', just rename it to 'install_dir\hydrus_client.exe'. For Linux users, that'll be 'install_dir/client'.

If you have a custom firewall rule for the Client API, you'll need to update it for the new executable name too.

And that's it! Let me know if you have any trouble.

QMediaPlayer

This is for advanced users only. Also only users who run from source and use Qt6!

I integrated Qt's built-in media player this week. I hope that in future it may be a fallback for users who cannot run mpv. Unfortunately, while it worked surprisingly well when it worked, it was also very crashy. I've got it stable when running from source, but it seems to insta-crash when in a build, so that's something to figure out later.

If you are an advanced user who runs Qt6 from source, you will now see the new experimental Qt Media Player as a selectable viewer under options->media for audio, animations, and video. It has a number of limitations (check the changelog for the full list), but it does work in most cases. Have a play with it and let me know how you get on.

next week

This week was a lot of work for what felt like little outcome. I was disappointed that QMediaPlayer crashed in the build. In any case, I'm short on getting small things done, so I'll return to that. Just some little fixes and quality of life.

I am taking my vacation week on the 8-14th of June, so I have four releases left before then. I won't go for anything huge, but try, if I can, to tie up some loose ends.

#release

1 note · View note

techvandaag · 4 months

Text

qBittorrent 4.6.5

Versie 4.6.5 van qBittorrent is verschenen. Deze opensourcetorrentclient heeft versies voor Windows, Linux en macOS. Het programma wordt met Qt ontwikkeld en is gebaseerd op libtorrent (rasterbar) en Boost. Het programma is het geesteskind van de Fransman Christophe Dumez, die er sinds begin 2006 aan werkt. Tegenwoordig wordt het door de community onderhouden. Er zijn twee downloads beschikbaar. De ene bevat libtorrent 1.2, de andere versie 2.0. Voor de gebruikersinterface wordt van Qt6 gebruikgemaakt, wat betekent dat het niet langer op Windows 7 en 8 draait. De changelog voor deze uitgave kan hieronder worden gevonden. Fixed: http://dlvr.it/T7RWrq

0 notes

haomeiconcretebatchingplant · 6 months

Text

Supplier of CHB Machine in the Philippines

There are many supplier of chb machine in the philippines, and each of them has its unique technology and models. In the Philippines, Haomei chb machine cover large part of market, below are the technical features of some mainstream chb machine manufacturers as well as the introduction of common models: Technical features of supplier of chb machine in the philippines: High degree of automation: Modern chb machine manufacturers generally adopt advanced automation control system to realize the automation and intelligence of the production process and improve the production efficiency and product quality. High molding precision: CHB machine manufacturers in the Philippines focus on the development of high-precision molding technology, which makes the brick size accurate and regular shape to meet the market demand. Energy saving and environmental protection: Concrete hollow block machine manufacturers focus on energy saving and environmental protection in product design, adopting low energy consumption and low emission production process to reduce the impact on the environment.

Common type of block making machine: Fully automatic block making machine: These block machines are characterized by a high degree of automation, capable of continuously and efficiently producing bricks of various specifications. Common models include QT4-15 and QT12-15. Cement block machine: Mainly used for producing cement bricks, characterized by stable structure and easy operation. The common models are QT6-15 type and so on. No-burning brick machine: Adopting special molding process, it can produce high-strength and high-density bricks without burning. Common models are QT6-15C, this model adopts table vibration and hydraulic molding method, which makes the bricks denser and is suitable for producing retaining walls, concrete blocks, standard bricks and so on. Liquid pressure brick machine: It works by hydraulic transmission principle, which has the advantages of high pressure and good molding effect. The common models are QT10-15A, whose molds, axle pins and other series of parts have gone through many kinds of heat treatment process, with long service life, and can be used for the production of dense blocks. In addition, there are also chb maker machines for different purposes, such as hollow brick machine, permeable brick machine, berm brick machine, curbstone brick machine, etc. Each model has its specific application scenario and technical characteristics. It should be noted that the technology and models of different supplier of chb machine in the philippines may have certain differences, therefore, when choosing a concrete hollow block making machine, you need to make comprehensive consideration according to your production needs, budget and market conditions and other factors. At the same time, it is also recommended to visit the manufacturer to understand its production scale, technical strength and after-sales service, etc., in order to ensure the purchase of reliable quality and stable performance of block making machine equipment.

This resource is from http://www.haomeibatchplant.com/news/supplier-of-chb-machine-philippines.html Should you be interested in buying our product, please contact us at: Haomei Machinery Equipment Co.,ltd Whatsapp/Wechat: 0086 181 3788 9531 Email: [email protected]

#brick machine #brick making machine

0 notes