Not sure if this is a bug or by design but there is no autocomplete for macros in resident files.
I have a windows res with macros like HIWORD() LOWORD() etc.. and it's a bit of a hassle not having autocomplete for them, it would be nice to have it.
No autocomplete for macros in residents
-
Captn. Jinguji
- User
- Posts: 94
- Joined: Sun Oct 24, 2004 9:25 am
Re: No autocomplete for macros in residents
Uhmmm..... it's there. I seemed to have the same problem.
I have PB5.72 and PB5.71 installed in adjacent paths of the same directory tree - AND I am creating the .res file through a custom entry in my tools menu in both installations.
On closer examination, I found that much to my surprise, lf I alter the entry for "Commandline" in the 5.71 Menu to point to the 5.71 compiler, the corresponding entry in the 5.72 also gets changed to point to the 5.71 compiler (et vice versa) behind my back! (yes. both Menu Items go by the same name).
The target paths to their respective compiler version-specific residents directory in each case is being coonstructed using the %HOME Parameter in the Arguments field in the Menu; thus, the .res file is being (re-)created with the wrong compiler in the (version-wise) "correct" target path, and with that .res-file, autocomplete is no longer working, until I set the correct compiler here, rebuild the res and restart this compiler. Of course, now the other version gets "mangled", but that only becomes obvious once the .res file is recreated succesfully there, which in my case is rare and long between. AND: With two versions of the compiler of the same major version 5.7x, this is really hard to detect on inspection of the Menus;if it were, say, 5.61 and 5.72, it would be more obvious.
You may want to check if your problem arises from a like condition!
I have PB5.72 and PB5.71 installed in adjacent paths of the same directory tree - AND I am creating the .res file through a custom entry in my tools menu in both installations.
On closer examination, I found that much to my surprise, lf I alter the entry for "Commandline" in the 5.71 Menu to point to the 5.71 compiler, the corresponding entry in the 5.72 also gets changed to point to the 5.71 compiler (et vice versa) behind my back! (yes. both Menu Items go by the same name).
The target paths to their respective compiler version-specific residents directory in each case is being coonstructed using the %HOME Parameter in the Arguments field in the Menu; thus, the .res file is being (re-)created with the wrong compiler in the (version-wise) "correct" target path, and with that .res-file, autocomplete is no longer working, until I set the correct compiler here, rebuild the res and restart this compiler. Of course, now the other version gets "mangled", but that only becomes obvious once the .res file is recreated succesfully there, which in my case is rare and long between. AND: With two versions of the compiler of the same major version 5.7x, this is really hard to detect on inspection of the Menus;if it were, say, 5.61 and 5.72, it would be more obvious.
You may want to check if your problem arises from a like condition!
Is this an artifact or should it be disposed of ?
Re: No autocomplete for macros in residents
Confirmed here. I made a test residents file with a constant and a macro, and only the constant name is auto-completed, and not the macro name.Justin wrote:there is no autocomplete for macros in resident files
I only have one version of PureBasic installed, so Captn. Jinguji's comment doesn't apply as the cause.
Re: No autocomplete for macros in residents
I would like to bring up this topic again since I couldn’t find any response in the forum.
Is it a bug that the macros do not appear in the autocomplete list, or is it intentional?
I think this feature would be very useful.
Is it a bug that the macros do not appear in the autocomplete list, or is it intentional?
I think this feature would be very useful.