[codenameone-discussions] Re: Not able to swipe tabs when sidemenu is added

2018-10-19 Thread Shai Almog
Hi,
can you file an issue?
I'll try to take a look at it, I made some fixes to pointer drag behavior 
with the side menu.

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/dbe59131-1884-4cc2-96ec-126a8f4141f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[codenameone-discussions] Re: Does Codename one support java 10 or java 11?

2018-10-19 Thread Shai Almog
We support JDK's up to 11 but there might be some nuances with some 
versions of OpenJDK. 

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/e6e4de87-e23e-400d-8a69-6fb0502fe81d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[codenameone-discussions] Not able to swipe tabs when sidemenu is added

2018-10-19 Thread Carlos Verdier
Hi

I'm facing a problem since the Friday's update. As described in the title, 
when a sidemenu is present it's no longer possible to swipe tabs, at least 
not gently.
If you show and hide the side menu, then the tabs start working as they 
should.

The issue is very easy to reproduce, both in simulator and devices. Here is 
a test case:

public void start() {
if(current != null){
current.show();
return;
}
Form f = new Form(new BorderLayout());
Tabs tab = new Tabs();
Container cont1 = new Container(new BorderLayout());
Label lbl1 = new Label("Hello 1");
cont1.add(BorderLayout.CENTER, lbl1);
Container cont2 = new Container(new BorderLayout());
Label lbl2 = new Label("Hello 2");
cont2.add(BorderLayout.CENTER, lbl2);
tab.addTab("Tab 1", cont1);
tab.addTab("Tab 2", cont2);
f.add(BorderLayout.CENTER, tab);
f.getToolbar().addComponentToSideMenu(new Label("Side Panel"));
f.show();
}


Thank you for your help.

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/8317a45b-de1d-4649-8c61-936c6a0dfac7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [codenameone-discussions] Re: Passing a reference of a NativeInterface instance as parametter of another NativeInterface method?

2018-10-19 Thread Thomas
Thanks Steeve. I already use a lookup static map as a solution to my 
problem. This is just that the possibility to pass a NativeInterface 
instance as a NativeInterface parameter (and forth, as a callback result) 
would have been cleaner as I wouldn't have to maintain this static map in 
parallel and have to worry about cleaning it when one of its elements is no 
longer used in my code (so that the GC can collect it)

On Friday, October 19, 2018 at 2:27:34 PM UTC+2, Steve Hannah wrote:
>
> If you can provide more information about your use case, I may be able to 
> suggest a way to achieve it.  While you can't just pass a NativeInterface 
> instance as a NativeInterface parameters, there are a few crafty techniques 
> that you can use to pass "native" objects back and forth.  E.g., on iOS, 
> "native" objects are just pointers, which can be cast to and from longs and 
> passed back and forth.  On java-native platforms (e.g. simulator and 
> Android), I generally use a static lookup table, then pass ids of this 
> lookup table back and forth.
>
> Steve
>
> On Thu, Oct 18, 2018 at 10:20 PM Thomas > 
> wrote:
>
>> OK Thanks.
>> As for the ByteBuffer I completely agree yes ;) (It is the basis of the 
>> binary messages solution chosen by Flutter to communicate between flutter 
>> dart code and native one and it is SO convenient and powerfull to work with 
>> that I also regret not having such an easy solution in CN1 too)
>>
>> On Friday, October 19, 2018 at 7:07:52 AM UTC+2, Shai Almog wrote:
>>>
>>> It hasn't been implemented, it would have been nice but it's a lot of 
>>> work since every change in this part of the code needs to be done for every 
>>> port. It also needs to be replicated in the code generation and the backend 
>>> generation logic. There are multiple points of failure and pain so we try 
>>> to avoid changing those things. The only thing I really miss in native 
>>> interfaces is a proper ByteBuffer to provide high performance shared memory 
>>> although it isn't crucial as we don't have the JNI overhead and can use 
>>> callbacks to map data directly.
>>>
>>> In other words, it's technically possible but such a pain to implement 
>>> we probably won't do it.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "CodenameOne Discussions" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to codenameone-discussions+unsubscr...@googlegroups.com 
>> .
>> Visit this group at 
>> https://groups.google.com/group/codenameone-discussions.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/codenameone-discussions/04ecf3a6-ad0d-4ebe-b14b-07b187ead623%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Steve Hannah
> Software Developer
> Codename One
> http://www.codenameone.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/6afbb278-ea75-4b11-8714-ce8859eb6b78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [codenameone-discussions] Re: Passing a reference of a NativeInterface instance as parametter of another NativeInterface method?

2018-10-19 Thread Steve Hannah
If you can provide more information about your use case, I may be able to
suggest a way to achieve it.  While you can't just pass a NativeInterface
instance as a NativeInterface parameters, there are a few crafty techniques
that you can use to pass "native" objects back and forth.  E.g., on iOS,
"native" objects are just pointers, which can be cast to and from longs and
passed back and forth.  On java-native platforms (e.g. simulator and
Android), I generally use a static lookup table, then pass ids of this
lookup table back and forth.

Steve

On Thu, Oct 18, 2018 at 10:20 PM Thomas  wrote:

> OK Thanks.
> As for the ByteBuffer I completely agree yes ;) (It is the basis of the
> binary messages solution chosen by Flutter to communicate between flutter
> dart code and native one and it is SO convenient and powerfull to work with
> that I also regret not having such an easy solution in CN1 too)
>
> On Friday, October 19, 2018 at 7:07:52 AM UTC+2, Shai Almog wrote:
>>
>> It hasn't been implemented, it would have been nice but it's a lot of
>> work since every change in this part of the code needs to be done for every
>> port. It also needs to be replicated in the code generation and the backend
>> generation logic. There are multiple points of failure and pain so we try
>> to avoid changing those things. The only thing I really miss in native
>> interfaces is a proper ByteBuffer to provide high performance shared memory
>> although it isn't crucial as we don't have the JNI overhead and can use
>> callbacks to map data directly.
>>
>> In other words, it's technically possible but such a pain to implement we
>> probably won't do it.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "CodenameOne Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to codenameone-discussions+unsubscr...@googlegroups.com.
> Visit this group at
> https://groups.google.com/group/codenameone-discussions.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/codenameone-discussions/04ecf3a6-ad0d-4ebe-b14b-07b187ead623%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKWfkUeZZmzA_YAxhK3B7soukTckHetQfhUT21qDyehy5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.