|
|
|||||||
I'm aiming to release Kixforms 2.1 (Build 35) this weekend ... lots-o-new-stuff in the next release - the biggest being ListViews and Collections - along with some other surprises. But I was concerned that maybe some "critical" items may have not made it into the build - some I have gathered and have already included (don't have the list with me) but was wondering if anyone had any outstanding issue or request for any new (small) feature, please post into this space. Will do my best to get it into the build for Saturday. |
||||||||
|
|
|||||||
How difficult would it be to change font attributes for 1 or more items in a listbox? Say, for example, I had a listbox of PCs in a domain and I wanted the NT PCs in green, 9x in red, etc. |
||||||||
|
|
|||||||
Reasonably dificult, I guess... You'd either need some way to accept feedback from the user program on a given display event for the list box, or supply a list with attributes on a per line basis or other, that the Shawn's code would have to use for it's own display callback routine. |
||||||||
|
|
|||||||
Well, each line in a listbox is added individually anyway so that shouldn't be a problem. $listbox.Additem("Item") The issue that I see would be if he could get various lines of a listbox to show the different colors. |
||||||||
|
|
|||||||
I think Madruga stated it perfectly: Reasonably difficult. Kixforms utilizes the standard windows ListBox control - and that control does not have multi-font support. However here's the "reasonably difficult" part ... Windows has a feature (most controls support it) called "OWNERDRAW". That means that as a developer, you can choose to assume the responsibility for drawing the contents (items) of a listbox. And that only comes at the expense of a whole lot of code and development cycles ... Will look deeper into it though ... I might be able to score a custom listbox somewhere ... keep this on the stack. Im also looking into enhancing the ListView control quite a bit going forward ... the ListView is a very "deep" object ... if we could get multi-font support there, would that be of interest ? Just create a single column ListView instead of a ListBox ? [ 02. October 2002, 01:02: Message edited by: Shawn ] |
||||||||
|
|
|||||||
Yeah, I thought it wouldn't be easy, but I tried. If you could get multifont support in the Listview object, well, that'd be awesome. |
||||||||
|
|
|||||||
I have run into something that I think was already mentioned somewhere, but I could not find it. I would like to set textboxes to to a state that they cannot be typed into but the scroll bar works and you can copy text out of it. The .Enabled property totally disables the box. I am looking for something like .Editing so I can turn off the ability to change the .TextBox. Forgive me, if I am going over something that was already discussed. Thanks |
||||||||
|
|
|||||||
something like .locked?   |
||||||||
|
|
|||||||
I would like to possibility to add a tooltip to specific listbox items (to display exta info about lines the mouse is going over) |
||||||||
|
|
|||||||
.Locked is fine with me. I have also noticed that I cannot copy out of a .ListBox. |
||||||||
|
|
|||||||
krabourn, try with this: code:$=createobject("kixtart.form") |
||||||||
|
|
|||||||
I am wanting to be able to either right click and get the standard windws menu to let me copy or be able to press I do appreciate the answer. If I have to script it in, This will help get me started. I was just thinking this was something that Kixforms should have inside it. Thanks |
||||||||
|
|
|||||||
oh, so you could catch the mouse,event and create that form. like you probably have seen there is no much "normal" functions happening automatically.   |
||||||||
|
|
|||||||
Actually, I am not looking to catch an event, in this case. I want someone to be able to copy out of this program. Just like you could copy something out of Word and paste it into Excel. I know the .TextBox and the .ComboBox have this functionality. |
||||||||
|
|
|||||||
you're right... but I remember the time when they didn't and I coded it with events for textbox. anyway, all I did was introduce you the workaround. until it is available as inbuild. anyway, I don't know how the new listview thingies will work out but it actually should be added. imagine excel without ability to select fields and copy it to elsewhere! so, I think it already will be there... just need to wait... shawn? |
||||||||
|
|
|||||||
hmmm ... it doesn't appear as if ListBoxes in either VB and VBA support this behavior ... can anyone verify this ? I think what could be done is the following (just green-lighting here): 1) The script could listen for the ctrl-c event on the listbox ... the KeyPress event would have to be inplemented (no biggie). 2) If ctrl-c pressed, the script could read the data from the listbox (either the whole list, or just an item) and "copy" it to the clipboard. That would have to be implemented as well. Then carry on as normal ... same thing for pasting into the listbox - listen for ctrl-v But more importantly - i would like some confirmation that VB and VBA doesn't support this - can't find much on the web right now. [ 02. October 2002, 16:39: Message edited by: Shawn ] |
||||||||
|
|
|||||||
what about listview? has it "support" for this? |
||||||||
|
|
|||||||
Its a good thing you raised this issue krabourn - because it reminded me that I still have to implement the Copy() & Paste() methods for all objects ... this was available in Version 1 (remember Jooel?) ... but got dropped in version 2. What I will do is quickly code-up the copy() message - then "send" it to the ListBox - and see if it responds ... be right back ... |
||||||||
|
|
|||||||
Ok - the Listbox didn't repond to the COPY message ... the ListView didn't either ... thats not to say that we can't "enhance" these controls to recognise these messages ... just that it won't happen over-night or by Saturday anyways. |
||||||||
|
|
|||||||
Is there going to be anything stop a .TextBox from being edited but still be able to scroll and use windows copy functions? Such as .Enabled/.Locked. |
||||||||
|
|
|||||||
Yeah - that should already be there in the current release - LOCKED = TRUE/FALSE |
||||||||
|
|
|||||||
Oop!!! I am usually better than that. I guess I should get more sleep. Thanks |
||||||||
|
|
|||||||
Krabourn - no worries - plus - there is still some debate in terms of whether the LOCKED property provides adaquate LOCKdown ... that is to say ... we were talking about removing the ability to use the mouse and select text when in it locked state - instead of readonly - it would truely be view-only (couldn't copy snippets out of it) ... Believe as well that one of the things that came out of that discussion was that maybe we could code it so that the textbox would enter this super-readonly state when LOCKED = TRUE and ENABLED = FALSE The other thing I going to squeeze in for saturday is to implement all THREE styles of ComboBox - adding a new property called STYLE and can be set as follows: 0 - DropDown The text portion is editable. The user must click the arrow button to display the list portion. 1 - DropDownList The user cannot directly edit the text portion. The user must click the arrow button to display the list portion. 2 - Simple The text portion is editable. The list portion is always visible. Anyways - stay tuned on that one. The other one was the FIND method for ListBoxes and ListViews ... see if I can get that one in as well. |
||||||||
|
|
|||||||
un-selectable text? can't see any usage for that... if it's addable, do it but if it takes many hours of work, I wouldn't go for it as it's purely a special need... and can be worked around with scripting really easily... just my 0.0127 cents...   |
||||||||
|
|
|||||||
I like the idea of 'unselectable' text. It would be great for an AUP or EULA where it adds an 'air' of legal authority in that the text cannot be duplicated - it is purely aesthetics mind you, but if it isn't difficult to implement then I would like to see it in there. Rod. |
||||||||
|
|
|||||||
Yeah - I've had a couple of occasions where that style of textbox would have been handy ... definitely keep it on the stack ... where is the stack anyways ? |
||||||||
|
|
|||||||
Lost under a stack of requests? Hidden under the piles of pulled out hair? BTW, Shawn, you have mail. |
||||||||
|
|
|||||||
back at yeah - thanks again. |
||||||||
|
|
|||||||
Jooel - you around tonight ? |
||||||||
|
|
|||||||
can i have a progress bar that is solid rather than being made up of blocks? |
||||||||
|
|
|||||||
Hi Redback, You can achieve a solid ProgressBar in code. Try the following out to give you an idea: code:{Edit}Edited code so that the PictureBox clears when the start button is pressed.{/Edit}Break On Rod. [ 03. October 2002, 13:07: Message edited by: rclarke ] |
||||||||
|
|
|||||||
sadly I wasn't... I can't understand this, what more I want to be around, that less I am. this evening (your day) I'll anyway be there...   |
||||||||
|
|
|||||||
Redback ... consider it done ! Jooel ... you got mail ... -Shawn |
||||||||
|
|
|||||||
noo-oooo! I planned to sleep on coming night! well, duty call is a duty call... no matter what... I just get my ass home and will see on that.   |
||||||||
|
|
|||||||
No rest for the weary my friend. |
||||||||
|
|
|||||||
Will the multi-line ToolTip be supported in this release? I think someone mentioned this in a previous post or something. One thing that i'm missing is OnMouseOver so you can show a short description of an item in a label or textbox. I'm guessing it won't be added anytime soon but I hope it's on the to-do list. |
||||||||
|
|
|||||||
that is implemented... for object: http://www.kixforms.freeuk.com/Docs/Events/onmousemove.htm not listbox item though... |
||||||||
|
|
|||||||
Oops I missed that one, thanks for pointing it out |
||||||||
|
|
|||||||
Ok, the three styles of ComboBox are done. Behavior is as outlined in previous post. The SMOOTH style for ProgressBar is done. It now responds to the STYLE (yeah?) property with the following settings: 0 = Chunky 1 = Smooth [ anyone for peanut butter? ] The ToolTip thingy I am game for ... but needs some discussion. In order to do this properly, would anybody "mind" if I introduced a new way of accessing the ToolTip property for all objects ? Basically what I'm saying is that I want break the interface and change things. Right now, the ToolTip property is simply a read-writable text string, like this: code:What I would like to do is turn this simple text property into an embedded object (within each object) ... so to setup a ToolTip going forward, one would say this:$Button.ToolTip = "Press me" code:This will give us much more flexibility. There are some more ToolTip features I would like to enable, for example - having Balloon ToolTips (like with MSAgent?) (I can already here Radimus groaning) and embedding icons in ToolTips (fe. a ToolTip that looks like a Windows MessageBox) ...$Button.ToolTip.Text = "Press Me" Anyways, thats the score - if we go this way - can probably have something going by Saturday ... think about it. I know its not good COM practice to keep change the interface, but this has always been a moving target. Plus there are plans for many more embedded (embeddable) objects down the road (like Menus, ToolBars, StatusBars and ImageLists) -Shawn [ 03. October 2002, 17:55: Message edited by: Shawn ] |
||||||||
|
|
|||||||
I'd rather have it redone if it means doing it the 'right' way or in a way that supports the evolution of KiXforms. If my vote counts, go for the ToolTip change. As far as other embeddable ojects go. Is Context Menu on the list? |
||||||||
|
|
|||||||
Yeah I think you should change it too, looks like it's going to be more effective that way. |
||||||||
|
|
|||||||
Go for the tooltip change !! Did you think over RFC regarding tooltip for listbox items ?? |
||||||||
|
|
|||||||
Tooltip for ListBox (items) would be a pretty big effort ... in the short-term, how about ToolTips for ListView (items) ? Let me know your thoughts maybe a couple of weeks after this saturday ... lets get ListViews out there and see if ListBoxes go the way of the dinosaur ... |
||||||||
|
|
|||||||
shawn, regarding to the previous e-mail... thanks! luv you!!!! |
||||||||
|
|
|||||||
Looking forward to your ideas ... thoughts ... |
||||||||
|
|
|||||||
all I know that my checker has to be updated... .view does not seem to have effect on anything. the thoughts come later... after I get over this weird feeling.   |