DropIt

[guinness]

You know how we check if the user is using Windows XP [_IsWindowsVersion() = 0] it's exactly the same, icons should be disabled (not showed) when using Classic Mode too.

My advice to test by adding whitespace to the start of the string and you'll understand more of why it won't work.


See the separating line between the icon and text, this is the reason why.

[Lupo73]

OK, thanks!

[guinness]

Does it make sense though?

[Lupo73]

I could directly modify __SetItemImage() and don't add icons in that case.. do you think is a good solution?

[guinness]

For speed do it outside of the function e.g. If IsNotWindowsXP Then __SetItem....(

[Lupo73]

But the included solution is much more compact (I updated SVN).. I don't know, I'd like to have a feedback from Leif and Si3rra..

The second beta release is available for tests:
http://www.lupopensuite.com/files/dropi ... rtable.zip
http://www.lupopensuite.com/files/dropi ... Source.zip

It includes several minor improvements and fixes (Leif helped me to update the program interface and the guide too)

Note that the package includes also the x64 version.. I'd like to know your opinion: if it works and if release separated versions or not..

[guinness]

Why didn't you do this?

Code: Select all

If __IsWindowsVersion() = 0 Or __IsClassicTheme() Then
	Return SetError(1, 0, 0)
EndIf

[si3rra]

This is how it looks now with the new 3.9.

http://www.box.com/s/qug3i5fv1a75xpoa1y9g
Aero vs. Classic

The x32/x64, how about doing a "wrapper" file containing both the 32 and 64 bit executable, a function checks if 64 or 32 and extracts the corrsponding one for use, after 1 use only cheks if the right one exists. (a little like ProcessExplorer)
http://technet.microsoft.com/en-us/sysi ... s/bb896653

[guinness]

You can't embed .swf objects in PhpBB3 forums.

[si3rra]

no and i can't upload images either

[guinness]

Have you tried using TinyPic or LocalHostr?

[tproli]

The x32/x64, how about doing a "wrapper" file containing both the 32 and 64 bit executable

I'm not very keen about it because of the larger file size.

[guinness]

How I do it in ProEject is provide the x32/x64 binaries as well as a wrapper, but honestly Lupo73 I had to re-structure the script because I FileInstall the ProEject_x32.exe & ProEject_x64.exe binaries to a folder called Data and then work from there though appearing to work from where the wrapper was launched .i.e. setting a Global variable $__ScriptDir with the @WorkingDir macro.

I would commit it but right now I'm busy with other projects, sorry.

[Lupo73]

@guinness: you are right no reason.. thanks!

@si3rra: good that the Windows Classic issue is fixed..

And about the x64, let me know if you find particular issues in it.. To distribute x32/x64 I think that the installer version may be unique (I could need your help to modify it, to check the system and extract the correct exe) and instead I could release a unique or two separated packages of the portable version (to reduce the single package size, as recommended by tproli).. your solution guinness is very efficient, but a little complex at the moment..

Merry Christmas!

[guinness]

Lupo73,

I wouldn't be too worried about the x64 build, because all the native AutoIt functions work on x64 without a problem (otherwise I would've reported by now) & we went through the UDF's updating structures & fixing compatibility issues etc... The only time you should be concerned is if you create a DLL call yourself and have to pass a structure using DLLCreateStruct() and just so happen to create an incorrect structure.