Falling victim to a fraudulent crypto site was a devastating experience that left me feeling helpless and financially drained. As a marketing professional based in New York, I thought I was tech-savvy enough to navigate the world of cryptocurrency. However, the allure of quick profits and the complexities of the market blinded me to the risks involved. After investing a significant amount of money, I discovered that the platform was a scam, and my funds had vanished. In the wake of this loss, I found myself grappling with frustration and confusion. I spent countless hours researching ways to recover my lost investment, only to encounter numerous shady firms promising miraculous results. It became clear that while some recovery firms were legitimate, many others were just as fraudulent as the original scam that had deceived me. The experience taught me a hard lesson about the importance of verifying the legitimacy of recovery firms. After an exhaustive search, I stumbled upon Salvage Asset Recovery. Initially skeptical, I took the time to read reviews and gather information about their services. They seemed to have a solid reputation and a track record of successfully helping individuals reclaim their lost assets. My gut told me to give them a chance, so I reached out to their team for assistance. From the very first interaction, I was impressed by their professionalism and knowledge of the crypto landscape. The team took the time to understand my situation in detail and walked me through their recovery process step by step. They provided clear communication, which helped me feel more at ease during such a stressful time. Unlike other firms, Salvage Asset Recovery was transparent about their fees and the expected timeline for recovery, making it easier to manage my expectations. Over the following weeks, I remained in constant contact with them as they diligently worked on my case. Their expertise in navigating the complexities of crypto transactions was evident, and their commitment to helping me recover my funds was unwavering. Finally, after what felt like an eternity, I received the good news: a substantial portion of my investment had been recovered. This has underscored the critical need to verify the legitimacy of recovery firms before entrusting them with sensitive information and finances. While the journey was challenging, Salvage Asset Recovery proved to be a beacon of hope in a tumultuous situation. Their assistance not only helped me recover my funds but also restored my faith in the potential for justice in the often murky waters of cryptocurrency.

Captain WebGenesis is a legitimate crypto recovery company that deals with Crypto scams recovery. Their impressive success rate and experienced team make them a leading provider in the industry, offering both reassurance and reliability for clients facing the challenging task of recovering lost digital assets.

@James-Gallegos It works, Thanks

I have started using Squish relatively recently. It's hard work to get something working robustly but I think I am getting there with the main part of my QML application. One aspect that is causing difficulty is the file dialogs that we use in a few places.

On Windows, I am using FileDialog from QtQuick.Dialogs 1.3, which resolves to a system file dialog. I can't get reliable identifiers for buttons and so on (they seem to shift from run to run) and picking files is very fragile. I can't examine the UI as programmatically as I can in the pure QML code and have to resort to coordinate-based picking of files. This is fragile and makes it harder to factor out common script fragments as I have done for other aspects of our GUI. For some reason I don't recall now I couldn't get the dialog to work by typing in the file name in the text box. It has basically been one problem after another for what is really a small part of our workflow.

I am wondering if anyone has any tips for dealing with file dialogs under Squish. My current thinking is that there isn't actually a lot of point in testing what is essentially a system dialog that I have no control over, so I am considering having a "running under Squish" mode for my application that will just pop up basic text input dialogs, written in pure QML, in place of any file dialogs. Does this sound like a reasonable approach?

Hello @Kamikaza I would like to join your team !

Hi @jsulm, I'm not quite familiar with the build process since I'm quite new to this. I know this link is a Cross Compile tutorial for Raspberry pi 4B, what build configuration should I use instead for the Pi zero 2 w when calling configure? (with native build, considering the pi zero 2 is armv8, cortex-a53, and neon support)? thank you!

@JonB Finally, I chose Qt under Linux, which is convenient for Windows installation environment. Thank you

I had the same goal. I used Docker (Windows 10) and CROPS to run Debian container on Win10 to cross compile.
With a hefty machine (8-12 cores, 32 GB RAM) I am able to cross compile from Win10 to the target (Toradex Colibri) pretty easily

https://docs.yoctoproject.org/dev-manual/start.html#setting-up-to-use-cross-platforms-crops