Odd stripey artifact in my pulgin's output

Hey everybody,
I've been experiencing an unpleasant bug in many of my plugins where I get an unpleasant stripey artifact in the output.
This happens in my plugins which involove several PF_ITERATE steps and some fast blurring. What it looks like is for certain rows of the image, an operation or two is skipped and not applied to those pixels.
It tends to happen when we're changing the value of a parameter with a slider or some such control and After Effects is rushing to complete the operations and something gets dropped at some point. These artifacts tend to go away when I turn the effect off and back on again but I'm not confident that it won't keep cropping up. Has anyone seen this type of behavior? Anyone hava an explanation/solution?
Any help is appreciated!
P.S. I'll try and post some screenshots later...

Hey everybody, I fixed my own problem!!
Here's what happened:
I was screwing up my PF_Err flag.
I had multiple calls to PF_ITERATE and each one was like:
err = PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction1, output_worldP);
err = PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction2, output_worldP);
err = PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction3, output_worldP);
so each call overwrote err, thereby blocking any previous errors from getting through.
I rewrote it like:
ERR(PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction1, output_worldP));
ERR(PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction2, output_worldP));
ERR(PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, myFunction3, output_worldP));
and everything was better.
Here's what I think was happening under the hood:
The stripes would show up when one changed parameter values quickly, like moving a slider fast back and forth. This would interrupt the rendering which would result in a error that if properly caught would tell AE to not display this frame, it didn't get finished properly. Well I was screwing up that error reporting so AE was displaying interrupted frames which looked like crap.
This was clearly a rookie mistake which I made by blindly copying code form an example without properly understading how it should work. Alas....
                    ERR(PF_ITERATE(0, height, input_worldP, &input_worldP->extent_hint,
                                     &si, generateSkinIsolationMatteDemo8, output_worldP));

