Modify

Opened 9 years ago

Closed 9 years ago

#1950 closed Feature Request (Rejected)

Add APIConstants.au3 and WinAPIEx.au3 and APIErrors.au3

Reported by: anonymous Owned by:
Milestone: Component: AutoIt
Version: Severity: None
Keywords: winapi Cc:

Description

Please add these files APIConstants.au3, WinAPIEx.au3 and APIErrors.au3 no your next release. This way coders can write they're software more easily.
An other Idea would be merge WinAPIEx and WinAPI which means that only 1 #include is enough.

Attachments (0)

Change History (9)

comment:1 Changed 9 years ago by mvg

You like to have WinAPIEx to be updated only when AutoIt is updated ??? ... Think you did not really gave your request much though. If you setup SciTE4AutoIt3 you can integrate it as a fixed part of your AutoIt coding setup(->GotoForum). Besides its called (WinAPI)Ex for a reason.

comment:2 Changed 9 years ago by TicketCleanup

  • Version Other deleted

Automatic ticket cleanup.

comment:3 follow-up: Changed 9 years ago by anonymous

Idea was that when it's includes with autoit by default as many other UDFs users can more easily find this function.

For example I searched from help _winapi* and didn't find func I needed, then I spent few hours on writing func and then found it was already made in WinApiEx. If it were in autoit by default I would have looked WinAPIEx from help.

comment:4 in reply to: ↑ 3 Changed 9 years ago by mvg

Mmm ... Starting to code something before finishing your search for already available code/UDF's will do that to you.

My view.
Some note about http://www.autoitscript.com/wiki/UDF from the UDF-Help might be a idea (In "User Defined Function Notes" section perhaps.).
From wiki it seems a small leap to forum itself. (although that wiki page might need some updating. WinAPIEx is not in there for example.)

But than again. Maybe WinAPIEx is just the beta part of WinAPI. And its planned to be included at some point anyway.

comment:5 Changed 9 years ago by Zedna

@mvg
I prefer WinAPIEx to be included as standard UDF too.

comment:6 Changed 9 years ago by mvg

@Zedna
Think that looking at, or for, some additional possible separations of the WinAPIEx functions would not be a bad thing before thinking of adding it (like it is) to the standard UDF set. (Like what was done with GDI part)
Having one "humongous!" WinAPI (or WinAPIEx if not added to WinAPI) function list seems less then desirable. (to me at least)

Anyway, apart from any point's that might be made here. Its really up to Yashied(I like) and Dev's(we do).

... Time will tell. ...

comment:7 follow-up: Changed 9 years ago by anonymous

I agree with mvg.

WinAPI and WinAPI should not be merged, WinAPIEx itself is already ballooning towards 2 MBs, and takes a few seconds to load

Separation is needed how ever that occurs.

comment:8 in reply to: ↑ 7 Changed 9 years ago by Zedna

Replying to anonymous:

I agree with mvg.

WinAPI and WinAPI should not be merged, WinAPIEx itself is already ballooning towards 2 MBs, and takes a few seconds to load

Separation is needed how ever that occurs.

You are wrong!

You can use

#AutoIt3Wrapper_run_obfuscator=y
#Obfuscator_parameters=/striponly

for smaller compiled EXE files
no matter how big standard UDFs are.

comment:9 Changed 9 years ago by trancexx

  • Resolution set to Rejected
  • Status changed from new to closed

Please use your head.

Additionally, format of WinAPIEx.au3 is unacceptable.

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Modify Ticket

Action
as closed The ticket will remain with no owner.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.