Braiden

Members
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

0

About Braiden

  • Birthday 01/01/1970

Profile Information

  • Location
    New Zealand
  • Interests
    Techie Basically :D
    VB.net
    Batch Scripting
    Soccer
  1. No, what i mean by "skin-able" is that i can change the whole look of a program as i release it. Not so that you guys can skin it. Adding a skinning feature isnt worth it, as you said, it will just be there so i can change the look of it at will
  2. It doesnt have those features yet, they are being added to new revisions of "X". If i WERE to add right click menu's I will probably release the program separately ( that program being the right-click menu ) which would alleviate the need for this. I could always make a .exe file which will clean out my program, if it ever needs a registry key or two. Actually, when i was making this, i didnt think you needed anything more than Regular Rights to access registry keys, but from what i searched, it generally wants Power User or Administrative Rights. At this particular point, im not too sure how to go about adding something to enable Admin Rights, or Power User for that matter ( i personally think giving Admin powers to a .net application is not all that wise, but power user i can handle ) No such key existing could also mean that i installed it to a pen drive, which I do for College work, so i can run the program anywhere. Paint.Net doesnt need any registry keys to work. Yea, I just notice that the controls dont draw themselves correctly, I will fix that problem tonight. That UI is NOT going to stay, i just threw it together for no real reason. the UI is going to be Skin-able soon ( once i figure out Custom Controls ). But skinning is at best a nuisance, for I would have to handle destroying each custom component ( sides, top & bottom, buttons, etc etc ), and also handle creating it on startup ( whop, there comes the Splash Screen ) I've figured out Late and Early Binding, all i have to do is recreate the menu bar you have in Paint.Net, so it draws correctly, then nullify the actions each plugin tries to acheive. It will have to have a Splash Screen to early bind 100 or so Plug-Ins Anybody want to make a mockup of what you would like a UI to look like? Im open to all suggestions Thanks for the feedback
  3. meh.. its a filecount gltich.. ill clear it up.... it meant to be added to the numbers at the top of a group box, but only the number ended up there
  4. New Version JUST Released, See First post for Details!!!
  5. PDN Plug-In Manager is being Built.... again... Read first post for more Info
  6. Hi guys, i need some help here, what im trying to do i make a silhouette of a person rotate about 45* so that he looks likes hes standing in a different direction. Dont worry about his features looking askew, it is an all black colored picture, black and white bg. Im not sure how i could do this, so any help is appreciated!
  7. Thats great there's going to be a Plugin Manager in 4.xx ( hopefully mine! ) Im also looking at .net .dll decompilation, .dll compilation and a UI for making Effects, in a simplified program, but that sort of complexity is out of my reach, for now atleast! I will also hopefully have a website up and running aswell, so i can have a Frontier for my ventures! Thanks for the support guys and gals!
  8. Actually, building upon what Harold said, You would have to do several things before you can use System.Reflection properly; Build a project with: Splash Screen, No Forms. and also, Read through the \src of PDN, finding all the functions you want. Then, using the Splash screen as a Proxy, Call System.Reflection on the dll's containing the functions you want, e.g. Public effectloader () 'Add a function to check registry key for default installation location If File.Exist(.dll file location as string) = "true" then 'See :*: Dim Effectsapi as New System.Reflection(.dll file location as string) Else End If From that point onwards, you can just call the following code to use functions: Effectsapi.linedraw(Parameters 'Usually a .X, .Y, Color, Width) 'Or Assign a function to an individual variable, to save code space Dim linedraw As New Effectsapi.linedraw(Parameters 'Usually a .X, .Y, Color, Width) 'Then you can simply call: linedraw("50","50","Blue","2") Unfortunately i have had no luck with that, so yea, thats just a possible way of handling it. /=====/ another idea you could look at is using a C++ .dll as a Proxy, by using code from the web, let the .dll handle all the heavy codes ( probably like 10kb of code, but it saves space in the program ) and just call the .dll in namespace. Well, thats my idea anyhow!
  9. Gosh, this is a pain in the butt. Ive fixed the Problem that has arised, but i probably should stress that improper use will throw errors, although im trying to add some error control to this. Ill try my best anyways
  10. No, not yet, because, it assumes your working with single 'Effect' dll's, because those are 'mainly' what are used, although there are probably some that have and need folders. @D3z, Ill see what i can do, but i think your mostly all alone with that problem, ill check that its being compiled under the correct FX, becuase for some strange reason i have found my projects change FX as i add newer code, which may be it. For some reason all functions seem to work for me, ill check over the code, from the looks of that JIT im missing some "=" in an "If" function. Ill see what i can do tonight!
  11. New Revision Version 1.3.5 New Features: -Plugin counting, shows exact numbers of Plugins loaded or available -Low-level Plugin Details ( this is a VERY low-level daignostic of the selected Plugin, but will be improved drastically in the very near future! ) Hopefully late binding can start being nice to me Then i can finish off the Plugin exploring features!
  12. Thanks for the Ups @D3z It does tell you which are installed and which aren't, the left list, happens to be Plugins that aren't installed ( but can be ), and the right list is of the Plugins that are installed ( and can be removed! ) I think ill add a Plugin counter tonight, and try work on some of the more annoying feat's
  13. Im not entirely sure its worth adding the ability to browse for the 'Effects' folder, because, to be truely honest, it would take just as long to copy the plugins, and paste them into the directory manually, so im sorry, but im not going to add the ability to browser for an installation directory, as it does that fine as long as you installed it properly. @Rick, Will PDN 4.0 have a built in plugin manager? Because if it is, how long would the manager be useful to the user's here? Anyways, ill keep adding now things to this project until its not useful anymore!
  14. New Version out now: Paint.Net Plugin Manager 1.3 Bug Fixes: -Fixed Crash when a file existed in Both the Plugins Folder, and the Effects folder New Features: -If you have an older Version of a Plugin installed, and you use the Manager to install a new one, it now deletes the older version, and installs the new one! -Slight code improvements