Similar Messages

  • Aperture 3.0.3, odd visual artifacts?

    Looks like a memory issue or something with the video card? Regardless, after upgrading to 3.0.3 I get to see these artifacts fairly often. At times they're rainbow-colored stripes, other times just black rectangles that randomly populate part of the image. Happens both in full-screen and regular mode. See screenshot:
    http://www.materialized.com/temp/a303.jpg
    Are there any solutions to this other than waiting for another update?

    Hi,
    There are many threads/posts on this forum dedicated to this very issue. This is related to a software incompatibility between Snow Leopard and some graphic cards (mainly ATI).
    Try this - un-tick the crop adjustment, then tick it again. It worked for me. In most cases.
    And provide feedback to Apple describing the issue. Hopefully they'll fix it someday.

  • Odd pixel artifacts

    recently had this show up on my display
    http://prolix21.googlepages.com/macbookpixelissue
    I thought it was a cluster of dead pixels, however.. they move(or disappear) if I change resolution, and if I drag a window or something across them, it will actually create a vapour trail effect.
    Any idea what this is? I don't think its any physical defect, since it moves and I can take a screen shot of it, but I can't get rid of it! They aren't there during the apple boot/splash screen, but once you're in the desktop gui they are there. Change colors depending what window you drag over/under it.

    Unfortunately, those are indicative of bad VRAM. My first MBP had the same problem. It's a very rare, very irritating hardware defect and will necessitate a new logic board... The fact that they disappear if you change resolutions indicates that only a few 'spots' in the memory are bad and if you don't use that memory (i.e. if you lower the color depth) you may not see the error. And yes, on my machine they showed up after I'd had the machine for a while... Apple ended up just giving me a new machine.
    Time for a call to AppleCare or a trip to the Genius Bar. Let them know what the problem is and they should be able to help you.

  • Odd display artifacts, glitch, and freeze

    For the past month, upon starting up my computer after having traveled with it my screen began to glitch, fade, show mutiple colors or go gray to the point of being beyond recognition. I took it to an apple store and they told me that flexing the screen would solve the problem because it was problem with a connection to the panel. This worked for a week or so, but now often upon starting my screen goes gray, flickers, gets glitched, and shows a gray text box that tells me I need to restart. Restart does not help.
    The interesting part however, is that if I hold down the option key while starting to select between OSX or Windows, all of the problems go away. I can start up in osx, no problem. I really have no idea what's going on. Any help would be much appreciated!

    Updated my computer info at the bottom :P

  • Odd artifacts in 32bit comps

    Hi all (mainly Todd),
    I'm experiencing some odd artifacts when using luma mattes in AE CS5.
    If I use a 32bit matte with a 32bit fill, there are some odd "black" artifacts that occur round the fringe of the matte. The AE info panel reports these as having an RGB value of NaN - I've attached an image to demonstrate this:
    I'm using .exr files from R11 of C4D if this makes any difference..
    Cheers
    Dan

    Thanks for the flowers, but I've only recently started to use that sucker again after years of staying away as best as I could (though even then I helped out some friends occasionally) I'm reasonably sure it is an issue in C4D and they are aware of it. I seem to recall that it was "fixed" in one version, but then broke again when they started reworking the render engine in recent versions. I think they're still treating Alpha as 16bit and that seems to conflict with some settings for antialiasing and sampling. Also using some of their render effects like Vector Motion Blur has been known to show this behavior. It's not occurring per se, but seems to be tied to specific combinations of things. Might wanna advise your peopel to chit-chat at NAB about it (and snatch a test license perhaps for investigating?).
    Mylenium

  • Output of files...create PDF File?

    Curious... I have a flat file with .txt extension and I am creating as an attachment. The issue I have is that in Wordpad it looks fine, but in Word or Notepad it looks odd. I need to control the output file but really can't because each user that opens it will have different extensions associated with different programs on their desktop.
    Is there a way to create this as a pdf? Then it would open the same way everywhere. Another solution? Thanks

    Can you clarify what "odd" means? Are we literally talking about a text file or is there some sort of markup (i.e. a rtf file?)?
    While there are a few third-party packages that allow you to generate PDF content from PL/SQL or from a Java stored procedure, that seems like a lot of complexity just to ensure that a text file displays correctly on different computers (and assumes that everyone has a PDF reader). Depending on what "odd" means, I would tend to suspect that there is a simpler answer.
    Justin

  • Playback artifacts with MOV files from GH3

    I have successfully played and edited MOV files from GH3 on this computer, but I suddenly (End of August) started having rendering artifacts in preview, after rendering in the timeline monitor, and on export.  I've tried several different MOV files with the same issue.  I've uninstalled and reinstalled Quicktime.  When I first open quicktime after an installation, it plays the source files cleanly. But after I run Premiere Pro, I can't get clean playback in either PP or QT.  I've disabled the Nvidia Drivers for the GeForve GTX770 video card and still get the artifacts.
    Any ideas about what might be going on?

    Thank you so much for your reply.
    Yes, I have CUDA installed.  I see the artifacts in the source monitor as well as the timeline monitor.  I have tried exporting in several formats and the artifacts appear randomly in all outputs.  I can get a clean export of the same files and projects from my laptop - HP Zbook.
    Quicktime Player also displays the artifacts, but when I uninstall and reinstall Quicktime the display is clear until I try to edit again in Premiere. Then the artifacts start to appear randomly in Quicktime Player as well.
    Windows 7Pro  64bit, Intel i7 3.4 Ghz processor, 16 GB Ram, Nividia GEForce GTX 770 video card.
    Screengrabs:

  • Apple Mail Graphic Artifacts Bug?

    For starters, I never encountered this issue with Lion.  But when I open Mail 6.0 (most of the time), I receive odd graphical artifacts around the message (especially messages that have graphics (i.e. pictures) on the right.  I took it to Apple and they said it's not my hardware, but a software issue.  Does anyone else have this problem? I'm hoping they fix this bug.  Thanks for any help.
    Here is another person with same issue:
    http://att.macrumors.com/showthread.php?t=1411214

    Hello, after clean installation of OS X 10.8 I got the same problem, still exists after updating to 10.8.1.

  • Odd problems, capacitor related?

    Hi all,
    I have an eMac that was purchased in August 2004 and it has a serial number that falls within the range covered by the Apple recall.
    I haven't had too many problems yet, but last month the eMac froze hard for about a week. I couldn't use it and had to use my iBook instead. It hasn't happened since and I haven't thought about it.
    Tonight I noticed a bunch of odd graphics artifacts on my screen saver. It looked like someone had cut the picture with a razor a bunch of times horizontially. It also affected the text in the OS itself.
    I opened up the back of the eMac and checked the capacitors. The black and bronze one looks fine, but there is a slight bulge at the top. The other one is flat, so I was able to compare the two. It's small, but there's definitely a bulge there.
    I turned the eMac back on and the problems seemed to have vanished.
    Can I take my eMac in even if the problems aren't consistent yet? Can I take it in just because I think I have a bulging capacitor?
    I've read that the logic boards are in short order? Is it true that some people are getting a new iMac out of the deal? What is the best way to go about doing this?

    Hello walker_ep
    I'm sure there are others here that may have a better answer for you but I thought I would reply because I just when thru this on my wife's eMac. Her eMac would experience a lockup from time to time, it wasn't totally dead. We did see the distorted video on most of the lockups. I did the same as you, checked the caps and one was rounded on the end. I took it in, they verified the SN was in the range and said it would be repaired. It took about 6 weeks to get the logic board. It was showing out-of-stock 2 days before it arrived.
    My advice is take it in and have them verify it. I was able to take it back with me and use it while waiting on the part to come it. Other posts about this same subject are saying that Apple is replacing some eMac's with the new iMac. If your problem is releated to the recall then it will be fixed, just may take some time.
    Hope this helps.
    Paul J

  • Graphic Artifacts and display freezing/blacking

    My 15inch MBP, purchased in July of 06, seems to be giving me major problems.
    I'm getting really odd graphics artifacts all the time. It can be as simple as a multicolor line in a window, on the desktop or through an icon. Othertimes its as major as an icon or section of a graphic showing up like its been scrambled and combined with really bright colors. Sometimes it looks like a triangle of a few pixels that have been stretched out.
    All of the issues are related to software, as I can make them go away by changing window size—and they only exist in the window or application. The heat coorelates to how severe the artifacts can get, if I'm about 60˚C I'll notice them more, so as a photographer I keep my fan running when I'm doing important work to avoid the crashes.
    And finally, the computer will crash with little explanation. Not like things timing out and I look mouse function, but things like the entire screen slowly being tinted green, or everything but the mouse seizes up(when this happens, my caps lock button still works, I can move the mouse just fine, but I can't click anything;commands don't work either.) The crashing can happen when I'm working in Photoshop(comp intensive) or if I only have Mail.app open and I happen to click on the finder icon too fast(very simple tasks).
    I have the funds to get this repaired, although I'm confident they will simply replace the logic board and that will not solve my issue—only temporarily put it off another few months.
    I'm waiting for the 10.5.2 update, hoping that will fix something. I have all other updates.
    Any suggestions?

    One thing to try would be to borrow an external display and see if the same artifacts occur on the external display. If so, you might have a graphics chip problem, either with the chip itself or with its attachment to the logic board. If the problem gets worse with heat, it may be that the ball grid array that holds the chip to the logic board is beginning to fail. It sounds like your software requires intense processor usage, which will generate more heat. As the heat builds, the failing ball grid array will work less well and you will get these visual artifacts and freezing and other symptoms.
    You might try one of the laptop coolers with fans to keep your Mac as cool as possible and see if this helps. The other thing to try is to reinstall the OS and see if that helps. If reinstalling the OS does not help, very likely you are dealing with some sort of hardware issue, and very likely they would want to replace the logic board.
    Have you tried running the Apple Hardware Test to see if it happens to show anything?
    Good luck!

  • My new video card shows me a small grey artifact at the bottom edge of the white screen at startup.

    2 months ago I needed a new internal hard drive and a new video card.  For the past months my white start-up screen shows me a small grey artifact that looks somewhat like a floppy disk.  There are other small odd shaped artifacts around the lower corners of the start-up screen.  Should I return my computer to the Apple repair/dealer to replace the video card?

    Shay912 wrote:
    Thank you very much, I was going out of my mind!!!
    Shay
    Your welcome. I hope all is well now. 
    Ciao.

  • Feedback on Outlook 2010 Conversations View

    Outlook 2010 Conversations view is a great idea, but the Beta implementation has a few usability problems which prevent the feature from being successful-- if I had to use the feature in RTM in its current Beta state, I'd probably turn it off. But fixing it seems not too difficult-- there are only a handful of very annoying usability issues I've found so far.  It'd be great to see the issues below addressed in RTM. 
    1) Keyboard Navigation shouldn't cause auto-expansion. When using the keyboard arrow keys to scroll through my inbox, Outlook will auto-expand the selected conversation.  The result is that scrolling with the keyboard is like playing whack-a-mole, with conversations expanding and collapsing seemingly at random.  This prevents effective reading of message titles and auto-previews.  The same thing sometimes happens when I delete a conversation and the following conversation is selected. In either case, you should *never* auto-expand a conversation unless I press ENTER or right-arrow on a selected conversation.  For mouse selection, auto-expansion seems more reasonable since you're not doing mouseclick-mouseclick-mouseclick in sequence like you do from the keyboard when reading and deleting messages.
    2) Converation "From" is confusing. Your "From" field shows any unread senders only, and shows all senders if all messages are unread. I'd expect to see all senders in both cases. What's even worse is when you use auto-preview and the most recent message is already read. In that case, you'll see auto-preview text from the most recent (read) message but see a sender(s) of older messages. You'll see User-X's name as sender of User-Y's AutoPreview text.  Weird!
    3) minor thing: double-click of a collapsed conversation opens the newest message. Once it's expanded, double-click doesn't do anything. It should behave the same in both cases.
    4) If you hit up arrow or down arrow to select a conversation, then quickly hit ENTER to open the top message in the conversation, it doesn't do anything. If you do the same thing but wait one second, before pressing ENTER, it will open the newest message. Behavior should be the same in both cases.
    5) When I use up/down arrow to select a message with auto-preview showing, sometimes the auto-preview will vanish and sometimes it won't. This is really disconcerting since my eyes need to jump upwards several lines to see what just got expanded. If something is there when the thread is collapsed, it should stick around when it's expanded. Oddly, I don't see this behavior for all conversations-- some will stay showing auto-preview, some won't. Perhaps only one-line auto-previews stick around while 2-3 line autopreviews are hidden upon expansion?
    6) When I right-click on a collapsed conversation, I'd expect to see "reply" or "reply-all" options (meaning reply to the topmost message in that conversation) but instead I need to separately select the message to reply to.
    Other than these gripes, I think conversations view is definitely headed in the right direction. Nice work!
    BTW, I already posted this feedback to the Office 2010 blog, but I got no responses there so am posting here so my feedback won't get lost. 
    Justin Grant

    Thanks Diane for the quick reply!  Some follow-up notes:
    1. Cool!  This is exactly the behavior I was looking for. Once I clicked the checkbox in Options, the behavior is much more predictable when using the keyboard.  It's a bummer this setting is not easier to discover.  Seems like this should be the default setting.  Note that there's a display bug when this option is selected-- I sometimes see odd visual artifacts after I collapse a thread with the keyboard, e.g. rectangles which aren't painted correctly or show up as gray boxes.
    2. Nope, you didn't understand correctly. :-)  The problematic scenario is where there are some unread and some read messages in a conversation. In that case, the autopreview text shows for the most recent message in the thread (regardless of whether it's read or not) but the "From" field shows the senders of the unread branches only. The result is you can see a sender of one message showing up above the autopreview text for a totally different message. This is weird. And then once you read the last unread message, all the senders come back in the From field, so reading one message causes From to show 10 senders where before it showed only one. 
    After using it for a while, I like the auto-preview behavior of always showing the most recent message in auto-preview, even if that particular message is read. I also like the behavior of continuing to show auto-preview until all branches of the thread are read. What I don't like is the "From" behavior showing a varying number of senders depending on what's read vs. not. Instead, I'd like to see "From" show all the senders on the thread, in order of recency (most recent branches should show up at the front of From).  Extra credit if unread senders show up bold and read senders unbold, but I'd also be OK with all senders showing up bold if the mixed boldness is too hard.
    3. try double-clicking on the name (the top line) of an expanded conversation. the double-click doesn't do anything. it should collapse the conversation-- the reverse of what happens when you double-click on a collapsed conversation.
    4. doesn't matter now that I have a solution for #1! :-)
    5. not a big deal now that I have a solution for #1.
    6. This was a bad choice for cleanup: reply is the probably most common (after delete!) operation you want to do on a conversation!  Certainly more common than printing or quick steps or the other random things remaining in that context menu. Anyway, thanks for the tip-- I always use right-click for replies, didn't think to use keyboard.
    > FWIW, most people don't like the conversation view.
    Hmmm. Now that I know about the keyboard no-expand setting, I like Conversations a lot more! If the Office folks can fix the From field issue (#2 above), then the feature will be, to me at least, good enough for RTM.
    But assuming these usability quirks get fixed, I really do need this feature.  I get hundreds of messages per day and without Conversations I'd have a much harder time dealing with the incoming load-- this is a feature I've been needing for years. I also really like the ability to see my Sent items on the same Conversation without making a trip to Advanced Find. 
    FWIW, Conversations (assuming the usability issues get addressed) is literally the only feature of Office 2010 that would justify the upgrade price for me.  The other improvements in Outlook and the other Office apps are nice, but Conversations saves me several minutes every day... and that productivity adds up quickly!
    Justin Grant

  • Having a hard time with FF XIII and wine

    Hi there! I'm trying to run Final Fantasy XIII on wine. I installed it through Steam. I've seen this page, but my problems don't seem to be addressed there and I don't know what to do.
    When I run the game from steam, I get no feedback whatsoever. The process is running according to ps, but nothing launches, no sound appears, etc.
    I tried setting my resolution to 720p, which did not change anything. I also tried running FFXIII manually from the Steam install. Running the launcher gives me the launcher window, but it closes and the process exits when I hit "Play". Running FFXIII directly does not have any effect.
    Last edited by SirCmpwn (2014-11-09 04:33:09)

    Lone_Wolf wrote:
    That page is for the retail PC version , not the steam version.
    Have you tried to follow this page :   https://wiki.archlinux.org/index.php/Steam/Wine  ?
    I installed Steam with the instructions on that page, yes. It's just FFXIII that doesn't work, other games are fine. There's no winehq page for the steam version, so the retail version is the next best thing.
    nstgc wrote:Are you launching steam from from a terminal? If so is there any output  that might look odd such as a segmentation fault?
    Output, nothing interesting
    Last edited by SirCmpwn (2014-11-09 15:47:19)

  • What to look for

    Hi,
    I understand that this board is a casualty unit for machines BUT having heard many reports of various faults on the mini from a wide variety of sources and having just ordered one recently(at a nice price) I wondered if there is any thing to look out for in particular.
    Kind regards,becca

    There is always a sense, reading the discussions here, that each and every product is littered with failures and faults regardless of what that product is, and I think if many people read these threads before they made their purchasing decisions, they'd decide not to buy anything at all!
    But the truth is that for the most part, these discussions are relatively quiet given the nature of the casualty unit, and if you consider the volume of sales of these systems, the fact that the vast majority of owners DON'T post here is actually a sign of a healthy product and happy owners rather than the content here being a sign of inherent problems or issues.
    That isn't to say there are no faulty minis and nothing to watch for, because there are always going to be a proportion of units with faults reaching the market and there's always the risk of getting one, but by and large the risk is pretty low.
    Common issues to watch out for are, as said, RAM, where the more you have the better the system runs. It's true of just about every computer, regardless of MacOS or Windows and whichever processor, but it's somewhat more true of Mac minis (and laptops in general too) because MacOS, like Windows, requires temporary storage on the hard drive, and a constantly active virtual memory store. Given that the drives in Mac minis are relatively slow, 'paging' activities creates a performance bottleneck which holds down the performance of the system as a whole. The more RAM you have (1Gb limit on G4 models, 2Gb limit on Intel units) the lower the paging overhead and thus the less the slow drive impacts on the system. On Intel Macs you also have to content with the memory demands of Rosetta, the on-the-fly PPC translator that allows you to run old. legacy, applications. 512Mb RAM is OK for fully native application use, though it still limits the performance of the system for the same reason as above, but where old software that is not Intel native is being used, it causes very poor performance indeed, and in some cases can render the system a little unstable.
    There are also potential issues with displays. The need to use an adaptor with VGA screens can create a 'stack' of connectors on the back that if not secure can leave odd color casts or image distortion. Keep the connectors tight and there's usually no problem. Earlier minis did have issues with some displays, with VGA being washed out or dull and DVI suffering colored static, and the Intel minis are similar, but rather less noticeably so.
    The issue that would concern me the most is that on Intel minis, careless owners (and even service providers) have proven apt at disturbing fan and audio connectors when working inside the case, so if the system you are buying is a used one, test it out to make sure that everything is functional before settling down to get it into full use, and watch for odd fan behavior and for proper audio output if there is any indication the system has been opened.
    Other than that, sit back and enjoy it. These are really extraordinarily powerful systems for their size, and easily outstrip the needs of many users. Most mini users (both G4 and Intel) would, I believe, tell you that they have been extremely happy with their choice of system, and there's no reason you should not be too.

  • Setting private fields from Parent class.

    Hi all, I have what seems to be a weird situation to me.
    Basically I have two classes:
    import java.lang.reflect.Field;
    public class Parent {
         protected void ensureDefaults() {
              Field[] declaredFields = getClass().getDeclaredFields();
              for (Field field : declaredFields) {
                   Object fieldValue = getDefaultValueForType(field.getType());
                   try {
                        System.out.println("defaulting field - name: " + field.getName() + " | this: " + this);
                        field.set(this, fieldValue);
                   } catch (Exception e) {
                        e.printStackTrace();
         private Object getDefaultValueForType(Class<?> type) {
              Object defaultValue = null;
              if (type.isAssignableFrom(String.class)) {
                   defaultValue = "default";
              } else if (type.isAssignableFrom(int.class)) {
                   defaultValue = -100;
              return defaultValue;
    public class Child extends Parent {
         private String name;
         private int age;
         public Child() {
              ensureDefaults();
         public String getName() {
              return name;
         public void setName(String name) {
              this.name = name;
         public int getAge() {
              return age;
         public void setAge(int age) {
              this.age = age;
    // Test Case
    import junit.framework.TestCase;
    public class ChildTest extends TestCase {
         public void testEnsureDefaults() {
              Child child = new Child();
              assertEquals("default", child.getName());
              assertEquals(-100, child.getAge());
    }The odd thing to me is that the output looks like:
    defaulting field - name: name | this: Child@7431b9
    java.lang.IllegalAccessException: Class Parent can not access a member of class Child with modifiers "private"
    ... more exception ...
    defaulting field - name: age | this: Child@7431b9
    java.lang.IllegalAccessException: Class Parent can not access a member of class Child with modifiers "private"
    ... more exception ...
    As you can see, it doesn't like me setting (or getting for that matter - tried that) these fields because they're private. However, if you look it's saying that "this" is a Child, so shouldn't those fields be accessible? Shouldn't ensureDefaults be executed as if it was being called by the Child instance?
    Obviously, I can try to use the accessor methods, but that means creating strings for method names, and then looking for the methods. I'd like to avoid this and it seems to me this should work, no?
    Another odd thing is that if I change the fields in Child to protected, it works fine.
    Also, I'm not sure if this is important (I don't know enough about security managers to know if they're different platform to platform, version to version), I'm on a Mac OSX 10.4.11 and:
    java version "1.5.0_13"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
    Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing)
    Any help with this would be greatly appreciated.
    Thanks,
    Eric

    jschell wrote:
    As you can see, it doesn't like me setting (or getting for that matter - tried that) these fields because they're private.Myself I don't like it because it suggests a design problem which is associated with understanding that although a child is a parent that doesn't mean that a parent is a child.
    I understand that, but I don't see how this actually breaks that. The Child is executing a method that is passed down to it from it's Parent, but it's executing it as itself - by that I mean it's not looking at anything that it can't already look at, or at least I thought it was.
    Shouldn't ensureDefaults be executed as if it was being called by the Child instance?No.Ok, I thought it was. Can you please explain this a bit more, I want to understand it.
    >
    Another odd thing is that if I change the fields in Child to protected, it works fine.If you messed with reflection some more you could get to to work even with private. How exactly? I really don't want to bypass any security measures (by settings accessible or using a different security manager, or anything like that). As I mentioned in my last post, what I want to do really is nothing more than a nice way to have a generic toString or hashCode method, if it's not possible to do it nicely - within java's default constraints, I'd rather not.
    >
    However in general the idiom would still be wrong.I'm moving more towards using beans anyway, so I plan on just calling accessor methods which corrects the "wrong idiom" right?
    Thanks for all the help,
    Eric

Maybe you are looking for