Sherlock

You mean a mockup. Best way of achieving a "he's not done yet" feeling is to present a mockup in a drawing program such as the "queen" Balsamiq and keep the Delphi implementation hidden from sight. Why are the users snooping around your workplace in the first place? And shouldn't one be addressing the GUI in the final stages of development? But I know where you're coming from. I'm there too. So the second best thing would be to create a shitty looking GUI. I do that through gross misplacement of components, horrid colors and a big fat "MOCKUP" label. But for the more professional approach: https://community.idera.com/developer-tools/b/blog/posts/prototyping-from-vision-to-ux-design Cheers

Finally my 2cts: Using methods like Predecessor (or Successor) to access an index based on the amount of items in a container would just hurt my brain to much. I also would always think that -1 or +1 is faster than calling some method, but then I'm the kind of developer that doe not inspect Delphis libs, I just use them and rely on documentation...a dying breed I know. But know this, all you Delphi RTL and VCL know-it-alls give Embarcadero an excuse to not maintain the online help. Please consider this comment tongue-in-cheek.

As to the issue at hand, I feel your data is not correct. Every city and every country should have a unique ID. In your example, Sao Paolo and Rio de Janeiro have the same ID. As well as California (not a city, btw) and New York (maybe not a city) who both have the same ID. Furthermore you at least need a country_ID in your city table. Better yet, a junction table that references both IDs*. What follows then is quite simple: create a query to select cities for a variable country_ID. Set this variable according to the country_ID selected in the country combo and update the query. Then the city LookupCombo should display the desired result. *: This might seem a little over the top at first glance, but there is a Santa Cruz in at least 15 different countries...

@Isaac Badru: Welcome to our little english Delphi forum. I know it is tough to post in English, especially technical stuff. There are people from all over the world here, and for everyone to profit from all that knowledge we use the common language of Delphi...and English to explain what we try to achieve and what we don't understand or know. Please try sticking to English as there might be a fellow programmer who can't speak Portuguese but is either the absolute expert for the question you are asking or has the same issue and desperately needs help. Google translate or Deepl are adequate tools to help you create your posts in a way anybody can understand, and more importantly can search for using the engine of their choice. You will find that searching for the solution of a programming problem will yield more useful results when the search is done with English key words anyway (or Chinese, but that is a different story), so try to get used to it, and enjoy learning English on the way. I translated above text with https://translate.google.com and with https://www.deepl.com. Which one is better? Google says: Bem-vindo ao nosso pequeno fórum Delphi em inglês. Eu sei que é difícil postar em inglês, especialmente coisas técnicas. Existem pessoas de todo o mundo aqui e, para que todos possam lucrar com todo esse conhecimento, usamos a linguagem comum do Delphi ... e o inglês para explicar o que tentamos alcançar e o que não entendemos ou sabemos. Tente aderir ao inglês, pois pode haver um colega programador que não sabe falar português, mas é o especialista absoluto na pergunta que você está fazendo ou tem o mesmo problema e precisa desesperadamente de ajuda. O Google translate ou Deepl são ferramentas adequadas para ajudá-lo a criar suas postagens de uma maneira que qualquer pessoa possa entender e, mais importante, pode pesquisar usando o mecanismo de sua escolha. Você descobrirá que procurar a solução de um problema de programação produzirá resultados mais úteis quando a pesquisa for feita com palavras-chave em inglês (ou chinês, mas essa é uma história diferente), então tente se acostumar e aproveite o aprendizado Inglês a caminho. Deepl says: Bem-vindo ao nosso pequeno fórum inglês Delphi. Eu sei que é difícil postar em inglês, especialmente coisas técnicas. Há pessoas de todo o mundo aqui, e para que todos beneficiem de todo esse conhecimento usamos a língua comum da Delphi... e o inglês para explicar o que tentamos alcançar e o que não entendemos ou não sabemos. Por favor, tente manter-se fiel ao inglês, pois pode haver um colega programador que não sabe falar português, mas ou é o especialista absoluto para a pergunta que está a fazer ou tem o mesmo problema e precisa desesperadamente de ajuda. Google translate ou Deepl são ferramentas adequadas para o ajudar a criar as suas mensagens de uma forma que qualquer pessoa possa compreender e, mais importante ainda, pode procurar usar o motor da sua escolha. Você vai descobrir que pesquisar pela solução de um problema de programação irá produzir resultados mais úteis quando a pesquisa é feita com palavras-chave em inglês (ou chinês, mas isso é uma história diferente), por isso tente se acostumar, e aproveite para aprender inglês no caminho.

Blasphemy!

MDI is said to be an interface type, Microsoft wants to get rid of. There are lots of people propagating to switch to other models such as TDI. This old SO Q&A should get the message across: https://stackoverflow.com/questions/486020/is-there-still-a-place-for-mdi That said, you could create an issue on https://quality.embarcadero.com

Thank you for the effort!!

I'm pretty sure, that is not what he meant. You will run into real problems once you tackle the last 20%, that is what the rule says. And as a rule, you may try to do the hard part first...but it will always be the last to be finished. Life just sucks that way.

Apple says this: https://forums.developer.apple.com/message/196395#196395 Enjoy

That is what happens to me half the time as well, the other half I'm chiding myself to be more careful next time. Then I forget...

Logging is required now. And of course a nice exception handler like MadExcept or EurekaLog.

@Fr0sT.Brutal

I have the strong feeling, that putting this much thought into that seemingly simple class will lead to "What the hell was I thinking?" sometime in the not so far future. KISS really is my prime directive when it come to software development.

@Fr0sT.Brutal If you have nothing substantial to contribute to a users topic please refrain from posting.

I use TParallel as well, but not to the extent some folks do. And I'm not sitting by meticulously counting CPU cycles either. But I do avoid inline variables - well avoid is a strong word...I ignore them.

So you trust inline variables to work flawlessly and use them wherever you like? You trust the TParallel lib?

That looks pretty cool. I don't know why, but I thought you where on a PC. But still the loading should be possible in a thread, where you can also prepare almost all the objects needed, and in the end just assign them to the main thread (synchronized!)

Load them in a thread, but don't expect speedup unless every single texture is stored on its own hard drive. You should also generate an AnimationBitmap object for each loaded image, and once the thread is done, or it once it needs to be used be used, synchronized assign it to the main thread BitmapListAnimation.

Just load it all at application or scene start. How large can those sprites be? It's a game, you may waste resources, it's kind of being expected anyway.

You either mean management reports or manged records... not sure which. Hmmmmm

Sorry, boss.

Wait a minute. A client should use a random port. Only the server needs fixed ports. So in theory you should be able to open thousands of http.Get in parallel. Do you set your client to use a fixed port as well?

That's me

Well luckily this is not a Cobol forum - no wait, even that will not die (german article on 60 years of Cobol: https://www.heise.de/developer/meldung/60-Jahre-COBOL-Die-Sprache-die-nicht-totzukriegen-ist-4518334.html) Then another surely dead language maybe, let's try Fortran ... oops, not dead (https://www.vortech.nl/en/fortran-is-alive/). TL;DR: Don't make unsustainable claims. 😉

I'm looking forward to a ton of bug fixes and performance improvements, for the IDE, the compiler(s) and the resulting executables. Considering the code name "Denali" is based on a mountain in Alaska a feature freeze could sound likely, but I doubt it. When Delphi Anchorage is finally released it will have some cool new features along with the obligatory cool new bugs... *Sigh*