Closed GoogleCodeExporter closed 9 years ago
Do you have gdiplus, or gdi++? If so, that is causing your error, and I'd
recommend disabling it for ShareXmod, or getting a newer fork of it (e.g.
MacType). If that's not the case, then it's probable that you have a corrupt
configuration. While importing them is ideal, you can't expect developers to do
all the work; try being a bit less lazy. I mean, you already knew it was
configs; it was in one of the three messages you posted -- which, by the way is
also a pain. Detail your problem, and add posts to it if you need to. You don't
need to post three separate issues all for one thing that is the same problem.
To reset your configs, export any FTP account settings, and then delete the
following directories:
%appdata%\ShareX
%appdata%\ShareXmod
%userprofile%\Documents\ShareX
%userprofile%\Documents\ShareXmod
%programfiles%\ShareX
%programfiles%\ShareXmod
Then, re-install fresh from the newest setup file. You should find everything
in working order. Good luck, and let us know (in this issue!) if you have any
further problems, and we'll be happy to try helping you through them.
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 2:27
Issue 79 has been merged into this issue.
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 2:28
What OS are you using?
Original comment by mcored
on 25 Mar 2013 at 2:46
Psst. Jhollish. "What version of the product are you using? On what operating
system?" Just saying.
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 2:50
Using Vista OS, Using the newest one just updated 7.1.272
System.PlatformNotSupportedException: Only supported on Windows 7 or newer.
at MS.WindowsAPICodePack.Internal.CoreHelpers.ThrowIfNotWin7()
at Microsoft.WindowsAPICodePack.Taskbar.TaskbarManager.get_Instance()
at ShareX.MainForm.TaskbarIntegration() in d:\Dev\ShareXmod\trunk\ShareX\Forms\MainForm.cs:line 96
at ShareX.MainForm.AfterShownJobs() in d:\Dev\ShareXmod\trunk\ShareX\Forms\MainForm.cs:line 91
at ShareX.MainForm.MainForm_Shown(Object sender, EventArgs e) in d:\Dev\ShareXmod\trunk\ShareX\Forms\MainForm.cs:line 736
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Form.CallShownEvent()
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
Original comment by jshol...@gmail.com
on 25 Mar 2013 at 2:55
This occurs when an image is attempted to be uploaded to Imageshack.
System.EntryPointNotFoundException: Unable to find an entry point named
'GdipDeleteEffect' in DLL 'gdiplus.dll'.
at GreenshotPlugin.UnmanagedHelpers.GDIplus.GdipDeleteEffect(IntPtr effect)
at GreenshotPlugin.UnmanagedHelpers.GDIplus.ApplyBlur(Bitmap destinationBitmap, Rectangle area, Int32 radius, Boolean expandEdges)
at GreenshotPlugin.Core.ImageHelper.CreateShadow(Image sourceBitmap, Single darkness, Int32 shadowSize, Point shadowOffset, Point& offset, PixelFormat targetPixelformat)
at ShareX.UploadTask.DoBeforeImagePreparedJobs() in d:\Dev\ShareXmod\trunk\ShareX\UploadTask.cs:line 500
at ShareX.UploadTask.DoThreadJob() in d:\Dev\ShareXmod\trunk\ShareX\UploadTask.cs:line 311
at ShareX.UploadTask.ThreadDoWork() in d:\Dev\ShareXmod\trunk\ShareX\UploadTask.cs:line 221
at HelpersLib.ThreadWorker.WorkThread() in d:\Dev\ShareX\trunk\HelpersLib\ThreadWorker.cs:line 61
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Original comment by jshol...@gmail.com
on 25 Mar 2013 at 2:56
Mcored, you not doing a check for OS? :P
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 2:57
Also, jhollis, are you annotating, or just uploading?
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 2:57
just uploading
Original comment by jshol...@gmail.com
on 25 Mar 2013 at 2:58
I have Vista, It should also work in Windows Server 2003 and 2008 shouldn't
it?
Original comment by jshol...@gmail.com
on 25 Mar 2013 at 3:00
Mopsy, I should be able to prevent Vista causing an error with Taskbar
integration, however, the GdiPlus issue seems something out of program's scope.
In Windows 7 it works just fine:
https://dl.dropbox.com/u/25501373/ShareXmod/2013-03/2013-03-25_11-32-47.png
Original comment by mcored
on 25 Mar 2013 at 3:34
Some cursory google searching indicates that Windows 7 has a newer version of
gdiplus.dll than does Vista. If this is the case, this wouldn't work in either
Vista or XP. Why is Greenshot code executing if he's not annotating?
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 3:40
jshollis seems to creating shadow which uses greenshot code.
Original comment by mcored
on 25 Mar 2013 at 5:39
Ah. And greenshot is making a call to gdiplus.dll, and I guess the entry point
isn't there because it's older?
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 5:40
This issue was closed by revision r272.
Original comment by mcored
on 25 Mar 2013 at 11:46
Fixed? It's not working.. I went back to 7.1.250. It's more stable and not a
thing wrong with it. 7.1.272 does not appear to be ready. I still r250 offered
and not r272 so that's good.
Original comment by jshol...@gmail.com
on 25 Mar 2013 at 11:46
Look, can you stop being so god damned rude? You don't even understand what's
happening. No one is going to want to help you if you're just acting slighted
all the time. You're using a free program created by unpaid developers who work
on it in their free time. This program works just fine for us, but we're
looking to make it work well for everyone as a courtesy. One thing we will NOT
do, however, is put up with rude, entitled people, who for some reason think we
owe it to them to fix their issue. You did not pay us for this software or
donate to us for our time, you did not help develop or contribute any code of
your own, you've done nothing but bitch that the program doesn't work on an OS
that you shouldn't be using. Vista is a direct downgrade from 7, and even XP is
better, though soon to be officially unsupported by even Microsoft. Yes, a
mistake way made in the Windows 7 Taskbar integration of 7.1.272, but that
doesn't entitle you to be an ass about it.
Anyhow, mcored posted that it was fixed by r272, or revision 272. Version
7.1.1.272, includes changes from r271 and previous, the 272 coming from the
versioning changes made before compiling it. I don't particularly agree with
doing things this way, but that is currently how they're done. "Fixed" as a
status in issue tracking means that the issue has been fixed in the code as of
the mentioned revision (in this case r272, which, if compiled, would be
versioned as 7.1.1.273), and that once you compile it, or use a version we
compile for you, you can verify that it has been fixed, and then we (or
possibly you, depending on permissions) can change the status to verified, in
that the question asker (you) has verified that it is indeed fixed.
7.1.250 (or revision 249 in terms of code changes) is still the stable,
featured download. However, because of a previous bug report you filed that
should have been fixed, either from changes pushed from ShareX, or mcored's own
work, a development version was compiled to fix yours (among some other
people's) problems. You then tell us if it fixed that, and if it causes a new
issue, you open up a new issue here in the tracker. What you do NOT do is get
belligerent with us as if we owe you some service, or are incompetent in some
way because we fixed your problem, and inadvertently caused another one in the
process -- one that very few users should experience, because no one has any
good reason to be on Vista. They offer free downgrades to XP, and 7 is really
cheap nowadays.
That all said, if you'd like to change your attitude, I'd be happy to compile
the latest changes for you, into a setup that should hopefully solve your issue.
Original comment by mopqu...@gmail.com
on 25 Mar 2013 at 11:59
For a new guy you come with quite the arrogance. You've been barking since you
came in. What a rant. Like I said 250 works and it'll do me fine.
Original comment by jshol...@gmail.com
on 26 Mar 2013 at 12:13
Actually read what I said. You're the arrogant one here. You don't understand
how issue-tracking works, and you're acting incredibly entitled. I'm new to
ShareXmod in terms of coding (though I made the logo, and I've been doing bug
testing for a while, and was even helping with initial features and whatnot
before it came out), and I'm new to C#, but I'm proficient in several other
languages, and certainly not new to coding.
If 250 does fine for you, then close your mouth for once. No one asked for your
attitude. You're clearly entitled, and you're probably used to getting the last
word and generally treating people as lesser than you, but it's not going to
fly with me, and I'm actually demonstrating a great deal of patience with you.
If you keep up this behavior, I'll just delete everything you post from now on.
Original comment by mopqu...@gmail.com
on 26 Mar 2013 at 12:18
Let me reiterate what Mopsy said. What you need to understand is that you are
using free and open source software. You are complaining and your attitude is
as if you have paid for the software and you are not getting the assistance as
you are entitled to. I have to admit that it was a mistake on my part releasing
r272 without committing the source code changes first. Anyway, the fixed means
that future releases will have the fix. It is not so intelligent to think that
after my comment saying it is fixed, the installation you already have gets
automatically fixed. Emailing me saying "what a jerk" doesn't definitely help
us developers to VOLUNTARILY provide support for people like you.
Original comment by mcored
on 26 Mar 2013 at 12:50
Original issue reported on code.google.com by
jshol...@gmail.com
on 25 Mar 2013 at 12:34