M
MatthewL019
Guest
It'd be very useful if I could have two projects open at once in the same application instance. E.g server/client, and simply changing between "work space".
Not happening
A flat "no" to a legitimate question where the use case is 100% valid and more than reasonable feature for a serious/pro developer to ask for is pretty poor, if you ask me. Whatever the reason is for not being able to deliver on such a feature request, it really speaks to how able YYG is, and how much GMS2 is ready for serious, professional developer teams to use.Not happening
It was considered very early on in development (as such as thing would be) and it was decided to go with one project per application instance.Why not?
There was nothing at all rude intended, @Jobo. As a customer, I am communicating my clear displeasure at the way you treated a legitimate question with a brusk, dismissive response.@csanyk Your recurring theme of rude posts will only make me ignore what you have to say in the future
It was considered very early on in development (as such as thing would be) and it was decided to go with one project per application instance.
And probably the same from @Jobo too. Just saying "No" or "Not happening" is not "out of line". Blunt, and to the point maybe, but not out of line.There was nothing at all rude intended, @Jobo.
Granted. BUT simply pointing out that alternative would have been worlds better than saying "not happening".And probably the same from @Jobo too. Just saying "No" or "Not happening" is not "out of line". Blunt, and to the point maybe, but not out of line.
I think that it probably isn't going to happen is because it looks like you can do what you could with GM:S 1.x - and have 2 copies of the IDE running at the same time. Use one for the client application, and one for your server. Don't see a problem with not being able to load multiple projects into the one IDE.
He wasn't being rude at all. You, on the other hand...@csanyk Your recurring theme of rude posts will only make me ignore what you have to say in the future
It was considered very early on in development (as such as thing would be) and it was decided to go with one project per application instance.
Thanks for speaking up for me, Samuel. It is appreciated.[redacted by poster's request]
This really should have been your first reply to OP - it's a bit harsh to be be so blunt and dismissive to a genuine question from a user.It was considered very early on in development (as such as thing would be) and it was decided to go with one project per application instance.
It wasn't -- it's not up to me alone to consider suggestions, but this is simply an early design decision that we won't change now. So this was already considered a long time ago.Jobo's reply was blunt and short - almost as if my suggestion wasn't even taken into consideration for a second
Which is the information I was looking for the first time aroundIt wasn't -- it's not up to me alone to consider suggestions, but this is simply an early design decision that we won't change now. So this was already considered a long time ago.