No More Posting New Topics!

tandrew

@dobbel first of all thanks for attending to this. I found the solution to this problem and am posting this here for others in case they run into the same issue.

The culprit here was that the property swipeable was set on the tag q-tab-panels. It makes sense that this would cause selecting items would result in the described symptom as mouse movement needs to be observed and swipe initiated.

Removing the property solved it.

Happy.

tandrew

When selecting any text (input field, heading, whatever else) with the mouse (click-and-drag) only the first few characters are seletable before selection via mouse stops.

The culprit here seems to be that on “mouse-drag-selecting” a text, the class “non-selectable” gets set on the <body> tag which then disables the selection capability.

This affects all text-selection. I do have a monaco-editor running in a <div> which is then also affected by this “global” class and makes text selection via mouse nearly impossible.

When selecting text with a mouse very slowly, however, the class “non-selectable” does not get set on the <body> tag and selection is possible.

I am wondering whether this behavior can be changed through some config setup which I may have missed.

Running this as a Singe-Page-Application web app for desktop.

Any help is much appreciated.
– Andrew

“quasar”: “^1.14.7”,
“@quasar/app”: “^2.1.13”,

tandrew

Will revert with results.

tandrew

Will do. Really appreciate your support, however!

tandrew

@metalsadman I think we are not talking about the same thing. I know how to move the Tab Panels into view. I was talking about the actual Tabs above the panels. So to replicate using our example:

Click on the first four check boxes -> tabs Mail, Alarms, Movies and Photos open visibly in the row of open tabs.
Then check “Videos” --> An arrow to the right in the tab bar indicates that there is another entry in the row of tabs. You can only guess, however, because you cannot see it.
Repeat by also checking “Address Book” --> There is no visible evidence that it is open, because it is too far right in the tab bar view.

Here is what I need:
I need a newly opened tab in the tab to scroll into view when opened. Either automatically when creating it, or programmatically, if possible.

tandrew

I’ll give it a shot. Thanks @metalsadman.

tandrew

Thanks for attending to my post. I am not sure whether I explained myself correctly as I am already working with dynamic tab creation.

The issue I have is that a newly created tab is created outside the viewable area if the area is too small. The sample you provided is actually a perfect example: If you activate all the tabs one after another, you can see how the last ones are created outside the viewable area. I need them to be created and scrolled into view so that it is obvious to the user. I am happy to so so programmatically also, but I don’t see how I can accomplish this.

Thanks for any comments!

tandrew

I haven’t seen any comments on the above so far. Would be great to at least get some info on whether there are plans to address this.

tandrew

Re: Omissions in QTabs component

In reference to the above topic, has the following issue been addressed, or does someone have a solution to this?

“When inserted, new tabs that go past the current width are not scrolled into view. Apparently there are not events for doing this.”

I am dynamically creating tabs, and to my knowledge there is no programmatic way of scrolling tabs into view.

Any help very welcome!
Andrew

tandrew

+1 regarding the documentation of this feature. I would like to use it.

tandrew

Hi everyone in this helpful community.
I have a few questions regarding the quasar tree component:

Questions: Is there a way in which I can

Programmatically jump to a node in the tree (as if it were clicked by the user)?
Prevent a node losing focus, even if the user clicks another node within the tree?

Sorry if this is an easy one for some. I don’t seem to be able to figure this out, though.

Thanks!
Andrew

tandrew

I ran into the exact same issue as @joeyezekiel but could not find a solution to this problem here or anywhere.

I figured out that there is a property called “lazy” which is part of the tree. This stores which nodes have been lazy loaded already. When the tree data array is reset (e.g. this.rootNodes.length = 0) then this obviously does not affect the “lazy” object of the tree which remains filled with all the node-keys which had been previously expanded. So when you load up the tree with the same data again (same node-keys), then all keys which are also stored in “lazy” will not show the expand arrow and will not lazy load any longer.

My (simple) solution to this issue was to simply add a statement and clear the lazy object like so: “this.$refs.treeName.lazy = {}” when also resetting the tree data.

I have no idea whether this breaks anything, but it seems to work for me.

Unless this is the appropriate way to deal with it, it would be really cool to have a method to clear the tree which takes care of all the necessary.

Hope it helps someone. Please correct if I am on the wrong path.

No More Posting New Topics!

Posts made by tandrew