David Heffernan

These things are determined at compile time. You can't declare either at run time. So why do you feel this a run time issue? 

FWIW, I have always installed Delphi, even as far back as D6 under program files. Once Vista and UAC arrived, I recall having to add a couple of permissive ACLs onto a couple of files, but it was pretty trivial. And had the benefit of keeping my machine nice and tidy.

I understand that people have different preferences, but I just wanted to point out that installing under program files is not as terrifying as it can be made out.

37 minutes ago, Lars Fosdal said:

Windows 7 was released in 2009, and Delphi 7 was released in 2007.  I guess it was not Windows 7 ready/aware.

UAC, virtualization, etc. was introduced with Vista in 2006

Doesn't virtualization take care of all of this? Or does the D7 IDE have an app manifest?

8 hours ago, dummzeuch said:

D7 writes to its installation directory

What does it write there? 

2 minutes ago, Fr0sT.Brutal said:

Yep but I guess it's considered obsolete.

This topic is not about what is considered the right way to handle manifests. It's about tracking down the inclusion of a resource whose origin is not immediately obvious.

4 minutes ago, Fr0sT.Brutal said:

XPman was there in D7 days, now the manifest is included by Project options -> Use runtime themes

XPMan is still there: http://docwiki.embarcadero.com/Libraries/Sydney/en/Vcl.XPMan.TXPManifest

The unit is named XPMan. Search for that. 

You should have all your work in revision control. Then when your drive fails you still have it. Not to mention all the other benefits. 

1 hour ago, Mike Torrettinni said:

This seems to be the winner, so far.

It doesn't need any extra setting up (Funcs arrays, temp variables, ...). I can add as many as I need, and I don't need to change any other expressions (Result := A or B ...).

The simpler Result := Eval(...) or Result = A or B... looked really good in simple examples, but as soon as you have any comments needed or additional conditions, the winner becomes a better choice.

 

Thank you, I really appreciate all suggestions!

You still need comments for future readers. 

It's automatically deleted here. Try setting up a brand new app and check how it behaves there. 

3 hours ago, Edwin Yip said:

But followed this HeidiSQL discussion this approach seems to be too issue-introducing...

I use SHAutoComplete and don't have any issues. 

Why don't you use the native Win32 TEdit but just enable CTRL+BACKSPACE?

Call  

    SHAutoComplete(WindowHandle, SHACF_AUTOAPPEND_FORCE_OFF or SHACF_AUTOSUGGEST_FORCE_OFF);

in an overridden CreateWnd. Use an interposer, or some other mechanism to get this code to run.

16 minutes ago, Stefan Glienke said:

That's why IMultiMap<TKey,TValue> from Spring4d is so cool 

Only cool for the users. Mind-bending if it's your job to implement it!

Also the owned objects are destroyed when items are removed from the dictionary. This is the same ownership model as the classic TObjectList. 

16 hours ago, at3s said:

I'm interesting, if it's possible to call a Fortran function within the Delphi code like libopenblas.dll does?

When you said that I thought you meant that you were not able to call libopenblas from Delphi.  But then you later said that you were doing that.  So I still don't understand that statement.

Notwithstanding, I am sure you will be able to work out which library is best suited to your needs.

1 minute ago, at3s said:

I just trying to check if it's possible to find eigenvalues\eigenvectors using Eigen library so fast as libopenblas.dll does.

I'd be astounded if that was not the case. Eigen has a very good reputation. Certainly for basic matrix arithmetic performance is excellent. And I'd be astonished if it could not match openblas for eigensolves.

1 minute ago, at3s said:

I am as well.

Then I don't know why you asked if it was possible to do something that you were already doing.

14 minutes ago, at3s said:

I geuss the difference is because LAPACK is based on Fortran math.

That isn't it. 

14 minutes ago, at3s said:

And probably one of reason is Fortran is faster in calculations.

Not true. C++ compilers can perform just as well. 

15 minutes ago, at3s said:

The other one could be difference in algorythm as well.

Possible. But I doubt it. I bet you are asking different questions, and not comparing like with like. 

16 minutes ago, at3s said:

I'm interesting, if it's possible to call a Fortran function within the Delphi code like libopenblas.dll does?

Quite simple to call libopenblas from delphi. I do just that. 

OK, I see. We'll, I don't really know. It seems odd because they use the same algorithm as I understand it. I imagine there is a good explanation. But there'd need to be more detail. 

Your lapack call does not calculate eigen vectors. The eigen call does. 

2 hours ago, at3s said:

I've noticed that Eigen::ComplexEigenSolver works much slower for large matrices than LAPACKE_zgeev from OpenBLAS library.

That would be surprising. I wouldn't want to comment without seeing what options you used when calling the functions. 

1 hour ago, Mike Torrettinni said:

Aha, but if each type requires different attribute values, each type has to have it's own attribute. That's how I understand your example and documentation, but have no actual experience with attributes, yet.

Unless all of your enumerated types have the same names, it seems like you'd have to provide names for each type. 

10 minutes ago, Mike Torrettinni said:

Yes, you are right. For a few minutes I was excited about the possibility 🙂

You have misunderstood me. The attribute is independent of the type. Therefore it can be used with any type. 

18 minutes ago, Mike Torrettinni said:

If I have 10 different types, would I still need to defined 10 different Attribute classes:

As you can see from the code, the attribute class is called NamesAttribute and is independent from the type. Otherwise the whole thing would be pointless. 

I do this;

  [Names(
    'Curvature',
    'Bend angle'
  )]
  TPreBendSpecifiedBy = (
    pbsCurvature,
    pbsBendAngle
  );

and then I can write:

Assert(Enum.Name(pbsCurvature) = 'Curvature'))

Of course this requires some library code behind it, but it's pretty convenient.