Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering Canvas for Firemonkey #6

Open
chmichael opened this issue Apr 23, 2018 · 1 comment
Open

Rendering Canvas for Firemonkey #6

chmichael opened this issue Apr 23, 2018 · 1 comment

Comments

@chmichael
Copy link

Hello,
Reading the below article, could you think that you can make any Firemonkey Vulkan Canvas ?
https://parnassus.co/firemonkey-canvas-classes-and-a-bugfix-to-speed-up-your-apps/

Thank you

@Fuehrerstand
Copy link

Hello @BeRo1985 too :)

you can try to compose into a virtual reality. Its nice, very fast and the moment, where i have leaving here a special thanks to BeRo. It maybe 30 years ago, when i played on Turbo Pascal 6.x. My teachers were ever nervously, when seen what i did, while looking my shoulder. And these were no stupids!!!

The good old times, when OOP was a great method to structure dynamic datasets into a static stability and accessing through direct adressable. There followed up the times, when i had other things to do. We had a lot of parties, most of them not in the public. Then i did so, as i'am sleeping for a while. The observation was shocked, as detected, what happens really.

Behind the scene there are 4 different technologies in the scene. The Vulcanics, Nox, Gemini, Asgard. They have their own knowledge and technology. All of it has own rules from top. Its an very very long time alliance. Mid of that are you! Between the humans and the other species sometimes was a magical, that you call as love.

The logical are came the Vulcanics. (Java, Fortran, Cobol)
The emotional came from the Nox. (Pascal)
The aggressiv came with the Gemini. (Mickeys C)
The creativity came from the Asgard. (Assembler)

Each of it haves own limits, own rules, own instructions. In some devices are blocking bits, you not seen BeRo. They are a part of the protection from unwanted accessing. So still use as you like and you will override the lame HAL by the old school through assembler. The homelands are interested too into the privacy of the unseen bits and bytes in front of the paranoid business. I smile again and take a look, whats awaiting you inside the AMD-CPUś. You'll find my signs behind the screen of the mirror. Use microcode to activate my stuff from just a shifted nx bit around themself. Turn down the Latency to 32 and increase CPU-Speed up to the first prime MHz ahead from regular. Do the same the second clock. Turn of the automatic clocking mode. There is a liquid sky. Its quantum operational from CPU and GPU same time. Sorry to the intel-nerds, but intel is outside this point. They failed from design!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants