I just installed "Smug MsgLoc" thinking I could use it at some later point, downloaded the source code, compiled and got a bunch of errors. I know you need to enable GPS for this to work, but without using a plugin in a screen, Xcode should be happy with code you aren't using (at least in my opinion) unless there is a real problem with the code. So, I'm wondering what you do in this case? I removed the plugin folder for this plugin from Xocde, so now Xcode is happy, but I'm wondering if you can simply remove a plugin from the control panel to a "unused state" so that it doesn't automatically get added to all future apps and you have to go through the same process again. Cheers

That would be a good feature to have in buzztouch for the future! I'll make sure that suggestion gets moved upwards. But, at the moment, it's not possible. You'll just have to delete the plugin folder in Xcode. Mark

Second that, would be a very useful feature.

Thanks Mark!

What errors are being generated from Smug MsgLoc? Whether you use the plugin or not, you shouldn't be getting errors... Cheers! -- Smug

I can't recall...deleted the plugin folder...try adding all your plugins into a new app, download and compile to see if you get the errors...not sure if it's a conflict with any other plugins...but once I removed the folder for this plugin, Xcode was happy...I'm using the plugins: Menu with Image, RD Simple RSS, HTML Doc, Custom HTML, Quiz (original from David), Weather, AppRater. Hope this helps.

Ok, well. If you do recall let me know. Cheers! -- Smug

I always have to remove the Smug MsgLoc plugin file too. It gives 4 errors. If I remember right I thought you had a fix lined up for the 1.1 version Smug? Here is a screenshot https://dl.dropboxusercontent.com/u/3433634/Screen%20Shot%202013-05-15%20at%2022.46.55.png

I get these. I was going to tell you about them, but since I don't need them for now, I jsut delete the file and it gets out of may way. I get the same problems that LevensGardener get.

I do, I did. Something. I've released v1.1, and it's in the market now. If you haven't updated, it's probably a good idea. But I notice there is still an issue with the naming conventions. I think I'm going to have to release v1.2 keeping the BT naming convention, because it keeps capitalizing the first letter of the filename for iOS. Cheers! -- Smug

@LevensGardner. Thanks...that's what I got. @SmugWimp...I just installed this plugin this afternoon, so it's whatever the current version is...cheers

I'll get busy on it. Cheers! -- Smug

@SmugWimp. You might want to consider removing the plugin altogether until the errors are fixed. Nothing like errors to put a downer on ever using the plugin again:-) Cheers