Exactly the same happened to me, when I named my .bat file shutdown.bat :) and was calling shutdown from that file causing an infinite loop

you're a dick. i was born and raised in southern california. lived there for 24 years and the place is a shit hole...so blow it out your ass. [ Don't do today what can be done tomorrow!! ;) ]

Yes, perfect! I only need an indexer, so the Interface would be nice and light. Thanks again Luc!

This will be added cheers, Chris Maunder CodeProject.com : C++ MVP

Everything that is in the designer is in the code. If your using VS2003 then check out the "Windows Form Designer generated code" region. If your using VS2005 then check out the yourform.Desginer.cs file

Hi Phil, two ideas: 1. the DroppedDown property manipulation should not be there at all; it is not needed to swap frame names; if your app needs it, put it elsewhere (or modify your method name) 2. you might want to use SelectedItem instead of SelectedIndex; this should even work if the selected index is different from oldIndex/newIndex; it will fail if your ComboBox holds duplicates (not a good idea anyhow) private static void SwapFrameNames(ComboBox cb, int oldIndex, int newIndex) { // remember current selection object sel=cb.SelectedItem; // unselect everything cb.SelectedItem=null; // swap object temp = cb.Items[newIndex]; cb.Items[newIndex] = cb.Items[oldIndex]; cb.Items[oldIndex] = temp; // restore selection if any (was null, so must search index now) cb.SelectedItem=sel; } Hope this helps. :) Luc Pattyn try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] } catch { [Google] }

You're welcome. Luc Pattyn try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] } catch { [Google] }

PhilDanger wrote: benefits of using an absolute path over a relative path? Well they are "absolute". Relative is subject to the Current Directory so it's only as good as a guarantee that it hasn't changed or is not something other than what you expect it to be.

Subtle, yes. I like it. :) ---- Yes, but can you blame them for doing so if that's the only legal way they can hire programmers they want at the rate they can afford? -- Nish on sketchy hiring practices

Sure, twice the memory, and a lot slower if you dont use a pointer... :) Luc Pattyn [My Articles] [Forum Guidelines]

To fix double set, I use the following code: pnlScroll.AutoScroll = false; pnlScroll.HorizontalScroll.Value = some value; pnlScroll.AutoScroll = true;

Hi Phil, the ResizeBegin/End events are new to me; I did most of my work in 1.1 compatible way. And I avoid using PictureBoxes, they are not worth the trouble in my opinion. When a panel suddenly shows/hides one or both scrollbars, naturally that affects the remaining "clientsize". For that reason, I do what you ar doing now, I think, that is having a non-scrolling (but moving) panel inside a scrolling panel. You probably can give your panel a ResizeBegin/End functionality by hooking them to the form; so you could disable your panel resize logic while the form is between ResizeBegin and End (unless you want ways to resize the panel without resizing the form...). BTW, I read in the doc that ResizeBegin/End also fires when you MOVE the form. Cheers. Luc Pattyn [My Articles] [Forum Guidelines]