Hi,
I am playing with Widgetry 1.12 and I encountered a problem related to Grids and scrolling. In the attached parcel, I placed two toy examples for a Finder-like interface: one works with listboxes (ListFinder) and one with grids (GridFinder). Clicking on a number should result in spawning another pane on the right and moving the scrollbar to the right position. "ListFinder open" works just fine and allows you add any number of panes. "GridFinder open" works just until you need to scroll beyond the size of the window. Afterwards, there seems to be something wrong with capturing clicking events. It looks as if scrolling creates some sort of confusion, but I could not figure out what exactly is happening. Does anyone have any hints? Cheers, Doru -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "To lead is not to demand things, it is to make them happen." WidgetryPlayground.zip (4K) Download Attachment |
Tudor,
>Does anyone have any hints? No, but I'll look into it. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
Thanks :)
Doru On Jul 25, 2007, at 7:18 PM, Samuel S. Shuster wrote: > Tudor, > >> Does anyone have any hints? > > No, but I'll look into it. > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using? > -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "What we can governs what we wish." |
In reply to this post by Tudor Girba-3
Tudor,
>Does anyone have any hints? To keep you up to date here. I just got around to looking at the problem, and it is a HUGE BUG! I'm still working on it, and as soon as I have a fix, I'll let you know. It is currently at the top of my task list. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
Hi Sames,
Thanks for letting me know and for working on it. Looking forward for the fix, Doru On Jul 26, 2007, at 9:56 PM, Samuel S. Shuster wrote: > Tudor, > >> Does anyone have any hints? > > To keep you up to date here. I just got around to looking at the > problem, and it > is a HUGE BUG! > > I'm still working on it, and as soon as I have a fix, I'll let you > know. It is > currently at the top of my task list. > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using? > -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "Beauty is where we see it." |
In reply to this post by Tudor Girba-3
Doru:
> >"GridFinder open" works just until you need to scroll beyond the size >of the window. Afterwards, there seems to be something wrong with >capturing clicking events. It looks as if scrolling creates some sort >of confusion, but I could not figure out what exactly is happening. > >Does anyone have any hints? Well, I have a provisional fix for you. The attached is UNREVIEWED and as yet unsupported, but I wanted you to get an early look since you reported the problem. It is considered a Critical bug, and it will be reviewed and supported very soon. Thanks for the report! And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? AR52600.st (5K) Download Attachment |
Hi Sames,
Thanks, that seems to solve the Grid problem. In the meantime I encountered a similar problem that is not solved by the fix. I attached here another parcel in which there is a ListInFormFinder that puts each listbox into a Form instead of directly adding it to the container form. I presume this might show another aspect of the same problem because again if the scroll is passed the visible region, the list does not respond to click events. Cheers, Doru On Jul 30, 2007, at 8:47 PM, Samuel S. Shuster wrote: > Doru: > >> >> "GridFinder open" works just until you need to scroll beyond the size >> of the window. Afterwards, there seems to be something wrong with >> capturing clicking events. It looks as if scrolling creates some sort >> of confusion, but I could not figure out what exactly is happening. >> >> Does anyone have any hints? > > Well, I have a provisional fix for you. The attached is UNREVIEWED > and as yet > unsupported, but I wanted you to get an early look since you > reported the > problem. It is considered a Critical bug, and it will be reviewed > and supported > very soon. > > Thanks for the report! > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using?<AR52600.st> www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "One cannot do more than one can do." WidgetryPlayground2.zip (4K) Download Attachment |
Tudor,
>In the meantime I encountered a similar problem that is not solved by >the fix. I attached here another parcel in which there is a >ListInFormFinder that puts each listbox into a Form instead of >directly adding it to the container form. Thanks. I'll have a look. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
In reply to this post by Tudor Girba-3
Doru,
>In the meantime I encountered a similar problem that is not solved by >the fix. I attached here another parcel in which there is a >ListInFormFinder that puts each listbox into a Form instead of >directly adding it to the container form. > >I presume this might show another aspect of the same problem because >again if the scroll is passed the visible region, the list does not >respond to click events. Wow, you really come up with good ones! I'm right now stuck in a 1/2 solution. I can get the form/list box to react to clicks... but it won't display. Go figure! <sigh> Your problem is at the top of my list, and as soon as I get a fix, I'll let you know. BTW, the fix I sent yesterday did not fully pan out... Attached is an updated fix for that (but not for this). And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? AR52600.st (6K) Download Attachment |
Hi Sames,
>> In the meantime I encountered a similar problem that is not solved by >> the fix. I attached here another parcel in which there is a >> ListInFormFinder that puts each listbox into a Form instead of >> directly adding it to the container form. >> >> I presume this might show another aspect of the same problem because >> again if the scroll is passed the visible region, the list does not >> respond to click events. > > Wow, you really come up with good ones! I am glad I can be of help :). > I'm right now stuck in a 1/2 solution. I can get the form/list box > to react to > clicks... but it won't display. Go figure! <sigh> I got the painting problem for buttons if I also added a button besides the listbox on the forms. > Your problem is at the top of my list, and as soon as I get a fix, > I'll let you > know. Thanks a lot for looking into it. > BTW, the fix I sent yesterday did not fully pan out... Attached is > an updated > fix for that (but not for this). Thanks. Cheers, Doru -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "Being happy is a matter of choice." |
Doru,
Well, I've got an UNREVIEWED fix for you. You still need the other one, and this one on top. Basically, we need to always take care to collect outer scrolledOffsets, which the original #scrolledOffset didn't. This new version does. That took care of making sure clicks were right. For display though, it was a bit more difficult, but the solution was/is easy. A new method, named #localScrolledOffset does what the old #scrolledOffset does, and only get any local offset. This is then used in Forms to "add" their local scrolled offset for display. This is because, for display, each pane as we drill down, adds its own local scroll to the translation. If we used the fully collected #scrolledOffset, it would then "double" add the offsets. So, the fix is simple, A change to #scrolledOffset to collect all enclosing offsets if there are any, a new localScrolledOffset to only get scrolled offset of the most local form at most, and a change to how FormArtist does its translation, using the new localScrolledOffset. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? AR52626.st (3K) Download Attachment |
Hi Sames,
Thanks. It works nicely. But, I stumbled across two more related problems shown in the attached parcel :): Problem 1. "ListAndButtonInFormFinder open" shows a ListBox and a Button inside each form that gets created. After creating several panes and scrolling, the images disappear from the buttons. I suppose it is the same as the previous display problem. Problem 2. I also added splitters to the example. The splitters only resize the pane to the left and move the panes and the splitters to the right entirely. I made the panes and splitters to the right move by adding both as left and right widgets. The problem is that after building a sufficient amount of panes, the splitters that are outside original view would not move anymore, although the icon changes accordingly. I suspect this is the same as the clicking on the grids. Thanks again. Cheers, Doru On Aug 1, 2007, at 8:58 PM, Samuel S. Shuster wrote: > Doru, > > Well, I've got an UNREVIEWED fix for you. You still need the other > one, and this > one on top. > > Basically, we need to always take care to collect outer > scrolledOffsets, which > the original #scrolledOffset didn't. This new version does. > > That took care of making sure clicks were right. > > For display though, it was a bit more difficult, but the solution > was/is easy. A > new method, named #localScrolledOffset does what the old > #scrolledOffset does, > and only get any local offset. This is then used in Forms to "add" > their local > scrolled offset for display. This is because, for display, each > pane as we drill > down, adds its own local scroll to the translation. If we used the > fully > collected #scrolledOffset, it would then "double" add the offsets. > > So, the fix is simple, A change to #scrolledOffset to collect all > enclosing > offsets if there are any, a new localScrolledOffset to only get > scrolled offset > of the most local form at most, and a change to how FormArtist does > its > translation, using the new localScrolledOffset. > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using?<AR52626.st> www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "There are no old things, there are only old ways of looking at them." PlaygroundWidgetry.zip (6K) Download Attachment |
Tudor:
> Problem 1. "ListAndButtonInFormFinder open" shows a ListBox and a > Button inside each form that gets created. After creating several > panes and scrolling, the images disappear from the buttons. I > suppose it is the same as the previous display problem. > > Problem 2. I also added splitters to the example. The splitters > only resize the pane to the left and move the panes and the > splitters to the right entirely. I made the panes and splitters to > the right move by adding both as left and right widgets. The > problem is that after building a sufficient amount of panes, the > splitters that are outside original view would not move anymore, > although the icon changes accordingly. I suspect this is the same > as the clicking on the grids. > > Thanks again. What is this? Attack of the Widgetry Bug Finder League? Again... Kidding. I want to know that these reports, with their clarity and the examples help make Widgetry better (once I fix the bugs of course). Thanks again. I'll look into this on Monday also And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
In reply to this post by Tudor Girba-3
Doru,
>Problem 1. "ListAndButtonInFormFinder open" shows a ListBox and a >Button inside each form that gets created. After creating several >panes and scrolling, the images disappear from the buttons. I suppose >it is the same as the previous display problem. > >Problem 2. I also added splitters to the example. The splitters only >resize the pane to the left and move the panes and the splitters to >the right entirely. I made the panes and splitters to the right move >by adding both as left and right widgets. The problem is that after >building a sufficient amount of panes, the splitters that are outside >original view would not move anymore, although the icon changes >accordingly. I suspect this is the same as the clicking on the grids. Attached is/are UNREVIEWED fixes for both of these problems. Enjoy! And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? AR52654.st (6K) Download Attachment |
Hi Sames,
Thanks again! It works really well. I still experience yet another related problem :). If you do "GridFinder open" after loading the attached parcel, you will see that the column label string disappears after scrolling to the right. Just for the record, in spite of my many "complains" I find Widgetry a very nice framework to work with. Cheers, Doru On Aug 7, 2007, at 6:59 PM, Samuel S. Shuster wrote: > Doru, > >> Problem 1. "ListAndButtonInFormFinder open" shows a ListBox and a >> Button inside each form that gets created. After creating several >> panes and scrolling, the images disappear from the buttons. I suppose >> it is the same as the previous display problem. >> >> Problem 2. I also added splitters to the example. The splitters only >> resize the pane to the left and move the panes and the splitters to >> the right entirely. I made the panes and splitters to the right move >> by adding both as left and right widgets. The problem is that after >> building a sufficient amount of panes, the splitters that are outside >> original view would not move anymore, although the icon changes >> accordingly. I suspect this is the same as the clicking on the grids. > > Fixes! > > Attached is/are UNREVIEWED fixes for both of these problems. > > Enjoy! > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using?<AR52654.st> www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "No matter how many recipes we'll know, we'll still value a chef." PlaygroundWidgetry.zip (6K) Download Attachment |
Doru,
>I still experience yet another related problem :). If you do >"GridFinder open" after loading the attached parcel, you will see >that the column label string disappears after scrolling to the right. This bug is now #2 on my list. I'll get to it soon. >Just for the record, in spite of my many "complains" I find Widgetry >a very nice framework to work with. Thank you. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? |
In reply to this post by Tudor Girba-3
Doru,
>I still experience yet another related problem :). If you do >"GridFinder open" after loading the attached parcel, you will see >that the column label string disappears after scrolling to the right. Got the UNREVIEWED fix attached. Note, the prior fix must be loaded first. And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, GUI Project Smalltalk Enables Success -- What Are YOU Using? AR52698.st (1K) Download Attachment |
Hi Sames,
Thanks a lot. It works fine. Cheers, Doru On Aug 13, 2007, at 8:55 PM, Samuel S. Shuster wrote: > Doru, > >> I still experience yet another related problem :). If you do >> "GridFinder open" after loading the attached parcel, you will see >> that the column label string disappears after scrolling to the right. > > Got the UNREVIEWED fix attached. Note, the prior fix must be loaded > first. > > And So It Goes > Sames > ______________________________________________________________________ > > Samuel S. Shuster [|] > VisualWorks Engineering, GUI Project > Smalltalk Enables Success -- What Are YOU Using?<AR52698.st> -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "Every successful trip needs a suitable vehicle." |
Free forum by Nabble | Edit this page |