Messages

Paket maybe? It's intended as Nuget wrapper to avoid certain pitfalls related with NuGet, however it can also be used to download git repos or even files.

I'm sorry guys but as was implied with Crimson Wizard's last post the latest changes were going to be pushed to the master branch of the source code, and now they are. I have now moved on to other tasks and projects that I cannot possibly divert my attention from, making montages of random situations where the icon is showing takes more than I am currently willing to offer of my limited spare time.

I'm honestly a little perplexed that you waited this long to speak, based on what you're saying you've clearly been following this thread, and I wrote this 5-6 days ago.

If anyone wants to see what the icon looks like under specific circumstances I can provide screen shots if they're unable to check out the dev branch themselves.

If anyone wants to see what it looks like, work more on this or make changes, you can download the icon here.

PS: I forgot to thank abstauer and LameNick for their help, so thank you guys. I credited them in the commit message.

LameNick, could you make a copy of ags_cup_screen_06_256x_unmirrored_darker_RGB.png into all the different dimensions?

I think I like the "ags_cup_screen_06_256x_unmirrored_darker_RGB" best personally, that mirroring will probably work better when scaled to smaller dimensions as well I think.

Try this, find and delete the following file on your computer "{MyUser}\AppData\Local\AGS\Layout.xml".

I'm sorry I don't understand what you're saying or what a tilt angle is in this context.

I'm not a designer myself or have any sort of proficiency in anything related to that, so I'll let others weigh in on that. It makes sense however to go with that color as it is closer the AGS logos color scheme.

I did consider the blue outline ones that LameNick provided, but ultimately decided against it as it didn't look good on the smaller icons and I preferred to use the same image for all the sizes, just for sake of simplicity.

If anyone wants to see what the icon looks like under specific circumstances I can provide screen shots if they're unable to check out the dev branch themselves.

Thank you, it looks much better than what I did. I uploaded the changes to PR #397.

This is pretty cool I think.

Spoiler

[close]

I think it might look even better, especially on the smaller icons, if we also had scaled each individual image by vector, but maybe this is too much hassle? I don't know. It probably would be better than the stretch scale that I used when I made the test icon. I would need copies of the file "ags_cuponscreen_256x_v2.png" in the following dimensions.

• 256x256
• 128x128
• 96x96
• 64x64
• 48x48
• 32x32
• 24x24
• 16x16

We're getting somewhere, however, LameNick, can you send me a 256x256 version of the narrowscreen image?

The splash screen looks really cool, so wouldn't including the skewed white screen solve the background problem?

https://www.sendspace.com/file/ljjj37

It would, however it requires additional space in an already cramped environment which would make the icon harder to see. Maybe trim off the sides so that it just covers the cup.

So I was trying to make a new icon for the editor when Crimson Wizard pointed out a potential issue, I was maybe hoping that someone who know Photoshop, GIMP or similar software could help out.

The issue is that the icon is entirely blue, and when it is placed over a blue background it fades in and becomes sort of invisible. Crimson Wizard suggested that adding a white outline to the shape could help, although I suppose a black outline would do the same thing. If anyone wants to try giving it a nicer color or do other edits they're free to do so.

Showcase:

Spoiler

[close]

Problem:

Spoiler

[close]

Image:

Spoiler

[close]

Original:

Spoiler

[close]

Bear in mind these 'people' presumably aren't unique.  So that could just be one XP user who's used AGS often enough to report back multiple times?  Or is it one report per unique machine ID or something, CW?

I'm looking at the code right now and it is set to send a new stat report when a minimum of 30 days has passed since last update.

Shouldn't the 34 people on line 7 also be included, upping the total to 47? Still not a whole lot... Slightly less than 0.7%.

Uhh, that depends.. I can't judge from the table if they're using Service Pack 2 or Service Pack 3 as they seem to have the same version number 5.1.2600, but I guess they should be added at any rate to factor in uncertainty. Like you say it is still a very low percentage so I don't think we should stop upgrading to .NET 4.0 in favor of this minority.

Windows 8.1 and 10 seems to be missing from that list, do we know why that is? I have difficulties believing that no one uses those OS with AGS, I know for a fact I have started up AGS on my Win 10 PC.

So if I'm interpreting these numbers correctly, roughly 13 people maximum will be affected by upgrading .NET to 4.0, that's not really a whole lot of people. These numbers also say nothing about if these people are keeping their AGS up to date, they could be using ages old version of AGS for all we know. Even if they did, they could possibly be persuaded into updating from Service Pack 2 to Service Pack 3.



OMG! There's someone still using Windows 2000 

I just dropped a message in GitHub but I'll copy paste it here

So I've done some more research.. Turns out upgrading to .NET 4.0 may not be a high enough of a upgrade unfortunately, at least if there's going to be any development towards bringing the AGS Editor to *nix systems. The problem is that Mono has dropped support for any compatibility with .NET below minimum v4.5. So if I or anyone else is going to pursue to work I recently began in #396 it is required that we at least upgrade to v4.5, or alternatively v4.6.1 which is the highest supported version by Mono.

By upgrading to v4.6.1 we would lose Windows Vista users(is that a problem? Is there anyone using Vista?) and minimum required VS will be 2015.

By upgrading to v4.6 we would keep the Vista support, however minimum required VS will still be 2015.

By upgrading to v4.5 we would keep the Vista support, however minimum required VS will be 2012.

https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#History
https://msdn.microsoft.com/en-us/library/8z6watww(v=vs.110).aspx

You'll notice on my screenshot that when I attempt to run AGS it tries to circumvent the issue by running the .NET 2.0 application in a default environment, what you can't see on my screenshot is that this freezes the entire OS when it attempts to show the splash screen, so it is stuck on that transparent rectangle.. Updating the framework version resolves the issue.

Spoiler

[close]

The only drawback is that I need to restart AGS in order to detect the changes in the edited files.

You sure about that? When I edit scripts externally with the editor open I get prompted with a dialog saying "The file MyScript.asc has been modified externally. Do you want to reload it?"

Sorry but the work in that thread is purely proof of concept at best, I could never find any time to work further on the topic. It is probably not a worthwhile endeavor to implement at this point anyways as the future of the Editor is uncertain.

I took 1001 Spikes, been wanting to check that out for a while, thanks

E: Or, alternatively, we may have white on on the splash and blue variant as the icons (unless that is too weird).

I think that's a great idea, let's do that.