-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile with specific profile option. #80
Comments
Hmm not sure what "Test" in this context means, but I was meaning something like the ability to pick presets (not a different config settings, but just compile related settings) like in VS you have debug and release options and can configure any other you want to, so something close to that and that would be attached to my current config settings (So all files with this particular config would have my compile configs). |
Both "Build" and "Test" now have a "Build/Test with config..." context menu. So you can choose a config to quickly compile your source with. Such as "Debug" and "Release" configurations in Visual Studio. Debug and Release are just Visual Studio configuration presets anyways. BasicPawn's configs system is pretty much like Visual Studio's, except its global, for every source, since there are no real projects in BasicPawn. Maybe ill drop this entirely and just add a ComboBox for config selection on top of the editor UI for faster switching configs such as Visual Studio does. Ill try to avoid making the settings page more cluttered and confusing. People already get confused how to use configurations haha. You can test the dev build if you want, let me know what you think: |
The main problem here is the amount of clicks you need to do to actually compile lol, and one of the main cases I asked about it was the need in duplicating configs to create debug variation or any other (like skipping some warnings etc.) where I only change compile related settings and everything else is the same, it gets messy really quickly. In VS you can pick preset you want and then all compiling would be on this particular preset (no need to go into 2 submenus etc every time), I guess current config system behaves the same, but the main problem with it is the loading time when you switching it (especially if you want to quickly test on debug or some quick compile with a different compile settings), so I guess having some custom compile only config where you switch it via drop down menu at the top (again like in VS) and then all compiles would be against selected config would be cool to see. |
Yea, but for it to be available on the top and to be config specific (compile preset options I mean), cuz rn you quickly switching configs as I see, so that doesn't eliminate the need in duplicating configs to set different compile options |
BasicPawn is aimed to be more a Notepad++ style of an IDE not Visual Studio. While i do like to have some Visual Studio features in BasicPawn, some can't be just copied 1:1 and require some design changes. |
That's all okay, not gonna ask you to do stuff that is currently impossible or hard to add, I totally understand it :) Then I guess this issue could be closed then? |
Nono keep it open, the config system does still need a little work still :p |
Is it possible to add some sort of customized layout for custom compile options. As an example I have 2 configs, and the only difference in them is that one have DEBUG define added, so If I want to compile in debug mode I would always need to switch profile, which always takes some time, and then after I'm done switch it back. So having some options inside "Build" section, or maybe even a new section, that can be configured by your current profile settings (and maybe here you can pick other compile options while being on one profile) where you can add build options that you would want on this specific profile. So later just clicking that "Custom build" section and picking whatever you configured would speed thing a lot. I'm gonna hope that this is a useful feature to have, and not specific to me :)
The text was updated successfully, but these errors were encountered: